Ramdisk: kernel panic...

Ramdisk: kernel panic...

[Prasad, Siva]

Hi,

I am trying to bring up Linux_2_4_Devel on a 750 custom board. Using
powerboot as the bootloader.

I was able to get until mounting the ramdisk and freeing both 'initrd' and
'unused' memory. After that when it tries to execute the below statement, I
get kernel PANIC. I commented the other 'init' execve's, to at least bring
up the system first.

	execve("/bin/sh",argv_init,envp_init);

Also looks like do_execve() in fs/exec.c returns fine with value "0". But in
the end I get kernel panic.

Actually I am using simple ramdisk (simple-ramdisk.image.gz). I don't see
the 'echo's of linuxrc getting printed on the console either. But following
kernel printk's are printed fine on the console.

Does this has anything to do with interrupts what so ever?.

I am giving the boot trace below. It would be great if any one can help me
out with this problem.

Thanks in advance
-- Siva


PowerBoot> go 400000
loaded at:     00400000 004091C4
relocated to:  00800000 008091C4
zimage at:     00406067 00488D64
relocated to:  0080A000 0088CCFD
initrd at:     00488D64 00513818
relocated to:  0088D000 00917AB4
avail ram:     00400000 00800000

Linux/PPC load: console=ttyS0,9600 root=/dev/ram0 rw
Uncompressing Linux...done.
Now booting the kernel
wTotal memory = 256MB; using 1024kB for hash table (at c0200000)
Linux version 2.4.10 (prasad@siva) (gcc version 2.95.3 20010315 (release))
#1 Fr
i Sep 28 11:24:33 PDT 2001
Host bridge in Agent mode
Force PCore port (C) 2001 MontaVista Software, Inc. (source@mvista.com)
On node 0 totalpages: 65536
zone(0): 65536 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=ttyS0,9600 root=/dev/ram0 rw
TODC real-time-clock was stopped. Now starting...
time_init: decrementer frequency = 945.000099 MHz
Warning: real time clock seems stuck!
Calibrating delay loop... 30198.98 BogoMIPS
Memory: 254780k available (860k kernel code, 372k data, 180k init, 0k
highmem)
Dentry-cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
Memory resource not set for host bridge 0
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming transparent
PCI: Cannot allocate resource region 0 of device 00:00.0
PCI: Cannot allocate resource region 1 of device 00:0b.0
PCI: Failed to allocate resource 0(10000000-1000ffff) for 00:00.0
PCI: Failed to allocate resource 1(10000000-10000fff) for 00:00.0
PCI: I/O Region 00:0b.0/-1 too large (2048 bytes)
PCI: I/O Region 00:0b.0/-1 too large (2048 bytes)
PCI: Failed to allocate resource 1(1000-17ff) for 00:0b.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
SERIAL_PCI en
abled
block: 128 slots per queue, batch=16
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 554k freed
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 180k init
Kernel panic: Attempted to kill init!
 <0>Rebooting in 180 seconds..


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Ramdisk: kernel panic...

[Mark Hatle]

> Freeing unused kernel memory: 180k init
> Kernel panic: Attempted to kill init!
>  <0>Rebooting in 180 seconds..

The message indicates it was unable to execute the init program.  Do you
have the required libraries in your ramdisk?  are they for the right
machine.. (remember cachelines are different between 8xx and the other
PPC processors.)

There are a lot of things that can cause init to bail, sigsegv, sigill,
etc, missing/bad library, etc..

--Mark

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Ramdisk: kernel panic...

[Prasad, Siva]

Hi,

I used simple-ramdisk.image.gz (indicated in archives of this list).
It has the following libraries in /lib directory.
 ld.so.1
 libc-1.99.so
 libc.so.6 -> libc-1.99.so
 libcrypt.so.1
 libproc.so.1.2.6
 libtermcap.so.2 -> libtermcap.so.2.0.8
 libtermcap.so.2.0.8

I thought of trying out with montavista's libraries and I built my own
ramdisk with following files replaced in the ramdisk /lib directory. All
these are built for 7xx processor (from CDK 1.2 CD of HHL).
 ld-2.1.3.so
 ld.so.1 -> ld-2.1.3.so
 libc-2.1.3.so
 libc.so.6 -> libc-2.1.3.so
 libcrypt-2.1.3.so
 libcrypt.so.1 ->  libcrypt-2.1.3.so
 libproc.so.2.0.0
 libproc.so ->  libproc.so.2.0.0
 libtermcap.so.2.0.8
 libtermcap.so.2 ->  libtermcap.so.2.0.8

 similarly I replaced bin/sh also.

