On Sat, 4 Feb 2006, Martin Michlmayr wrote:
> > For some reason, the de2104x driver isn't listed as a handler for
> > IRQ 10. That's probably the cause of the problem. Did you have any
> > full- or low-speed USB devices plugged in at the time this occurred?
> > If you didn't then the UHCI hardware would not have generated any
> > interrupt requests.
>
> No, I don't think I ever used USB on this machine. I did some more
> tests based on what you said and have the following data points:
> - Having a USB device (USB stick) plugged in when booting doesn't
> make a difference.
> - When I load the de2104x driver _before_ uhci_hcd, both USB and
> Ethernet work fine.
> - Both modules load fine. USB also works. The problem only occurs
> when I actually try to use the Ethernet device (i.e. run DHCP).
> Then I get that traceback, and USB also stops working.
It sure looks as though the ethernet interface is generating an interrupt
request before the de2104x driver has registered its interrupt handler.
When uhci-hcd isn't already loaded the IRQ is unused, hence disabled, and
so nothing bad happens. If uhci-hcd is already loaded then the IRQ is
enabled (because uhci-hcd is using it), so you get the problem -- an
interrupt occurs with no registered handler.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
