[Xen-devel] Re: Xen 4.0 + PVOPS + Intel VTD + USB EHCI = BUG()

["David P. Quigley" <dpquigl@xxxxxxxxxxxxx>]

On Tue, 2010-01-26 at 13:19 -0500, Konrad Rzeszutek Wilk wrote:
> > > The kernel output. Can you boot the pvops kernel without Xen and provide
> > > the 'dmesg' and 'cat /proc/interrupts' output please?
> > 
> > I attached two files with the output.
> 
> > Initializing cgroup subsys cpuset
> > Initializing cgroup subsys cpu
> > Linux version 2.6.31.6-pvops-dom0 (dpquigl@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx) 
> > (gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC) ) #7 SMP Tue Jan 26 
> > 12:09:38 EST 2010
> > Command line: ro root=/dev/mapper/VolGroup-lv_root console=tty0 
> > console=ttyS0,115200n8
> > KERNEL supported cpus:
> >   Intel GenuineIntel
> >   AMD AuthenticAMD
> >   Centaur CentaurHauls
> > BIOS-provided physical RAM map:
> 
> ... snip ..
> > pci 0000:00:1a.0: reg 20 io port: [0xff20-0xff3f]
> > pci 0000:00:1a.1: reg 20 io port: [0xff00-0xff1f]
> > pci 0000:00:1a.2: reg 20 io port: [0xfc00-0xfc1f]
> > pci 0000:00:1a.7: reg 10 32bit mmio: [0xfebda000-0xfebda3ff]
> > pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
> > pci 0000:00:1a.7: PME# disabled
> 
> ... snip ..
> > IOMMU: Setting identity map for device 0000:00:1a.0 [0xbfe58000 - 
> > 0xbfe70000]
> > IOMMU: Setting identity map for device 0000:00:1a.1 [0xbfe58000 - 
> > 0xbfe70000]
> > IOMMU: Setting identity map for device 0000:00:1a.2 [0xbfe58000 - 
> > 0xbfe70000]
> > IOMMU: Setting identity map for device 0000:00:1a.7 [0xbfe58000 - 
> > 0xbfe70000]
> 
> ... snip ...
> > ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 22 (level, low) -> IRQ 22
> > ehci_hcd 0000:00:1a.7: setting latency timer to 64
> > ehci_hcd 0000:00:1a.7: EHCI Host Controller
> > ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
> > ehci_hcd 0000:00:1a.7: debug port 1
> > ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
> > ehci_hcd 0000:00:1a.7: irq 22, io mem 0xfebda000
> > ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
> > usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
> > usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> > usb usb1: Product: EHCI Host Controller
> > usb usb1: Manufacturer: Linux 2.6.31.6-pvops-dom0 ehci_hcd
> > usb usb1: SerialNumber: 0000:00:1a.7
> > usb usb1: configuration #1 chosen from 1 choice
> > hub 1-0:1.0: USB hub found
> > hub 1-0:1.0: 6 ports detected
> > work_for_cpu used greatest stack depth: 3888 bytes left
> >   alloc irq_desc for 23 on node 0
> >   alloc kstat_irqs on node 0
> > ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
> > ehci_hcd 0000:00:1d.7: setting latency timer to 64
> > ehci_hcd 0000:00:1d.7: EHCI Host Controller
> > ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
> > ehci_hcd 0000:00:1d.7: debug port 1
> > ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
> > ehci_hcd 0000:00:1d.7: irq 23, io mem 0xff980000
> > ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
> > usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
> > usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> > usb usb2: Product: EHCI Host Controller
> > usb usb2: Manufacturer: Linux 2.6.31.6-pvops-dom0 ehci_hcd
> > usb usb2: SerialNumber: 0000:00:1d.7
> > usb usb2: configuration #1 chosen from 1 choice
> > hub 2-0:1.0: USB hub found
> > hub 2-0:1.0: 6 ports detected
> > ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
> 
> So what happend to 0000:00:1a.0 and 0000:00:1a.1? In the Xen boot
> those devices were the ones that failed:
> 
> uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> uhci_hcd 0000:00:1a.0: UHCI Host Controller
> uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
> uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000ff20
> uhci_hcd 0000:00:1a.0: host system error, PCI problems?
> uhci_hcd 0000:00:1a.0: host controller halted, very bad!
> uhci_hcd 0000:00:1a.0: HC died; cleaning up
> uhci_hcd 0000:00:1a.0: USB bus 3 deregistered
> uhci_hcd 0000:00:1a.0: PCI INT A disabled
> uhci_hcd 0000:00:1a.0: init 0000:00:1a.0 fail, -108
> uhci_hcd: probe of 0000:00:1a.0 failed with error -108
> 
> But they don't show up in your bootup here? So did somethinh change? Did
> they get initialized later?
> 
> Can you provide the 'lspci -vvvv' from your bare-metal? Wonder what the
> 1a.0 and 1a.1 show as.

Ahh sorry about that. I removed the uhci module from the kernel build to
see if I could get the pvops kernel to finish booting. I've rebuilt it
with uhci back in and here is the updated dmesg and interrupts.
Something that was odd when I took the uhci driver out was that it hung
just after the failure to initialize the radeon driver which both dmesg
outputs have in them so I don't think thats the problem. Just after that
it hangs.

Dave

Attachment: interrupts.txt
Description: Text document

Attachment: pvops-output.txt
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel