• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 105 subscribers
  • Views 902 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Kernel panic

bah thierno
Intellectual 340 points

Hello,

I have a problème to boot my DM6467 with the U-boot (RS232).

here my printenv

DM6467 EVM # printenv
bootcmd=nboot 80700000 0 a0000;bootm
bootdelay=3
baudrate=115200
bootfile="uImage"
serverip=192.168.1.100
ipaddr=192.168.1.201
nfshost=192.168.1.168
rootpath=/home/thierno/workdir/filesys
bootargs=console=ttyS0,115200n8 noinitrd rw ip=192.168.1.177:192.168.1.168::255.
255.255.0:dm6467:eth0: root=/dev/nfs nfsroot=192.168.1.168:/home/thierno/workdir
/filesys,nolock,tcp mem=120M
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:0e:99:02:b2:68

Environment size: 444/131068 bytes

 

the adress ip of my host system is: 192.168.1.168 and the ip of the EVM:192.168.1.177

I tried the method outlined in the forum but i have against a problem.

NB: here the resultat from the u-boot

Booting Application @ 0x81080000


U-Boot 1.2.0 (Dec 13 2007 - 14:52:18)

I2C:   ready
DRAM:  256 MB
unknown vendor=0 Flash:  0 kB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
ARM Clock :- 297MHz
DDR Clock :- 297MHz
Hit any key to stop autoboot:  0
DM6467 EVM # printenv
bootcmd=nboot 80700000 0 a0000;bootm
bootdelay=3
baudrate=115200
bootfile="uImage"
serverip=192.168.1.100
ipaddr=192.168.1.201
nfshost=192.168.1.168
rootpath=/home/thierno/workdir/filesys
bootargs=console=ttyS0,115200n8 noinitrd rw ip=192.168.1.177:192.168.1.168::255.
255.255.0:dm6467:eth0: root=/dev/nfs nfsroot=192.168.1.168:/home/thierno/workdir
/filesys,nolock,tcp mem=120M
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:0e:99:02:b2:68

Environment size: 444/131068 bytes
DM6467 EVM # boot

Loading from NAND 128MiB 3,3V 8-bit, offset 0xa0000
   Image Name:   Linux-2.6.10_mvl401-davinci_evm
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1390892 Bytes =  1.3 MB
   Load Address: 80008000
   Entry Point:  80008000
## Booting image at 80700000 ...
   Image Name:   Linux-2.6.10_mvl401-davinci_evm
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1390892 Bytes =  1.3 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................
................................. done, booting the kernel.
Linux version 2.6.10_mvl401-davinci_evm (davincihd@psplinux.india.ti.com) (gcc v
ersion 3.4.3 (MontaVista 3.4.3-25.0.116.0601565 2006-09-20)) #1 Wed Oct 22 19:05
:32 IST 2008
CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Machine:
Memory policy: ECC disabled, Data cache writeback
DM6467
Built 1 zonelists
Kernel command line: console=ttyS0,115200n8 noinitrd rw ip=192.168.1.177:192.168
.1.168::255.255.255.0:dm6467:eth0: root=/dev/nfs nfsroot=192.168.1.168:/home/thi
erno/workdir/filesys,nolock,tcp mem=120M
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 120MB = 120MB total
Memory: 118528KB available (2391K code, 505K data, 152K init)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
spawn_desched_task(00000000)
desched cpu_callback 3/00000000
ksoftirqd started up.
desched cpu_callback 2/00000000
desched thread 0 started up.
NET: Registered protocol family 16
Registering platform device 'serial8250.0'. Parent at platform
DaVinci: 48 gpio irqs
DaVinci I2C DEBUG: 19:03:51 Oct 22 2008
Registering platform device 'i2c'. Parent at platform
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
musb_hdrc: version 2.2a/db-0.4.8 [cppi-dma] [host] [debug=0]
Registering platform device 'musb_hdrc'. Parent at platform
musb_hdrc: USB Host mode controller at c8000000 using DMA, IRQ 13
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
yaffs Oct 22 2008 19:03:27 Installing.
Registering platform device 'DavinciHD_vdce.2'. Parent at platform
Consumer IR INFO: CIR device registered successfully (Major = 253, Minor = 0)
Registering platform device 'cir.0'. Parent at platform
Consumer IR INFO: CIR IRQ 42 registered successfully
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
Registering platform device 'serial8250'. Parent at platform
ttyS0 at MMIO 0x1c20000 (irq = 40) is a ST16654
ttyS1 at MMIO 0x1c20400 (irq = 41) is a ST16650V2
io scheduler noop registered
io scheduler anticipatory registered
RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
Registering platform device 'ti_davinci_emac'. Parent at platform
TI DaVinci EMAC: MAC address is 00:0e:99:02:b2:68
TI DaVinci EMAC Linux version updated 5.0
TI DaVinci EMAC: Installed 1 instances.
netconsole: not configured, aborting
i2c /dev entries driver
Linux video capture interface: v1.00
Registering platform device 'vpif capture.1'. Parent at platform
Registering platform device 'vpif display.1'. Parent at platform
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
MUX: initialized ATAEN
hda: TOSHIBA MK4032GAX, ATA DISK drive
elevator: using anticipatory as default io scheduler
ide0 at 0xe10661f0-0xe10661f7,0xe10663f6 on irq 22
hda: max request size: 1024KiB
hda: 78140160 sectors (40007 MB), CHS=16383/255/63
 hda: hda1 hda2
    ide0: BM-DMA at 0xe1066000-0xe1066007, BIOS settings: hda:pio, hdb:pio
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
Registering Audio Devices. Total communication peripherals (ASP) : 2
Codec with ID = 0 on ASP = 0 is initialized.Using minor number :  3
Configuring the McASP as Master
Configuring the McASP 1 for DIT
SPDIF on ASP = 1 is initialized.Using minor number : 19
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: Complete:
      device=eth0, addr=192.168.1.177, mask=255.255.255.0, gw=255.255.255.255,
     host=dm6467, domain=, nis-domain=(none),
     bootserver=192.168.1.168, rootserver=192.168.1.168, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.168
