All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Riffard <laurent.riffard@free.fr>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>, Lee Revell <rlrevell@joe-job.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>, Paul Fulghum <paulkf@microgate.com>
Subject: Re: [patch, 2.6.9-rc4-mm1] fix rmmod uhci_hcd oops
Date: Sun, 17 Oct 2004 21:47:56 +0200	[thread overview]
Message-ID: <4172CC6C.1010108@free.fr> (raw)
In-Reply-To: <20041016160737.GA19630@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]


Ingo Molnar wrote:
> this patch fixes the rmmod oops reported by Paul Fulghum. It is
> caused by the generic-irqs subsystem creating multiple
> /proc/irq/<nr>/<name> directory entries with the same name which
> then confuses procfs upon module removal.
> 
> Ingo

This patch fixed the problem for me.

For information, here is the the contents of my /proc/interrupts :
>            CPU0       
>   0:    1085029          XT-PIC  timer
>   1:       4473          XT-PIC  i8042
>   2:          0          XT-PIC  cascade
>   5:     129799          XT-PIC  eth0, Ensoniq AudioPCI, uhci_hcd, uhci_hcd
>   8:          1          XT-PIC  rtc
>   9:          0          XT-PIC  acpi
>  10:          2          XT-PIC  ohci1394
>  12:      16872          XT-PIC  i8042
>  14:      12803          XT-PIC  ide0
>  15:         78          XT-PIC  ide1
> NMI:          0 
> LOC:          0 
> ERR:          0
> MIS:          0

and the contents of /proc/irq/5/ :
> /proc/irq/5/:
> total 0
> dr-xr-xr-x  2 root root 0 oct 17 21:45 Ensoniq AudioPCI/
> dr-xr-xr-x  2 root root 0 oct 17 21:45 eth0/
> dr-xr-xr-x  2 root root 0 oct 17 21:45 uhci_hcd/
> 
> /proc/irq/5/Ensoniq AudioPCI:
> total 0
> 
> /proc/irq/5/eth0:
> total 0
> 
> /proc/irq/5/uhci_hcd:
> total 0

Thank you, Paul and Ingo.

-- 
laurent


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2004-10-17 19:50 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
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 [this message]
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=4172CC6C.1010108@free.fr \
    --to=laurent.riffard@free.fr \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mingo@elte.hu \
    --cc=paulkf@microgate.com \
    --cc=rlrevell@joe-job.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.