On Wed, 1 Dec 2010, Alexander E. Patrakov wrote: > > One last test. What happens if you unbind the firewire driver and all > > the UHCI controllers except the one attached to IRQ 16? > > As I was not sure if you mean 16 or 19, I did two tests. In both cases, > the firewire driver and all UHCI controllers except one were unbound. In > both cases, the system printed the line I added to uhci_hc_died(), > reported a bad IRQ (16 and 19, respectively), waited, displayed SATA > errors, waited again, and powered itself off. I.e., the screenshot is > nearly identical to what I sent earlier. > > > > Possible explanations: IRQs are being misrouted, so the system thinks > > it gets IRQ 16 when in fact a different interrupt line was activated > > (this is related to ACPI, but I don't see any connection to systemd). > > Or the interrupt layer is malfunctioning and it thinks IRQs are > > arriving when they aren't. > > I forgot to mention that only shutdown is problematic, reboots are OK. Well, I'm baffled. I don't see how the problem could be coming from the drivers, which implies it must be in a more central part of the kernel. The fact that the bad IRQs arrived on the expected lines indicates that they are not being misrouted. Alan Stern -- 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
