* xHCI Express Card failure -- ACPI related? @ 2011-02-23 0:55 Sarah Sharp 2011-02-23 1:54 ` Matthew Garrett 0 siblings, 1 reply; 5+ messages in thread From: Sarah Sharp @ 2011-02-23 0:55 UTC (permalink / raw) To: linux-usb-u79uwXL29TY76Z2rM5mHXA, linux-acpi-u79uwXL29TY76Z2rM5mHXA Cc: Len Brown I'm having an issue with an xHCI (USB 3.0 host controller) Express Card. This card works fine on 2.6.37, but on 2.6.38-rc5, when I plug in the card, I get this output in dmesg: Feb 22 16:32:28 xanatos kernel: [ 119.345996] irq 23: nobody cared (try booting with the "irqpoll" option) Feb 22 16:32:28 xanatos kernel: [ 119.346002] Pid: 0, comm: kworker/0:0 Not tainted 2.6.38-rc5+ #745 Feb 22 16:32:28 xanatos kernel: [ 119.346005] Call Trace: Feb 22 16:32:28 xanatos kernel: [ 119.346007] <IRQ> [<ffffffff8109a1f6>] ? __report_bad_irq+0x26/0xa0 Feb 22 16:32:28 xanatos kernel: [ 119.346019] [<ffffffff8109a3fc>] ? note_interrupt+0x18c/0x1d0 Feb 22 16:32:28 xanatos kernel: [ 119.346024] [<ffffffff8109ad7d>] ? handle_fasteoi_irq+0xcd/0x100 Feb 22 16:32:28 xanatos kernel: [ 119.346029] [<ffffffff8100543d>] ? handle_irq+0x1d/0x30 Feb 22 16:32:28 xanatos kernel: [ 119.346032] [<ffffffff81004bb8>] ? do_IRQ+0x58/0xd0 Feb 22 16:32:28 xanatos kernel: [ 119.346037] [<ffffffff8149f5d3>] ? ret_from_intr+0x0/0xe Feb 22 16:32:28 xanatos kernel: [ 119.346040] <EOI> [<ffffffff8126f2d0>] ? acpi_idle_enter_c1+0x7e/0x99 Feb 22 16:32:28 xanatos kernel: [ 119.346048] [<ffffffff8126f2b2>] ? acpi_idle_enter_c1+0x60/0x99 Feb 22 16:32:28 xanatos kernel: [ 119.346054] [<ffffffff8138ac92>] ? cpuidle_idle_call+0x82/0xf0 Feb 22 16:32:28 xanatos kernel: [ 119.346059] [<ffffffff81001906>] ? cpu_idle+0x56/0xb0 Feb 22 16:32:28 xanatos kernel: [ 119.346064] [<ffffffff8149861b>] ? start_secondary+0x1c1/0x1c8 Feb 22 16:32:28 xanatos kernel: [ 119.346068] [<ffffffff81263386>] ? acpi_ns_parse_table+0x2e/0x34 Feb 22 16:32:28 xanatos kernel: [ 119.346073] [<ffffffff81267a8c>] ? acpi_load_tables+0x9c/0x15d Feb 22 16:32:28 xanatos kernel: [ 119.346076] handlers: Feb 22 16:32:28 xanatos kernel: [ 119.346078] [<ffffffffa0123500>] (usb_hcd_irq+0x0/0x70 [usbcore]) Feb 22 16:32:28 xanatos kernel: [ 119.346100] Disabling IRQ #23 I haven't had a chance to bisect yet. Given that there wasn't any big new features added to the xHCI driver in 2.6.38, I don't think my code is the culprit here. Could it be a USB core or ACPI issue? Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: xHCI Express Card failure -- ACPI related? 2011-02-23 0:55 xHCI Express Card failure -- ACPI related? Sarah Sharp @ 2011-02-23 1:54 ` Matthew Garrett [not found] ` <20110223015445.GA27481-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org> 0 siblings, 1 reply; 5+ messages in thread From: Matthew Garrett @ 2011-02-23 1:54 UTC (permalink / raw) To: Sarah Sharp Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA, linux-acpi-u79uwXL29TY76Z2rM5mHXA, Len Brown On Tue, Feb 22, 2011 at 04:55:13PM -0800, Sarah Sharp wrote: > I'm having an issue with an xHCI (USB 3.0 host controller) Express Card. > This card works fine on 2.6.37, but on 2.6.38-rc5, when I plug in the > card, I get this output in dmesg: Is the controller associated with irq 23? -- Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <20110223015445.GA27481-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>]
* Re: xHCI Express Card failure -- ACPI related? [not found] ` <20110223015445.GA27481-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org> @ 2011-02-23 14:57 ` Sarah Sharp 2011-02-23 15:09 ` Matthew Garrett 0 siblings, 1 reply; 5+ messages in thread From: Sarah Sharp @ 2011-02-23 14:57 UTC (permalink / raw) To: Matthew Garrett Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA, linux-acpi-u79uwXL29TY76Z2rM5mHXA, Len Brown On Wed, Feb 23, 2011 at 01:54:45AM +0000, Matthew Garrett wrote: > On Tue, Feb 22, 2011 at 04:55:13PM -0800, Sarah Sharp wrote: > > I'm having an issue with an xHCI (USB 3.0 host controller) Express Card. > > This card works fine on 2.6.37, but on 2.6.38-rc5, when I plug in the > > card, I get this output in dmesg: > > Is the controller associated with irq 23? I think it is, before the xHCI driver switches to MSI/MSIX. I'd have to disable MSI in 2.6.37 to confirm. Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: xHCI Express Card failure -- ACPI related? 2011-02-23 14:57 ` Sarah Sharp @ 2011-02-23 15:09 ` Matthew Garrett 2011-02-23 16:23 ` Sarah Sharp 0 siblings, 1 reply; 5+ messages in thread From: Matthew Garrett @ 2011-02-23 15:09 UTC (permalink / raw) To: Sarah Sharp; +Cc: linux-usb, linux-acpi, Len Brown On Wed, Feb 23, 2011 at 06:57:47AM -0800, Sarah Sharp wrote: > On Wed, Feb 23, 2011 at 01:54:45AM +0000, Matthew Garrett wrote: > > On Tue, Feb 22, 2011 at 04:55:13PM -0800, Sarah Sharp wrote: > > > I'm having an issue with an xHCI (USB 3.0 host controller) Express Card. > > > This card works fine on 2.6.37, but on 2.6.38-rc5, when I plug in the > > > card, I get this output in dmesg: > > > > Is the controller associated with irq 23? > > I think it is, before the xHCI driver switches to MSI/MSIX. I'd have to > disable MSI in 2.6.37 to confirm. Mm. Sounds like it's the hardware generating a legacy IRQ after you've changed to MSI? Any chance this could be related to the irq synchronisation patches? -- Matthew Garrett | mjg59@srcf.ucam.org ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: xHCI Express Card failure -- ACPI related? 2011-02-23 15:09 ` Matthew Garrett @ 2011-02-23 16:23 ` Sarah Sharp 0 siblings, 0 replies; 5+ messages in thread From: Sarah Sharp @ 2011-02-23 16:23 UTC (permalink / raw) To: Matthew Garrett; +Cc: linux-usb, linux-acpi, Len Brown On Wed, Feb 23, 2011 at 03:09:22PM +0000, Matthew Garrett wrote: > On Wed, Feb 23, 2011 at 06:57:47AM -0800, Sarah Sharp wrote: > > On Wed, Feb 23, 2011 at 01:54:45AM +0000, Matthew Garrett wrote: > > > On Tue, Feb 22, 2011 at 04:55:13PM -0800, Sarah Sharp wrote: > > > > I'm having an issue with an xHCI (USB 3.0 host controller) Express Card. > > > > This card works fine on 2.6.37, but on 2.6.38-rc5, when I plug in the > > > > card, I get this output in dmesg: > > > > > > Is the controller associated with irq 23? > > > > I think it is, before the xHCI driver switches to MSI/MSIX. I'd have to > > disable MSI in 2.6.37 to confirm. > > Mm. Sounds like it's the hardware generating a legacy IRQ after you've > changed to MSI? Any chance this could be related to the irq > synchronisation patches? Could be related, but I'm not sure that's the issue. I don't see any messages at all from the xHCI driver or the USB core about the new host before the "nobody cared" message appears (although it turned out I have CONFIG_USB_XHCI_HCD_DEBUGGING turned off). AFAICT, the driver never gets loaded. But if the xHCI driver failed in its init sequence... I'll check. Sarah Sharp ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-02-23 16:23 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-02-23 0:55 xHCI Express Card failure -- ACPI related? Sarah Sharp
2011-02-23 1:54 ` Matthew Garrett
[not found] ` <20110223015445.GA27481-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2011-02-23 14:57 ` Sarah Sharp
2011-02-23 15:09 ` Matthew Garrett
2011-02-23 16:23 ` Sarah Sharp
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox