RE: [Ltib] Kernel panic with RAMDISK

[Gérard LASSAILLY]

Hello, some news :

C] solved. Needed to change :
#/dev           d       755     0       0       -       -       -       -
-
To
/dev            d       755     0       0       -       -       -       -
-
In file device_table.txt.
It seems to be needed by genext2fs but not by mkfs.jffs2!

No change on "Kernel Panic".

I tested "rootfs.ext2" file on dev PC (REDHAT 9.0) by mounting it with :
mount -t ext2 -o loop /home/user/bsp/ltib-mcf5445x-20071214/rootfs.ext2 test

It seem to be OK : it look like filesystem I get when booting from JFFS2.
I can see dev/ram et dev/ram0 devices nodes in it and also every files I
need.

So I think that misuse is in kernel config or u-boot config.
Please have you seen something bad in my preceding mail ?

Best regards.

**********************************
Gérard LASSAILLY
KN SYSTEMES
Tél. : 04 42 94 63 63
Fax. : 04 42 94 66 24
e-mail : address@hidden
**********************************

> -----Message d'origine-----
> De : Gérard LASSAILLY [mailto:address@hidden
> Envoyé : mardi 26 mai 2009 10:59
> À : 'Stuart Hughes'
> Cc : 'address@hidden'
> Objet : RE: [Ltib] Kernel panic with RAMDISK
> 
> Hi Stuart,
> 
> Thanks for your suggestions.
> A] What do you mean by "load address" ?
> 
> We are in trouble only when trying to use RAMDISK for rootfs and not
> JFFS2.
> When using rootfs.jffs2 all is fine.
> 
> NOTA : Ramdisk is OK when booting with rootfs.jffs2.
> 
> B] Are you agree with me about kernel config (add to KERNEL 2.6.23 Setup :
> (*)Initial RAM filesystem support)?
> 
> C] During "genext2fs" I got some "warning":
> creating an ext2 compressed filesystem image: rootfs.ext2.gz
> genext2fs: device table line 39 skipped: can't find directory '/dev' to
> create '
> pts''
> ... (same for all device node)
> 
> rootfs/dev directory is here and 777 attrib.
> Have you already experienced this ?
> 
> D] I have tried many bootargs :
> 
> 1) set bootargs 'root=/dev/mtdblock4 rw rootfstype=jffs2 ip=none
> mtdparts=physmap-
> flash.0:384k(ub)ro,128k(par),384k(fw),2560k(KSafe)ro,4096)'
> 
> 2) set bootargs 'root=/dev/ram rw ramdisk_size=10771 ip=none
> mtdparts=physmap-
> flash.0:384k(ub)ro,128k(par),384k(fw),6M(KSafe)ro,6M(BinApp),3200k(jffs2)'
> 
> 3) set bootargs 'root=/dev/ram ip=none mtdparts=physmap-
> flash.0:384k(ub)ro,128k(par),384k(fw),6M(KSafe)ro,6M(BinApp),3200k(jffs2)'
> 
> 4) set bootargs 'root=/dev/ram0 ip=none mtdparts=physmap-
> flash.0:384k(ub)ro,128k(par),384k(fw),6M(KSafe)ro,6M(BinApp),3200k(jffs2)'
> 
> 5) set bootargs 'ip=none mtdparts=physmap-
> flash.0:384k(ub)ro,128k(par),384k(fw),6M(KSafe)ro,6M(BinApp),3200k(jffs2)'
> 
> 6) set bootargs 'root=/dev/ram0 initrd=0x43cd5000 ip=none
> mtdparts=physmap-
> flash.0:384k(ub)ro,128k(par),384k(fw),6M(KSafe)ro,6M(BinApp),3200k(jffs2)'
> 
> 7) set bootargs 'root=/dev/ram0'
> 
> 8) set bootargs 'root=/dev/ram'
> 
> =======================================================================
> When I try initrd with ramdisk I got this (for case "8)", sames results
> for other cases) :
> =======================================================================
> 
> -> bootm 0x6e0000 0xce0000
> ## Booting image at 006e0000 ...
>    Image Name:   Linux Kernel Image
>    Created:      2009-05-25  16:18:53 UTC
>    Image Type:   M68K Linux Kernel Image (uncompressed)
>    Data Size:    2277376 Bytes =  2.2 MB
>    Load Address: 40020000
>    Entry Point:  40020000
>    Verifying Checksum ... OK
> OK
> ## Current stack ends at 0x43F8DA38 => set upper limit to 0x43F8D230
> ## cmdline at 0x43F8D130 ... 0x43F8D13D
> memstart    = 0x40000000
> memsize     = 0x04000000
> flashstart  = 0x00000000
> flashsize   = 0x01000000
> flashoffset = 0x00000000
> sramstart   = 0x80000000
> sramsize    = 0x00008000
> mbar        = 0xFC000000
> busfreq     = 133.333 MHz
> flbfreq     = 66.666 MHz
> inpfreq     = 33.333 MHz
> vcofreq     = 533.333 MHz
> 
> baudrate    = 115200 bps
> Not skipping initrd
> ## Loading RAMDisk Image at 00ce0000 ...
>    Image Name:   uboot ext2 ramdisk rootfs
>    Created:      2009-05-25  17:30:07 UTC
>    Image Type:   M68K Linux RAMDisk Image (gzip compressed)
>    Data Size:    2848175 Bytes =  2.7 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
> ## initrd at 0x00CE0040 ... 0x00F975EE (len=2848175=0x2B75AF)
>    Loading Ramdisk to 43cd5000, end 43f8c5af ... OK
> ## Transferring control to Linux (at address 40020000) ...
> Bumping USB Priority
> Linux version 2.6.23 (address@hidden) (gcc version 4.2.0
> 20070318 (prerelease) (Sourcery G++ Lite 4.2-35)) #151 Mon Ma9
> starting up linux startmem 0xc024c000, endmem 0xc3ffffff,       size 61MB
> console [ttyS0] enabled
> Built 1 zonelists in Zone order.  Total pages: 8156
> Kernel command line: root=/dev/ram
> PID hash table entries: 256 (order: 8, 1024 bytes)
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 8192 (order: 2, 32768 bytes)
> Inode-cache hash table entries: 4096 (order: 1, 16384 bytes)
> Memory: 62784k/62784k available (1520k kernel code, 1144k data, 80k init)
> SLUB: Genslabs=23, HWalign=16, Order=0-2, MinObjects=8, CPUs=1, Nodes=1
> Mount-cache hash table entries: 1024
> NET: Registered protocol family 16
> MCF5445x INIT_DEVICES
> usb: OTG Host registered
> SCSI subsystem initialized
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> NET: Registered protocol family 2
> IP route cache hash table entries: 2048 (order: 0, 8192 bytes)
> TCP established hash table entries: 2048 (order: 1, 16384 bytes)
> TCP bind hash table entries: 2048 (order: 0, 8192 bytes)
> TCP: Hash tables configured (established 2048 bind 2048)
> TCP reno registered
> JFFS2 version 2.2. (NAND) B) 2001-2006 Red Hat, Inc.
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> ColdFire internal UART serial driver version 1.00
> ttyS0 at 0xfc060000 (irq = 90) is a builtin ColdFire UART
> ttyS1 at 0xfc064000 (irq = 91) is a builtin ColdFire UART
> ttyS2 at 0xfc068000 (irq = 92) is a builtin ColdFire UART
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> loop: module loaded
> FEC ENET Version 0.2
> fec: PHY @ 0x0, ID 0x20005ca2 -- DP83849
> eth0: ethernet 00:50:c2:5d:b0:7e
> fec: PHY @ 0x0, ID 0x20005ca2 -- DP83849
> eth1: ethernet 00:50:c2:5d:b0:7f
> physmap platform flash device: 01000000 at 00000000
> physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
>  Intel/Sharp Extended Query Table at 0x0031
> Using buffer write method
> cfi_cmdset_0001: Erase suspend on write enabled
> RedBoot partition parsing not available
> fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
> fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
> fsl-ehci fsl-ehci.0: irq 175, io mem 0xfc0b0000
> fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 1 port detected
> Initializing USB Mass Storage driver...
> usbcore: registered new interface driver usb-storage
> USB Mass Storage support registered.
> mice: PS/2 mouse device common for all mice
> i2c /dev entries driver
> TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> List of all partitions:
> 1f00      16384 mtdblock0 (driver?)
> No filesystem could mount root, tried:  ext2 msdos vfat
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
> block(1,0)
> 
> ============================
> 
> 
> Bests regards
> 
> **********************************
> Gerard LASSAILLY
> KN SYSTEMES
> Tel. : 04 42 94 63 63
> Fax. : 04 42 94 66 24
> e-mail : address@hidden
> **********************************
> 
> > -----Message d'origine-----
> > De : Stuart Hughes [mailto:address@hidden
> > Envoye : mardi 26 mai 2009 09:54
> > À : Gérard LASSAILLY
> > Cc : address@hidden
> > Objet : Re: [Ltib] Kernel panic with RAMDISK
> >
> > Hi Gerade,
> >
> > You probably need to contact Freescale to get support with this as I
> > don't have hardware to try this out.
> >
> > However, here's some suggestions:
> >
> > * Have you tried booting from an initrd that you've tftp'ed to the same
> > load address ?
> >
> > * Have you tried storing exactly the same image into your jffs2
> filesystem
> > ?
> >
> > * Can you verify the integrity of the rootfs you have stored in jffs2
> >
> > * Did you pass the load address in the jffs2 case ?
> >
> > * If you boot in another way, are you able to access the jffs2
> > filesystem (decompress/mount it)?
> >
> > Regards, Stuart
> >
> > Gérard LASSAILLY wrote:
> > > Using LTIB for MCF54455EVB (COLDFIRE) we can’t got boot with an
> initrd.
> > > When using rootfs.jffs2 we can boot.
> > >
> > > We have added in General Setup (KERNEL 2.6.23) : Initial RAM
> filesystem
> > and
> > > RAM disk support
> > > And
> > > root=/dev/ram0 in bootargs
> > > ==> Without success.
> > >
> > > We can see U-boot : “loading Ramdisk to 43CD50000, end 43F8C74F … OK”
> > > message.
> > >
> > > But kernel already finish with :
> > >
> > > List of all partitions :
> > > 1f00   ...... (mtdblock0....)
> > > ...
> > > No filesystem could mount root, tried: ext2 msdos vfat
> > > Kernel panic - not syncing: VFS: Un       able toi mount root fs on
> > > unknown-block(1, 0)
> > >
> > > What are we missing?
> > > Does using MTD have some effect on initrd use?
> > >
> > > Best regards
> > >
> > > **********************************
> > > Gérard LASSAILLY
> > > KN SYSTEMES
> > > 80 avenue Archimède -  BP60284
> > > 13798 AIX EN PROVENCE CEDEX 3
> > > Tél. : (33)04 42 94 63 63
> > > Fax. : (33)04 42 94 66 24
> > > e-mail : address@hidden
> > > **********************************
> > >
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > LTIB home page: http://bitshrine.org
> > >
> > > Ltib mailing list
> > > address@hidden
> > > http://lists.nongnu.org/mailman/listinfo/ltib
> > >