From: Martin Michlmayr <tbm@cyrius.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: Bad interaction between uhci_hcd and de2104x
Date: Sat, 4 Feb 2006 11:15:21 +0000 [thread overview]
Message-ID: <20060204111521.GB18806@deprecation.cyrius.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0602032227200.10200-100000@netrider.rowland.org>
* Alan Stern <stern@rowland.harvard.edu> [2006-02-03 22:30]:
> > When I unload de2104x and uhci_hcd and load only de2104x again
> > then Ethernet works. Similarly, when I completely blacklist the
> > uhci_hcd module the de2104x driver works without any problems.
>
> And presumably, if you blacklist the de2104x driver then your USB
> controller works without any problems.
...
> 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.
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2006-02-04 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 0:50 Martin Michlmayr
2006-02-04 3:30 ` Alan Stern
2006-02-04 11:15 ` Martin Michlmayr [this message]
2006-02-04 16:09 ` Alan Stern
2006-02-04 22:14 ` Martin Michlmayr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060204111521.GB18806@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®