On Mon, Jun 18, 2007 at 12:23:32AM +1000, Keith Goggin wrote:
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
> PCI: No IRQ known for interrupt pin A of device 0000:00:13.0. Probably buggy 
> MP table.
> ohci_hcd 0000:00:13.0: Found HC with no IRQ.  Check BIOS/PCI 0000:00:13.0 
> setup!
> ohci_hcd 0000:00:13.0: init 0000:00:13.0 fail, -19
> PCI: No IRQ known for interrupt pin B of device 0000:00:13.1. Probably buggy 
> MP table.
> ohci_hcd 0000:00:13.1: Found HC with no IRQ.  Check BIOS/PCI 0000:00:13.1 
> setup!
> ohci_hcd 0000:00:13.1: init 0000:00:13.1 fail, -19
> PCI: No IRQ known for interrupt pin C of device 0000:00:13.2. Probably buggy 
> MP table.
> ohci_hcd 0000:00:13.2: Found HC with no IRQ.  Check BIOS/PCI 0000:00:13.2 
> setup!
> ohci_hcd 0000:00:13.2: init 0000:00:13.2 fail, -19
> PCI: No IRQ known for interrupt pin B of device 0000:00:13.3. Probably buggy 
> MP table.
> ohci_hcd 0000:00:13.3: Found HC with no IRQ.  Check BIOS/PCI 0000:00:13.3 
> setup!
> ohci_hcd 0000:00:13.3: init 0000:00:13.3 fail, -19
> PCI: No IRQ known for interrupt pin C of device 0000:00:13.4. Probably buggy 
> MP table.
> ohci_hcd 0000:00:13.4: Found HC with no IRQ.  Check BIOS/PCI 0000:00:13.4 
> setup!
> ohci_hcd 0000:00:13.4: init 0000:00:13.4 fail, -19
> PCI: No IRQ known for interrupt pin D of device 0000:00:13.5. Probably buggy 
> MP table.
> ehci_hcd 0000:00:13.5: Found HC with no IRQ.  Check BIOS/PCI 0000:00:13.5 
> setup!
> ehci_hcd 0000:00:13.5: init 0000:00:13.5 fail, -19

Eeek, that's not good at all (and is indicitive of not a USB problem,
but something else.)

Can you try out the -vanilla kernel and let us know if that fixes the
problem or not?  If not, we need to know this real soon as 2.6.22 is
about to be released.

thanks,

greg k-h
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to