Looking up port of RPC 100005/1 on 192.168.1.168
VFS: Mounted root (nfs filesystem).
Freeing init memory: 152K
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

Please help me

Thierno

  • 0
    TI__Mastermind 37340 points

    I noticed this happens right after mounting file system.  I have seen this in two ocations, one where the kernel and file-system where not compatible (e.g. came from different software releases) and the other where my kernel was corrupt (I was using tftp, so copying new kernel to my tftp directory fixed the issue).

     

  • 0 in reply to Juan Gonzales
    Intellectual 950 points

    This can also happen if you don't have the filesystem at the nfs mount point.

     

    Regard's

    RT

  • 0 in reply to Roh@n T@bish
    Prodigy 60 points

    This happen when file system is not properly exported. check the entry of file system export in /etc/export file and restart the nfs services.

  • 0 in reply to Mrugendra
    Expert 2315 points

    Hi everybody,

    I am getting exactly this problem but only after I do a power-up reset on my board that autoboots from NAND - following the wiki : How to create a Ramdisk with auto-run demo but at the point it panics I press reset and go into u-boot and flash my ramdisk to NAND again and if I boot then it is fine.  Do you have any idea why this can happen?  Is something actually writing to NANAD where my filesystem (in ramdisk.gz) is located and corrupting it as I assume none of the previous mentioned cases could be valid because it does boot up successfully on a hot restart after writing the NAND?  I did get the "console" error befor ebut fixed it by making sure the devices folder had the correct stuff in - forgotten the details though.  Below is the bottom of the kernel trying to boot:

     

    Switched to high resolution mode on CPU 0

    IP-Config: Complete:

    device=eth0, addr=196.1.6.110, mask=255.255.255.0, gw=196.1.6.1,

    host=196.1.6.110, domain=, nis-domain=(none),

    bootserver=196.1.6.107, rootserver=196.1.6.107, rootpath=

    RAMDISK: Compressed image found at block 0

    invalid compressed format (err=2)

    VFS: Mounted root (ext2 filesystem).

    Freeing init memory: 200K

    EXT2-fs error (device ram0): ext2_check_page: bad entry in directory #1609: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

    EXT2-fs error (device ram0): ext2_check_page: bad entry in directory #1537: rec_len is smaller than minimal - offset=1024, inode=0, rec_len=0, name_len=0

    Kernel panic - not syncing: No init found. Try passing init= option to kernel.

     

    Thanks, Jinh T.

  • 0 in reply to Jinh
    Expert 2315 points

    My apologies for posting this on the dm64x forum but I forgot to add in my previous post that I am using the evmdm365 board with DVSDK_2_10_01_18 with mvpro5.0.

    Any help would be appreciated. Thanks, Jinh T.

  • 0 in reply to Jinh
    Expert 2315 points

    I resolved this issue. Something wrote an extra directory into my filesystem that goes into ramdisk pushing it just over the boundary of what is written to NAND.

    Thanks, Jinh T.

  • 0
    Intellectual 665 points
    I solved these kind of many problem for many reasons,so Paste .config file. Then only we decide what is the problem..