Still I am getting the same problem. Is there any other libraries that I
need to add ither than the above. Please let me know.

-- Siva


> -----Original Message-----
> From: Mark Hatle [mailto:fray@mvista.com]
> Sent: Friday, September 28, 2001 4:03 PM
> To: Prasad, Siva
> Cc: linuxppc-embedded@lists.linuxppc.org
> Subject: Re: Ramdisk: kernel panic...
>
>
> > Freeing unused kernel memory: 180k init
> > Kernel panic: Attempted to kill init!
> >  <0>Rebooting in 180 seconds..
>
> The message indicates it was unable to execute the init
> program.  Do you
> have the required libraries in your ramdisk?  are they for the right
> machine.. (remember cachelines are different between 8xx and the other
> PPC processors.)
>
> There are a lot of things that can cause init to bail,
> sigsegv, sigill,
> etc, missing/bad library, etc..
>
> --Mark
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Ramdisk: kernel panic...

[Mark Hatle]

"Prasad, Siva" wrote:

> ...
>I thought of trying out with montavista's libraries and I built my own
>ramdisk with following files replaced in the ramdisk /lib directory. All
>these are built for 7xx processor (from CDK 1.2 CD of HHL).
> ...
>
> > > Freeing unused kernel memory: 180k init
> > > Kernel panic: Attempted to kill init!
> > >  <0>Rebooting in 180 seconds..
> >
> > The message indicates it was unable to execute the init
> > program.  Do you

I would suggest you get HHL 2.0 from our ftp site and try that.  The
easiest thing for you to try is "/bin/sash" as the shell or
"ash.static".  Just copy them in as /bin/sh.  (These do not use
libraries so you can assure they are correct.)

If that stuff comes up, then you have library issues and will have to
resolve those seperately.  (FYI I'd stay away from CDK 1.2 at this
point, it's old and there is a known path issue w/ the glibc.. i.e. it
want to live in /opt/hardhat/.../.../target/lib instead of /lib...)

--Mark

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Ramdisk: kernel panic...

[Prasad, Siva]

Hi,

I am getting the same "Kernel panic" message still even after using
'ash.static' in place of '/bin/sh'. So, I guess this is not a library
problem. Then what is it?... and how to go about debugging this problem.

I just want to try out '/bin/sash' also. How to get that code which is in
professional version of HHL 2.0.

I am just calling
execve("/bin/sh", ...
and not any of the init's.
Found that 'do_execve' returns fine, after that kernel panics.

Using Linux_2_4_devel source as on Sep 26th. For PPC750 board. Using Force's
PowerBoot as boot loader. Using 'PowerCore' option for building.

Any suggestion would be greatly appreciated.

Thanks in advance.

-- Siva


> -----Original Message-----
> From: Mark Hatle [mailto:fray@mvista.com]
> Sent: Monday, October 01, 2001 7:06 PM
> To: Prasad, Siva
> Subject: Re: Ramdisk: kernel panic...
>
>
> "Prasad, Siva" wrote:
> >
> > Hi Mark,
> >
> > Thanks a lot for the help and time that you had extended.
> > As you suggested, I had installed HHL2.0 (for Sandpoint
> since it uses 7xx).
> >
> > In the directory /hardhat/devkit/ppc/7xx/target/bin, I
> don't see "sash". Can
> > you please point me to exact place where I can find this
> file and use that
> > in my ramdisk.
> >
> > "ash.static" is present in the directory. Can I copy that
> as "/bin/sh"???.
> > Do I have to copy any libraries too along with that???.
> >
> > Thanks for the patience.
> >
> > -- Siva
>
>
> You can copy ash.static as "/bin/sh".  There are no libraries required
> for it to work.
>
> I just realized that sash is not part of Journeyman, but our
> professional kit.  So ash.static will have to do.  If you can boot up
> and into ash.static then your system is working.. (more or less...)
>
> At that point you can be more adventerous and copy regular apps and
> their associated libraries and try that.
>
> --Mark
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/