From: Jon Smirl <jonsmirl@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: lkml thread "current linus bk, error mounting root"
Date: Tue, 22 Mar 2005 00:01:46 +0000 [thread overview]
Message-ID: <9e473391050321160154cbfe2c@mail.gmail.com> (raw)
I just sent this to AndrewM in reference to the lkml thread "current
linus bk, error mounting root".
The problem is that something in the bk tree after 2.6.11 caused the
mount of my root SATA device to fail.
--------------------------------------------------------------------
No, I think Jens wants all of the distributions to fix it. I have
filed a bug with Fedora on it.
Something changed in the timing for loading drivers during boot. You
used to be able to do:
modprobe ata_piix
mount /dev/sda1
Now you have to do this:
modprobe ata_piix
sleep 1
mount /dev/sda1
I suspect the problem is that udev doesn't get a chance to run anymore.
The sleep 1 allows it to run and it creates /dev/sda1.
Build ata_piix in and the problem goes away too.
Jens is right that this is a user space issue, but how many people are
going to find this out the hard way when their root drives stop
mounting. Since no one is complaining I have to assume that most
kernel developers have their root device drivers built into the
kernel. I was loading mine as a module since for a long time Redhat
was not shipping kernels with SATA built in.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&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
reply other threads:[~2005-03-22 0:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9e473391050321160154cbfe2c@mail.gmail.com \
--to=jonsmirl@gmail.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).