[ELDK] Problems in kernel init while using busybox on ELDK 4.2

[Diptopal Basu]

Hi Wolfgang ,

    I have tried to answer some of the questions ,

Regards
Diptopal

On Wed, May 27, 2009 at 3:25 PM, Wolfgang Denk <wd at denx.de> wrote:

> Dear Diptopal Basu,
>
> In message <bd97640b0905270244i6c85d4a1v994ba0acc129415 at mail.gmail.com>
> you wrote:
> >
> > I linked busybox statically because I use "mklibs to generate dynamic
> shared
> > libs in /lib...and I wanted to remove mklibs from "possible cause of
> error".
>
> I have no idea what "mklibs" might be, but you are actually
> introducing more sources of errors here.


Yes that's why in this case  I did not use mklibs and statically compiled
the busybox . What I meant above was that since there is a possibility of
introduction of error using mklibs I compiled the busybox statically .

>
>
> >    The kernel works fine if compiled with ELDK 4.1 . I am attaching a
>
> And what does this working kernel, compiled with ELDK 4.1, do when you
> boot it with the ramdisk image with your  busybox 1.13.4 compiled with
> ELDK 4.2 and linked statically?


The kernel crashes with a kernel panic .

>
>
> > snapshot of the kernel panic here . I am suspecting that its a busybox
>
> Argh... Why don't you use a serial console so you can just copy &
> paste the text? Sending a screen shot is *strongly* discouraged and
> usually useless.


I am pasting the message generated by a successful kernel boot up which was
compiled with ELDK 4.1 . I am also attaching the cpio archive which has been
used for this image .

$ qemu-system-arm -M versatilepb -m 16 -serial stdio -kernel
arch/arm/boot/zImage -append "console=ttyAMA0,115200"
Uncompressing
Linux.........................
........................................................................
done, booting the kernel.
Linux version 2.6.26.5 (pierre at localhost.localdomain) (gcc version 4.0.0
(DENX ELDK 4.1 4.0.0)) #16 Fri May 29 11:10:44 CEST 2009
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00093177
Machine: ARM-Versatile PB
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-through cache
CPU0: I cache: 4096 bytes, associativity 4, 32 byte lines, 32 sets
CPU0: D cache: 65536 bytes, associativity 4, 32 byte lines, 512 sets
Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 4064
Kernel command line: console=ttyAMA0,115200
PID hash table entries: 64 (order: 6, 256 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory: 16MB = 16MB total
Memory: 13128KB available (2072K code, 156K data, 840K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 328 bytes
NET: Registered protocol family 16
PCI core found (slot 11)
PCI: bus0: Fast back to back transfers disabled
PCI map irq: slot 0, pin 1, devslot 12, irq: 27
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP reno registered
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
CLCD: unknown LCD panel ID 0x00001000, using VGA
CLCD: Versatile hardware, VGA display
Clock CLCDCLK: setting VCO reg params: S=1 R=99 V=98
Console: switching to colour frame buffer device 80x30
Serial: AMBA PL011 UART driver
dev:f1: ttyAMA0 at MMIO 0x101f1000 (irq = 12) is a AMBA/PL011
console [ttyAMA0] enabled
dev:f2: ttyAMA1 at MMIO 0x101f2000 (irq = 13) is a AMBA/PL011
dev:f3: ttyAMA2 at MMIO 0x101f3000 (irq = 14) is a AMBA/PL011
fpga:09: ttyAMA3 at MMIO 0x10009000 (irq = 38) is a AMBA/PL011
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico at cam.org>
eth0: SMC91C11xFD (rev 1) at c180a000 IRQ 25 [nowait]
eth0: Ethernet addr: 52:54:00:12:34:56
mice: PS/2 mouse device common for all mice
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
Freeing init memory: 840K
init started: BusyBox v1.11.2 (2009-05-29 10:56:30 CEST)
starting pid 167, tty '': '/etc/init.d/rcS'

+--------------------------+
| Busybox + QEMU ARM9 demo |
|       GLIBC version      |
+--------------------------+

input: AT Raw Set 2 keyboard as /class/input/input0
 00:00:01 up 0 min, load average: 0.00, 0.00, 0.00

Please press Enter to activate this console. input: ImExPS/2 Generic
Explorer Mouse as /class/input/input1

starting pid 176, tty '': '-/bin/sh'
/ #


>
>
> > problem because the init is handled by busybox  and that's where the
> kernel
> > is crashing .
> >
> > I will be providing you with more details .
>
> You should test your ramdisk image in a working envrionment first,
> like with root file system mounted over NFS. Then mount the ramdisk
> image, and try if you can "chroot" into it. This is much easier to
> debug.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> To be awake is to be alive.        - Henry David Thoreau, in "Walden"
>