On Sat, 27 Nov 2010, Alexander E. Patrakov wrote:
26.11.2010 01:25, Alan Stern wrote:They should be called before the bad IRQ is reported. That's what IOn Thu, 25 Nov 2010, Alexander E. Patrakov wrote:Sorry, I didn't add them due to being busy with a different (non-kernel)
25.11.2010 21:06, Alan Stern wrote:On Thu, 25 Nov 2010, Alexander E. Patrakov wrote:It is not a module here, so I have to recompile the kernel in order to
Hello.According to your listing, they are used by uhci-hcd. Do the messages
After switching my Gentoo desktop from sysvinit + openrc to systemd, I
started getting "nobody cared" messages about IRQs 16 and 19 (common
thing: they are assigned to the USB controllers, that's why CC:
go away if you unload uhci-hcd before shutting down?
try this. Will do that tomorrow.
You may need to debug the uhci-hcd driver. Look intoOK, tomorrow I will add some printks there.
drivers/usb/host/uhci-hcd.c; the uhci_shutdown() routine ought to be
called and it ought to call uhci_hc_died(), which in turn calls
uhci_reset_hc() in pci-quirks.c, which is supposed to prevent the
controller from generating any IRQs.
bug. What do you want to know - just the fact that these functions are
called before or after reporting the bad IRQ?
want to verify.
This suggests that the problem comes from the firewire controller, notEven without rebuilding the kernel, you can unbind the uhci-hcd driverThanks for the tip. Below are the updated test results, including the
from the hardware by going to the /sys/bus/pci/drivers/uhci_hcd
directory and doing:
echo -n device-name>unbind
where "device-name" is the name of one of the symlinks in that
directory.
ones posted in my first mail, for completeness.
1. No irqpoll, no unbind: the system reports that nobody cared for IRQs,
then waits, displays SATA errors, waits again, shuts down.
2. irqpoll, no unbind: the system shuts down without any delays.
3. No irqpoll, unbind uhci-hcd from everything it controls: the system
reports bad IRQ 19 (consumed by firewire-ohci), waits, displays SATA
errors, waits again, shuts down.
the UHCI controller.
Are you sure that you ever got "nobody cared" reports for IRQ 16? Your
listing showed that uhci-hcd used both 16 and 19 whereas firewire-ohci
used only 19.
4. No irqpoll, unbind both uhci-hcd and firewire-ohci from everything:And this tends to confirm it. The SATA errors are probably a separate
the system does not report any bad IRQs, waits, displays SATA errors,
waits again, shuts down.
issue.
What happens if you unbind firewire-ohci but not uhci-hcd?
5. irqpoll, unbind both uhci-hcd and firewire-ohci from everything: sameApparently that doesn't stop the controller from misbehaving. But you
as (4).
I have no firewire devices.
need to do more tests to be sure of this.
Attachment:
nobody_cared_1.jpg
Description: JPEG image