From: Lee Revell <rlrevell@joe-job.com>
To: Paul Fulghum <paulkf@microgate.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Laurent Riffard <laurent.riffard@free.fr>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
Kernel development list <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.9-rc4-mm1 : oops when rmmod uhci_hcd [was: 2.6.9-rc3-mm2 : oops...]
Date: Fri, 15 Oct 2004 16:42:08 -0400 [thread overview]
Message-ID: <1097872927.5119.5.camel@krustophenia.net> (raw)
In-Reply-To: <1097861761.2820.18.camel@deimos.microgate.com>
On Fri, 2004-10-15 at 13:36, Paul Fulghum wrote:
> Unique device names are useful for identifying
> which device instance is on a particular interrupt
> (/proc/interrupts), but other drivers beside uhci_hcd
> use a constant name so I guess that is legal :-)
>
I agree that this would be a useful enhancement to the uhci_hcd driver.
For example:
CPU0
0: 183247514 XT-PIC timer 0/47514
1: 67096 XT-PIC i8042 58/67096
2: 0 XT-PIC cascade 0/0
8: 82425669 XT-PIC rtc 0/25669
10: 163607273 XT-PIC uhci_hcd, EMU10K1 0/7273
11: 1912890 XT-PIC uhci_hcd, eth0 0/12890
12: 0 XT-PIC uhci_hcd 0/0
15: 244330 XT-PIC ide1 0/44329
The front panel USB port shares an interrupt with the sound card, the
rear with eth0. Fome some of my testing it would be helpful if these
just had numbers that I could mentally associate with a USB port. Right
now I have to move the mouse and watch the interrupt count.
> Either way, the generic IRQ code should deal with
> duplicates without generating an oops.
Agreed, this bug should be fixed either way.
Lee
next prev parent reply other threads:[~2004-10-15 20:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 19:40 2.6.9-rc4-mm1 : oops when rmmod uhci_hcd [was: 2.6.9-rc3-mm2 : oops...] Laurent Riffard
2004-10-13 15:41 ` Alan Stern
2004-10-14 20:23 ` Laurent Riffard
2004-10-14 21:03 ` Alan Stern
2004-10-14 23:21 ` Laurent Riffard
2004-10-15 15:22 ` Paul Fulghum
2004-10-15 16:18 ` Alan Stern
2004-10-15 16:48 ` Paul Fulghum
2004-10-15 17:21 ` Alan Stern
2004-10-15 17:36 ` Paul Fulghum
2004-10-15 20:42 ` Lee Revell [this message]
2004-10-15 21:14 ` Paul Fulghum
2004-10-16 16:07 ` [patch, 2.6.9-rc4-mm1] fix rmmod uhci_hcd oops Ingo Molnar
2004-10-17 19:47 ` Laurent Riffard
2004-10-15 17:22 ` [linux-usb-devel] Re: 2.6.9-rc4-mm1 : oops when rmmod uhci_hcd [was: 2.6.9-rc3-mm2 : oops...] David Brownell
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=1097872927.5119.5.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=greg@kroah.com \
--cc=laurent.riffard@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mingo@elte.hu \
--cc=paulkf@microgate.com \
--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