linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Justin Mattock" <justinmattock@gmail.com>
To: "John Kacur" <jkacur@gmail.com>
Cc: linux-rt-users@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Ingo Molnar" <mingo@elte.hu>,
	"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: Can't boot 2.6.26-rt1
Date: Sat, 2 Aug 2008 14:31:48 -0700	[thread overview]
Message-ID: <dd18b0c30808021431m12b1600en7f52eb825d27ed76@mail.gmail.com> (raw)
In-Reply-To: <520f0cf10808021416n286855f9s126d416230aee249@mail.gmail.com>

On Sat, Aug 2, 2008 at 2:16 PM, John Kacur <jkacur@gmail.com> wrote:
> VFS: Cannot open root device
> "disk/by-id/scsi-SATA_WDC_WD1600BEVS-WD-WXEZ07100576-part 7" or
> unknown block(0,0)
> Please append a correct "root = " boot option; here are the available
> partitions.
> Pid:1,comm:swapper Not tainted
> 2.6.26-rt1-default#1linux-rt-users@vger.kernel.org
> [< ffff ffff 8046 c149 >] rt_mutex_lock+0x22/0x50
> [< ffff ffff 8046 cae6 >] _mutex_unlock+0xe/0x10
> [< ffff ffff 8020 cb00 >] exit_intr+0x10/0x1e
> [< ffff ffff 8028 633d >] trace_hardirqs_on_caller+0x1e/0x133
> [< ffff ffff 8020 d608 >] child_rip+0xa/0x12
> [< ffff ffff 8020 cb69 >] restore_args+0x0/0x30
> [< ffff ffff 8020 d5fe >] child_rip+0x0/0x12
>
> preempt count 00000001
> 1-level deep critical section nesting
> [< ffff ffff 8047 43e2 >] .... panic +0x43/0x167
> [< ffff ffff 8073 6338 >] (<= mount_block_root+0x258/0x26f
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Hello; I was receiving this last week,
wasn't receving this:
Pid:1,comm:swapper Not tainted
> 2.6.26-rt1-default#1linux-rt-users@vger.kernel.org
> [< ffff ffff 8046 c149 >] rt_mutex_lock+0x22/0x50
> [< ffff ffff 8046 cae6 >] _mutex_unlock+0xe/0x10
> [< ffff ffff 8020 cb00 >] exit_intr+0x10/0x1e
> [< ffff ffff 8028 633d >] trace_hardirqs_on_caller+0x1e/0x133
> [< ffff ffff 8020 d608 >] child_rip+0xa/0x12
> [< ffff ffff 8020 cb69 >] restore_args+0x0/0x30
> [< ffff ffff 8020 d5fe >] child_rip+0x0/0x12

but was having this:
 VFS: Cannot open root device
what was causing this is grub from dapper,feisty,etc..
if you compile you're kernel with initrd.img then will work,
but if you: make you're kernel statically(make, make install)
it will produce unable to mount vfs.
downgrade grub or use grub2.
if you've already did that, then I don't know.
regards;
-- 
Justin P. Mattock

  reply	other threads:[~2008-08-02 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 21:16 Can't boot 2.6.26-rt1 John Kacur
2008-08-02 21:31 ` Justin Mattock [this message]
2008-08-02 21:31 ` Steven Rostedt
2008-08-02 22:24   ` John Kacur
2008-08-02 23:29     ` Justin Mattock

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=dd18b0c30808021431m12b1600en7f52eb825d27ed76@mail.gmail.com \
    --to=justinmattock@gmail.com \
    --cc=jkacur@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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).