From: Georg Acher <acher@in.tum.de>
To: Rui Sousa <rsousa@grad.physics.sunysb.edu>
Cc: Michael Elkins <me@sigpipe.org>,
usb@in.tum.de, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel 2.4.0-test11-ac1 hang with usb-uhci and emu10k1
Date: Thu, 23 Nov 2000 17:49:52 +0100 [thread overview]
Message-ID: <20001123174952.B7591@in.tum.de> (raw)
In-Reply-To: <20001123020203.A30491@toesinperil.com> <Pine.LNX.4.21.0011231028030.17678-100000@grad.physics.sunysb.edu>
In-Reply-To: <Pine.LNX.4.21.0011231028030.17678-100000@grad.physics.sunysb.edu>
On Thu, Nov 23, 2000 at 04:35:33PM +0000, Rui Sousa wrote:
> On Thu, 23 Nov 2000, Michael Elkins wrote:
>
> Usb controller is sharing a interrupt with the emu10k1.
> For what I know the emu10k1 driver doesn't have any problem
> sharing irq's, so I would blame the usb driver...
usb-uhci doesn't also have any problem with sharing irqs:
> cat /proc/interrupts
10: 5597981 XT-PIC aic7xxx, eth0, usb-uhci
Hm, no one left to blame...
I would debug it as follows:
Place various printks in the initialization code (reset_hc(), start_hc() and
alloc_uhci) and find out after which printk it hangs. Then it would be
possible to investigate this further...
--
Georg Acher, acher@in.tum.de
http://www.in.tum.de/~acher/
"Oh no, not again !" The bowl of petunias
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-23 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 10:02 Michael Elkins
2000-11-23 15:32 ` Rui Sousa
2000-11-23 16:49 ` Georg Acher [this message]
2000-11-23 22:45 ` Michael Elkins
2000-11-23 23:06 ` [PATCH] " Jeff Garzik
2000-11-23 23:53 ` Linus Torvalds
2000-11-24 13:04 ` [patch-2.4.0-test11] various small fixes Tigran Aivazian
2000-11-24 7:06 ` [PATCH] Re: PROBLEM: kernel 2.4.0-test11-ac1 hang with usb-uhci and emu10k1 Michael Elkins
2000-11-24 16:30 ` Linus Torvalds
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=20001123174952.B7591@in.tum.de \
--to=acher@in.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=me@sigpipe.org \
--cc=rsousa@grad.physics.sunysb.edu \
--cc=usb@in.tum.de \
/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®