Subject: Re: booting 2.6 kernel on ML403

From: Ameet Patil <[email-masked]>
Date: Wed, 04 Oct 2006 09:00:15 +0100

Pradeep Sampath wrote:
> Hi Ameet,
> Thanks for the instant reply. I changed root parameter to xsa as you 
> suggested root=/dev/xsa2. But i still get the same failure.
>  
> [    3.093694] TCP bic registered
> [    3.129458] NET: Registered protocol family 8
> [    3.181412] NET: Registered protocol family 20
> [    3.236744] VFS: Cannot open root device "xsa2" or unknown-block(0,0)
> [    3.313092] Please append a correct "root=" boot option
> [    3.375552] Kernel panic - not syncing: VFS: Unable to mount root 
> fs on unkno
> wn-block(0,0)
> [    3.474504]  <0>Rebooting in 180 seconds..
>
>  
> On the CF i created the following block and character device files
> # mknod -m 660 console c 5 1
> # mknod -m 660 xsa b 254 0
> # mknod -m 660 xsa1 b 254 1
> # mknod -m 660 xsa2 b 254 2
> # mknod -m 660 xsa3 b 254 3
> mkdir tts
> # mknod -m 660 0 c 4 64
>
> > Problem 2:
> > - Untar the kernel 2.6.17.1
> > - Applied the 5 TEMAC patches
> > - Applied Ameet's Sysace patch
> which patch did you apply? For TEMAC... apply the following patch:
> http://www.cs.york.ac.uk/rtslab/demos/amos/xupv2pro/patches/linuxppc-2.6.17.1-sysace-1.2-after-TEMAC.patch
> Yes, i have applied *only* after-TEMAC.patch. But looks like it blows 
> away the configuration and results in kernel hang.
>  
> Any further suggestions on where i should look at.
>  
> regards.
> Pradeep
Please could send me all the boot messages until the point where it 
stops. This will help me better identify the problem.

Thanks,
-Ameet