All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc4-mm1 panic on boot
Date: Tue, 16 May 2006 01:45:38 -0700 (PDT)	[thread overview]
Message-ID: <e4c3fi$utm$1@terminus.zytor.com> (raw)
In-Reply-To: 20060516001501.GA7528@localhost

Followup to:  <20060516001501.GA7528@localhost>
By author:    lgouv@tele2.be
In newsgroup: linux.dev.kernel
>
> Just upgraded from rc3-mm4.
> Panic on boot with this message (copied by hand ):
> 	kinit:do_mount
> 	kinit: name_to_dev_t(/dev/hda8) = dev (0,0)
> 	kinit:rot_dev = dev (0,0)
> 	kinit root_dev = dev (0,0)
> 	kinit trying to mount /dev/root on /root
> 	...........
> /dev/hda8 is my root partition but I suppose dev (0,0) is the first
> partition on hda which is FAT.
> I tried vanilla rc4 with the same result.
> 

This means kinit couldn't find a name-to-number mapping for the string
/dev/hda8.  However, you said you tried vanilla rc4 with the same
result, and vanilla rc4 doesn't use klibc.

This means hda8 simply isn't discovered on your system, which probably
means hda isn't discovered.  This typically is an issue with your
kernel configuration, but it's not always.

There should be somewhere in your boot messages a message such as the
following:

Probing IDE interface ide0...
hda: WDC WD2500JB-00EVA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 1024KiB
hda: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63,
UDMA(100)
hda: cache flushes supported
 hda: hda1 hda2 hda3 hda4

Does this show up in your successful boots?  Failing boots?

	-hpa

  reply	other threads:[~2006-05-16  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16  0:15 2.6.17-rc4-mm1 panic on boot lgouv
2006-05-16  8:45 ` H. Peter Anvin [this message]
2006-05-16 16:50   ` Leopold Gouverneur
2006-05-16 17:31     ` H. Peter Anvin

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='e4c3fi$utm$1@terminus.zytor.com' \
    --to=hpa@zytor.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.