mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Frédéric L. W. Meunier" <1@pervalidus.net>
To: linux-kernel@vger.kernel.org
Cc: linux-hotplug-devel@lists.sourceforge.net
Subject: udev related ? (Was Re: rmmod deadlocks with 2.6.5-rc[2,3])
Date: Tue, 30 Mar 2004 19:49:11 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0403301938450.1237@pervalidus.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0403301606180.352@pervalidus.dyndns.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2196 bytes --]

OK, I gave 2.6.3-rc3-mm1 a try and could reproduce it.

I still compile with CONFIG_DEVFS_FS=y and
CONFIG_DEVFS_MOUNT=y, but to use udev boot with devfs=nomount.

I then booted with devfs=mount acpi=off noapic. Guess what ? I
was able to unmount all offending modules.

What next ? Boot with devfs=mount to see if ACPI was to blame.
No, it wasn't.

My /etc/rc.d/rc.S is very simple:

[ -e /dev/.devfsd -a -x /sbin/devfsd ] && devfsd /dev

(only run devfsd if devfs is mounted)

mount -vn -t proc proc /proc # Needed for LABEL= in /etc/fstab

mount -vn -t sysfs sysfs /sys

[ ! -e /dev/.devfsd -a -d /sys/block ] && /etc/rc.d/start_udev

(only run start_udev if devfs isn't mounted and sysfs is
mounted)

Since 2.6.4 works fine for me using devfs=nomount, something is
broken. I'm using the latest udev and hotplug.

I'm attaching a strace of a rmmod that failed.

On Tue, 30 Mar 2004, Frédéric L. W. Meunier wrote:

> On Tue, 30 Mar 2004, Daniel Drake wrote:
>
> > Frédéric L. W. Meunier wrote:
> > > If I boot with 2.6.5-rc[2,3] and use rmmod snd_via82xx or rmmod
> > > ohci_hcd (it doesn't happen with all modules), rmmod deadlocks.
> > > 2.6.4 works fine.
> >
> > The ohci_hcd problem should be temporarily fixed by a recent
> > patch to this list, from Greg KH (subject: [PATCH] USB:
> > Eliminate wait following interface unregistration). This
> > worked for me.
>
> I forgot to report that I don't need OHCI. It's hotplug which
> loads it for some reason under 2.6, but not under 2.4.
>
> > As for the snd_ modules, this is a different problem, which I
> > am still experiencing. I have had it with both snd_emu10k1
> > and snd_intel8x0 - but it does not happen every time. I have
> > experienced it on 2.6.5-rc2 and -rc3 (plus their -mm
> > patches). rmmod hangs and doesnt respond to kill -9.
>
> I used ALSA from CVS.
>
> > Is there any output I can capture to diagnose this?
>
> Here nothing gets printed. Maybe strace can help. But I'll
> wait.
>
> It also happened removing i2c_isa when I went through removing
> all modules. Nothing wrong with joydev, adi, gameport, it87...

-- 
http://www.pervalidus.net/contact.html

[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 950 bytes --]

  reply	other threads:[~2004-03-30 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-30 18:43 rmmod deadlocks with 2.6.5-rc[2,3] Frédéric L. W. Meunier
2004-03-30 15:48 ` Daniel Drake
2004-03-30 19:12   ` Frédéric L. W. Meunier
2004-03-30 22:49     ` Frédéric L. W. Meunier [this message]
2004-03-30 23:42       ` udev related ? (Was Re: rmmod deadlocks with 2.6.5-rc[2,3]) Greg KH
2004-04-01  9:35         ` Takashi Iwai

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=Pine.LNX.4.58.0403301938450.1237@pervalidus.dyndns.org \
    --to=1@pervalidus.net \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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®