On Tue, Mar 5, 2013 at 3:41 PM, Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx> wrote: > On Fri, Mar 01, 2013 at 08:41:13AM +0100, Hannes Reinecke wrote: >> On 02/27/2013 10:13 PM, Bjorn Helgaas wrote: >> >[+cc Andy] >> > >> >3) I don't understand why the xhci init fails in the first place. It >> >looks like the "request interrupt 255 failed" message is from >> >xhci_try_enable_msi(), but that function tries to enable MSI-X, then >> >MSI, then falls back to legacy interrupts, where we get the error. >> >But the device supports MSI, so I don't know why we even fall back to >> >trying legacy interrupts. Hannes, do you have any insight into that? >> >Obviously I'm missing something here. >> > >> Hehe. Due to overly clever design. >> xhci actually sets up interrupts _twice_, once per request_irq() in >> the generic code and a second time during xhci_run. >> But as the first call fails it'll never ever run the second part. >> >> I'll be sending a patch. > > Something like this? > > http://marc.info/?l=linux-usb&m=132972894117916&w=2 > > (Apparently we had this issue around the same time last year, but we > thought the BIOS bug had been resolved.) > > Sarah Sharp Where are we at with this? I don't see Sarah's patch in the tree, and I haven't applied any changes, so my guess is this is still broken. Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
