From: Takashi Iwai <tiwai@suse.de>
To: Greg KH <greg@kroah.com>
Cc: "Fr?d?ric L. W. Meunier" <1@pervalidus.net>,
linux-kernel@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: udev related ? (Was Re: rmmod deadlocks with 2.6.5-rc[2,3])
Date: Thu, 01 Apr 2004 09:35:16 +0000 [thread overview]
Message-ID: <s5hisgkvy5n.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040330234251.GA8549@kroah.com>
At Tue, 30 Mar 2004 15:42:51 -0800,
Greg KH wrote:
>
> On Tue, Mar 30, 2004 at 07:49:11PM -0300, Fr?d?ric L. W. Meunier wrote:
> > OK, I gave 2.6.3-rc3-mm1 a try and could reproduce it.
>
> Yes, the bug is still there. It is being activly worked on as I type
> this...
>
> And no, it's not udev related, but udev does help show the bug...
i've heard that the recent sysfs change since 2.6.5-rc triggered rmmod
hangup of ALSA modules.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-04-01 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0403301529590.1233@pervalidus.dyndns.org>
[not found] ` <406996C2.4030204@reactivated.net>
[not found] ` <Pine.LNX.4.58.0403301606180.352@pervalidus.dyndns.org>
2004-03-30 22:49 ` udev related ? (Was Re: rmmod deadlocks with 2.6.5-rc[2,3]) Frédéric L. W. Meunier
2004-03-30 23:42 ` Greg KH
2004-04-01 9:35 ` Takashi Iwai [this message]
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=s5hisgkvy5n.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=1@pervalidus.net \
--cc=greg@kroah.com \
--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;
as well as URLs for NNTP newsgroup(s).