All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walt H <waltabbyh@comcast.net>
To: akpm@osdl.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test6-mm4
Date: Sun, 05 Oct 2003 12:31:10 -0700	[thread overview]
Message-ID: <3F80717E.6060300@comcast.net> (raw)

I'm having a problem booting 2.6.0-test6-mm(2-4) when using an initrd.
Seems that the initrd never gets loaded, and the root filesystem never
gets mounted as a result. Reverting RD0-initrd-B6.patch allows initrd to
work again, and my machine to boot. I'm using a standard non-initramfs
initrd and a devfs enabled SMP kernel. I don't see any of the printk's
regarding ramdisk/initrd in any boot messages prior to panic. Let me
know if you need anything else. Thanks,

-Walt

mice: PS/2 mouse device common for all mice
input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI: (supports S0 S5)
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Kernel panic: VFS: Unable to mount root fs on hda3



             reply	other threads:[~2003-10-05 19:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-05 19:31 Walt H [this message]
2003-10-05 21:56 ` 2.6.0-test6-mm4 Walt H
  -- strict thread matches above, loose matches on Subject: below --
2003-10-05  8:33 2.6.0-test6-mm4 Andrew Morton
2003-10-05  8:33 ` 2.6.0-test6-mm4 Andrew Morton
2003-10-05  9:26 ` 2.6.0-test6-mm4 Daniele Bellucci
2003-10-05  9:26   ` 2.6.0-test6-mm4 Daniele Bellucci

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=3F80717E.6060300@comcast.net \
    --to=waltabbyh@comcast.net \
    --cc=akpm@osdl.org \
    --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.