From: Prarit Bhargava <prarit@sgi.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.6.12-rc4+ & udev kobject problem
Date: Thu, 26 May 2005 16:00:03 +0000 [thread overview]
Message-ID: <4295F283.1010007@sgi.com> (raw)
In-Reply-To: <42931DD4.4040200@iit.demokritos.gr>
Vassilis Virvilis wrote:
> I echoed DEVPATH after Prarit Bhargava suggestion.
> But shouldn't modprobe not beeing called if is MODALIAS is null string
>
linux-hotplug-devel Colleagues,
I've privately emailed Bill with a quick-and-dirty solution for the problems he
was experiencing with the system boot. I wasn't sure if he was having the same
problems I've had with 2.6.12 and old packages but it looks like he was.
I'm surprised we haven't had more people on this list wondering about the
strange behaviour of their initrd/initramfs :).
When I looked at the original output Bill had posted I noticed that it looked
like drivers were attempting to load at the same time and because of this he
eventually hit an oops. I (and an engineer from another company working on
another arch) have hit the same problem due to the requirements of our current work.
(Unfortunately, I'm more familiar with RedHat than I am with other distro's --
please bear with me.)
The issue is that David Howells posted a patch that changed the behaviour of
kallsyms/insmod/rmmod sometime ago. The patch is correct in what it does,
however, the patch requires that /sbin/sh must be aware of pid returns by wait().
http://lkml.org/lkml/2005/1/17/132
There are two fixes that I'm aware of, and depending on what you're doing they
are both "correct" (although in the case of developing in 2.6.12, IMO, you
_must_ do the latter).
The first fix is for the situation where you're developing for a specific
distribution. If this is the case, then you should back out the patch above and
continue moving forward.
The second fix, and again you must do this if you're developing 2.6.12, is to
*update the mkinitrd package* which has a new version of /bin/sh.
P.
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
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
next prev parent reply other threads:[~2005-05-26 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 12:28 2.6.12-rc4+ & udev kobject problem Vassilis Virvilis
2005-05-25 0:22 ` Greg KH
2005-05-25 11:55 ` Vassilis Virvilis
2005-05-25 15:55 ` Greg KH
2005-05-25 17:11 ` Vassilis Virvilis
2005-05-25 17:18 ` Kay Sievers
2005-05-26 15:10 ` Vassilis Virvilis
2005-05-26 15:41 ` Vassilis Virvilis
2005-05-26 15:53 ` Greg KH
2005-05-26 16:00 ` Prarit Bhargava [this message]
2005-05-27 12:55 ` Vassilis Virvilis
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=4295F283.1010007@sgi.com \
--to=prarit@sgi.com \
--cc=linux-hotplug@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).