linux-kernel - Re: Can't boot 2.6.26-rt1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <dd18b0c30808021629y374d0e96t1f8f8d063b1872d1@mail.gmail.com>
Date:	Sat, 2 Aug 2008 16:29:37 -0700
From:	"Justin Mattock" <justinmattock@...il.com>
To:	"John Kacur" <jkacur@...il.com>
Cc:	"Steven Rostedt" <rostedt@...dmis.org>,
	linux-rt-users@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>
Subject: Re: Can't boot 2.6.26-rt1

On Sat, Aug 2, 2008 at 3:24 PM, John Kacur <jkacur@...il.com> wrote:
> On Sat, Aug 2, 2008 at 11:31 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
>>
>> On Sat, 2 Aug 2008, John Kacur wrote:
>>
>>> VFS: Cannot open root device
>>
>> Do you use an initrd boot disk? If so make sure the initrd is correct.
>> Sometimes it is best to first get a 2.6.26 kernel booting without initrd
>> and then use that same config on the -rt kernel.
>>
>> -- Steve
>
> Thanks Justin and Steve for the hints - it turned out to be simple,
> somehow the make install scripts were mangling the location of the
> initrd, a quick edit to grub and everything is working again.
> John
>
>>
>>> "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@...r.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
>>>
>>
>>
>

Cool;
yeah last week this happened as well
to me, something so simple. causing me
to run around freaking out.
regards;

-- 
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/