mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.28-rc2: initrd fails to create bloc devices
Date: Thu, 30 Oct 2008 21:48:10 +0300	[thread overview]
Message-ID: <200810302148.10761.arvidjaar@mail.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

I am using Mandriva which has mkinitrd based on RedHat (current version
in 6.0.63). With 2.6.28 it sporadically fails (or I should rather say,
it sporadically manages) to created block devices in initrd which of
course prevents kernel from finding root later.

The control flow is

1. mkblkdevs (I assume, it is for any built-in driver)
2. load modules, needed for disk access/file system
3. mkblkdevs again
4. mount real root etc etc etc

First mkblkdevs will initially traverse /sys/block and create all it
finds there. It is empty in my case (no built-in driver).

Second mkblkdev will notice that device tree was already initialized
and will not descend into /sys/block but rather listen and process to
hotplug events generated in step 2. At least that is how I interpret
nash code.

So it looks like something has changed between 2.6.27 and 2.6.28 regarding
event delivery. It looks like race condition. I do not see any pattern
except after several attempts it would suddenly boot.

I tried both IDE and PATA, both show the same problem.

Any idea?

-andrey

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

                 reply	other threads:[~2008-10-30 18:48 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=200810302148.10761.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --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®