From: Rusty Russell <rusty@rustcorp.com.au>
To: Pozsar Balazs <pozsy@uhulinux.hu>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
333052@bugs.debian.org, Harald Dunkel <harald.dunkel@t-online.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.14, udev: unknown symbols for ehci_hcd
Date: Sun, 06 Nov 2005 14:51:36 +1100 [thread overview]
Message-ID: <1131249096.12902.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20051105184802.GB25468@ojjektum.uhulinux.hu>
On Sat, 2005-11-05 at 19:48 +0100, Pozsar Balazs wrote:
> On Sat, Nov 05, 2005 at 06:31:04PM +0100, Kay Sievers wrote:
> > I've got these messages several times on the experimental SUSE too,
> > but can't reproduce it so far, even without Rusty's patch to modprobe
> > they have disappeared. See here for the details:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=333052
>
>
> Just to let you know, I've also met this problem (on another distro),
> and did not know about this bugreport until now.
> So I've done another workaround: modprobe already parses /proc/modules
> to check whether the modules needed are already loaded, and this file
> also shows us the state of the modules, being "Loading", "Live" or
> "Unloading".
>
> With my patch, modprobe waits until the needed modules come out of the
> "Loading" or "Unloading" state.
Yes, this was going to be my solution. However, we only need to resort
to this is locking fails (read-only root filesystem).
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next prev parent reply other threads:[~2005-11-06 3:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-05 15:37 2.6.14, udev: unknown symbols for ehci_hcd Harald Dunkel
2005-11-05 16:25 ` Greg KH
2005-11-06 5:59 ` Harald Dunkel
2005-11-06 17:03 ` Gustavo Guillermo Pérez
2005-11-11 0:20 ` Rob Landley
2005-11-06 21:51 ` Greg KH
2005-11-07 11:33 ` Marco d'Itri
2005-11-07 17:31 ` Greg KH
2005-11-07 19:07 ` Pozsar Balazs
2005-11-07 19:12 ` Greg KH
2005-11-07 19:20 ` Pozsar Balazs
2005-11-07 19:27 ` Greg KH
[not found] ` <1131405438.21610.17.camel@localhost.localdomain>
2005-11-07 23:19 ` Marco d'Itri
2005-11-05 17:31 ` Kay Sievers
2005-11-05 18:48 ` Pozsar Balazs
2005-11-06 3:51 ` Rusty Russell [this message]
2005-11-06 6:22 ` Bug#333052: " Harald Dunkel
2005-11-06 14:50 ` Harald Dunkel
2005-11-06 15:29 ` Pozsar Balazs
2005-11-06 17:05 ` Harald Dunkel
2005-11-06 17:21 ` Marco d'Itri
2005-11-07 6:00 ` Harald Dunkel
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=1131249096.12902.1.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=333052@bugs.debian.org \
--cc=harald.dunkel@t-online.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pozsy@uhulinux.hu \
/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