From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
tj@kernel.org, LKML <linux-kernel@vger.kernel.org>,
albcamus@gmail.com, pjones@redhat.com, alex.shi@intel.com,
fedora-devel-list@redhat.com
Subject: Re: system fails to boot
Date: Mon, 17 Nov 2008 16:19:55 +0800 [thread overview]
Message-ID: <1226909995.2866.116.camel@ymzhang> (raw)
In-Reply-To: <1226644196.2866.83.camel@ymzhang>
On Fri, 2008-11-14 at 14:29 +0800, Zhang, Yanmin wrote:
> On Fri, 2008-11-14 at 09:18 +0300, Alexey Dobriyan wrote:
> > On Fri, Nov 14, 2008 at 01:16:21PM +0800, Zhang, Yanmin wrote:
> > > Jens,
> > >
> > > We run into system boot failure with kernel 2.6.28-rc. We found it on a couple of
> > > machines, including T61 notebook, nehalem machine, and another HPC NX6325 notebook.
> > > All the machines use FedoraCore 8 or FedoraCore 9. With kernel prior to 2.6.28-rc,
> > > system boot doesn't fail.
> > >
> > > I debug it and locate the root cause. Pls. see
> > > http://bugzilla.kernel.org/show_bug.cgi?id=11899
> > > https://bugzilla.redhat.com/show_bug.cgi?id=471517
> > >
> > > As a matter of fact, there are 2 bugs.
> > >
> > > 2) root=LABEL=/, system always can't boot. initrd init reports
> > > switchroot fails. Here is an executation branch of nash when booting:
> > > (1) nash read /sys/block/sda/dev; Assume major is 8 (on my desktop)
> > > (2) nash query /proc/devices with the major number; It found line "8 sd";
> > > (3) nash use 'sd' to search its own probe table to find device (DISK) type for the device
> > > and add it to its own list;
> > > (4) Later on, it probes all devices in its list to get filesystem labels;
> > > scsi register "8 sd" always.
> > > When major is 259, nash fails to find the device(DISK) type. I enables CONFIG_DEBUG_BLOCK_EXT_DEVT=y
> > > when compiling kernel, so 259 is picked up for device /dev/sda1, which causes nash to fail
> > > to find device (DISK) type.
> > > To fixing issue 2), I create a patch for nash and another patch for kernel.
> > > http://bugzilla.kernel.org/attachment.cgi?id=18859
> > > http://bugzilla.kernel.org/attachment.cgi?id=18837
As for issue 2) with root=LABEL=/, I double-checked nash codes. That's really beyond what I imagined. I'm not
an expert of nash. kernel might allocate MINOR number from MAX_EXT_DEVT (259) for any type of disk
(cciss/ataraid/sd/ide/floppy/md ...), while nash assumes a MAJOR number is used by one of them exclusively.
In the other hand, nash probes scsi/ide/usb serially as long as the type is DEV_TYPE_DISK. I won't say
nash codes are not perfect, but nash is growing.
Peter Jones,
You maintain nash. What's your opinion?
-yanmin
next prev parent reply other threads:[~2008-11-17 8:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 5:16 system fails to boot Zhang, Yanmin
2008-11-14 5:26 ` Tejun Heo
2008-11-14 7:16 ` Jens Axboe
2008-11-14 6:18 ` Alexey Dobriyan
2008-11-14 6:22 ` Tejun Heo
2008-11-14 7:22 ` Zhang, Yanmin
2008-11-14 6:29 ` Zhang, Yanmin
2008-11-17 8:19 ` Zhang, Yanmin [this message]
2008-11-21 17:26 ` Jike Song
2008-11-24 5:52 ` Zhang, Yanmin
2008-11-24 6:40 ` Jike Song
2008-11-24 6:57 ` Zhang, Yanmin
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=1226909995.2866.116.camel@ymzhang \
--to=yanmin_zhang@linux.intel.com \
--cc=adobriyan@gmail.com \
--cc=albcamus@gmail.com \
--cc=alex.shi@intel.com \
--cc=fedora-devel-list@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.com \
--cc=tj@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