[News]

News: Welcome to GLomation peer support forum

[davecramer]

davecramer

davecramer

• Guest

I get a kernel panic following these instructions

EXT2-fs error (device ram0): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=163735142
9, rec_len=5, name_len=152
Remounting filesystem read-only
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.


Dave

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

Can you please post the complete boot log?

[davecramer]

davecramer

davecramer

• Guest

Not sure how this got in this thread, it should be the thread for using debian. Either way I get the kernel panic when trying to use the ramdisk.

et bootargs console=ttyS0,115200 root=/dev/ram rw initrd=0x21800000,8M rootfstype=ext2 mtdparts=at91_nand:1M(bootloader),3M
(kernel),-(rootfs)
U-Boot> nand read 0x21000000 0x100000 0x200000; bootm 0x21000000

NAND read: device 0 offset 0x100000, size 0x200000
 2097152 bytes read: OK
## Booting kernel from Legacy Image at 21000000 ...
   Image Name:   Linux-2.6.25
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1494792 Bytes =  1.4 MB
   Load Address: 20008000
   Entry Point:  20008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux................................................................................................. done, booting t
he kernel.
Linux version 2.6.25 (user1@Atlas) (gcc version 4.2.3) #23 Wed Aug 27 22:28:51 EDT 2008
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Atmel AT91SAM9260-EK
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 198 MHz, master 99 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: console=ttyS0,115200 root=/dev/ram rw initrd=0x21800000,8M rootfstype=ext2 mtdparts=at91_nand:1M(bootloader),3M
(kernel),-(rootfs)
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 53564KB available (2756K code, 223K data, 120K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 152 bytes
NET: Registered protocol family 16
AT91: Power Management
AT91: Starting after general reset
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: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 8192K
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (SUMMARY)  B) 2001-2006 Red Hat, Inc.
yaffs Aug 26 2008 19:36:02 Installing.
io scheduler noop registered
io scheduler anticipatory registered (default)
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL
atmel_usart.4: ttyS4 at MMIO 0xfffd0000 (irq = 23) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
ssc ssc.0: Atmel SSC device at 0xc4878000 (irq 14)
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (00:0c:20:02:0a:5b)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, irq=-1)
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver rndis_wlan
usbcore: registered new interface driver zd1201
Driver 'sd' needs updating - please use bus_type methods
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
AT91 NAND: 8-bit, Software ECC
Scanning device for bad blocks
Bad eraseblock 209 at 0x01a20000
Bad eraseblock 785 at 0x06220000
Bad eraseblock 837 at 0x068a0000
3 cmdlinepart partitions found on MTD device at91_nand
Creating 3 MTD partitions on "at91_nand":
0x00000000-0x00100000 : "bootloader"
0x00100000-0x00400000 : "kernel"
0x00400000-0x08000000 : "rootfs"
usbmon: debugfs is not available
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
udc: at91_udc version 3 May 2006
mice: PS/2 mouse device common for all mice
input: gpio-keys as /class/input/input0
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
rtc-at91sam9 at91_rtt.0: rtc0: SET TIME!
i2c /dev entries driver
at91sam9_wdt: invalid timeout (must be between 1 and 16)
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock
RAMDISK: Compressed image found at block 0
invalid compressed format (err=1)
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 120K
EXT2-fs error (device ram0): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_le
n=0, name_len=0
Remounting filesystem read-only
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

RAMDISK: Compressed image found at block 0
invalid compressed format (err=1)

The above 2 lines from the boot log shows that the kernel didn't find the a correct RAM disk image.  Can you check your U-boot command that loaded the RAM disk to make sure the correct RAM disk image is loaded to the right memory location?

[davecramer]

davecramer

davecramer

• Guest

good catch, I should have seen that

here's the command same problem

-Boot> t 0x21800000 ramdisk.gz
macb0: link up, 100Mbps full-duplex (lpa: 0x45e1)
Using macb0 device
TFTP from server 192.168.1.14; our IP address is 192.168.1.15
Filename 'ramdisk.gz'.
Load address: 0x21800000
Loading: #################################################################
         #################################################################
         ########
done
Bytes transferred = 2024042 (1ee26a hex)
U-Boot> set bootargs console=ttyS0,115200 root=/dev/ram rw initrd=0x21800000,8M rootfstype=ext2 mtdparts=at91_nand:1M(bootloader),3M
(kernel),-(rootfs)
U-Boot> nand read 0x21000000 0x100000 0x200000; bootm 0x21000000

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

Not sure why it wouldn't work.  Please try the RAMDISK image in the attachment.  Maybe the image from the website is corrupted.

[davecramer]

davecramer

davecramer

• Guest

Still didn't work,

I think this might be related to using OS X as the tftp server. Is there any way to specify binary for the t command ?

Dave

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

If you suspect the TFTP server problem then try to use serial download.  The u-boot command loadb can be used for bianry file transfer in Kermit mode and loady can be used for y-modem mode.

[davecramer]

davecramer

davecramer

• Guest

OK, that was the problem, I used a linux box for my tftpserver and it's all good now.

Thanks,
Dave