* kernel panic...........
@ 2001-06-28 12:47 karanth karanth
0 siblings, 0 replies; 3+ messages in thread
From: karanth karanth @ 2001-06-28 12:47 UTC (permalink / raw)
To: linuxppc-embedded
Hai,
I have been using mpc823 with 2.2.14 kernel, below shows the output message of the kernel panic.
Boot
loaded at : 00000000 000141B4
board data at : 00202344 00202374
zimage at : 0038A000 0007E0B1
avail ram : 002141B4 0038A000
Linux/PPC load: console=ttyS0, 19200n8!
Uncompressing Linux...done
hold_residual=00600100
Now booting the kernel
###########################
NIP 00000000 XER: E000B97F LR: C0006564 REGS: c00f7e50 TRAP: 0400
MSR: 08209032 EE: 1 PR: 0 FP:0 ME: 1 IR/DR: 11
TASK = c00f6000[1] 'swapper' mm->pgd c017f000 Last syscall = -1
last math 00000000
GPR00: 00000078 C00F7F40 C00F6000 00000E00 00000000 00000E000 00000000 C00CE857
GPR08: 00000024 C00D0000 FF002068 C00B3AC8 956DF039 000000000 00000000 00100000
GPR16: 04000000 FF000000 0000006E 00000000 00020000 00202344 00000000 02008000
GPR24: 00200000 00080080 00000000 00600015 00600000 00000000 C00C0000 C00C0000
Call backtrace:
00000000
Instruction DUMP:
kernel panic: kernel access of bad area pc 0 lr c0006564 address 0 tst swapper/1
Rebooting in 180 secound ...
########################
can anybody tell me what could be the reason of the crash.
Thanking you,
kk.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Kernel panic
@ 2002-10-29 20:06 Aman
2002-10-30 19:57 ` Matt Porter
0 siblings, 1 reply; 3+ messages in thread
From: Aman @ 2002-10-29 20:06 UTC (permalink / raw)
To: linuxppc embedded
Hi All
I am trying to build linux image with ramdisk and download to the PPC 440GP
evalkit. Earlier the filesystem was using nfs mount, now I hv builded a
zImage.initrd with ramdisk.image [I havent compressed the ramdisk image]. To
build the ramdisk, I used the procedure defined by HHL.. I defined the
ramdisk size as 8MB. However when I booted with the image built. I am
getting a kernel panic error. I have pasted the output below. One question
, how should we decide about the files to be loaded in ramdisk which will
be needed by kernel image.
Thanking you in advance.
Regards
Aman
Loading file "zImage.initrd" ...
Sending tftp boot request ...
Transfer Complete ...
Loaded successfully ...
Entry point at 0x1000000 ...
loaded at: 01000000 018821BC
zimage at: 01005950 0107E2C9
initrd at: 0107F000 0187F000
avail ram: 00400000 00800000
Linux/PPC load: root=/dev/ram ramdisk_size=8192
Uncompressing Linux...done.
Now booting the kernel
Linux version 2.4.17_mvl21-ebony (root@hardhat) (gcc version 2.95.3 20010315
(release/MontaVista)) #18 Tue Oct 29 19:28:19 IST 2002
IBM Ebony port (C) 2002 MontaVista Software, Inc. (source@mvista.com)
On node 0 totalpages: 32768
zone(0): 4096 pages.
zone(1): 28672 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/ram ramdisk_size=8192
Calibrating delay loop... 599.65 BogoMIPS
Memory: 119264k available (876k kernel code, 344k data, 68k init, 0k
highmem)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Disabling the Out Of Memory Killer
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
SERIAL_PCI enabled
ttyS00 at 0xfdfe9200 (irq = 0) is a 16550A
ttyS01 at 0xfdfe8300 (irq = 1) is a 16550A
block: 128 slots per queue, batch=32
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
eth0: Phy @ 0x8, type Am79c875A (0x00225541)
Reset ethernet interfaces
eth1: Phy @ 0x9, type Am79c875A (0x00225541)
Reset ethernet interfaces
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
eth0: IBM EMAC: link up, 100 Mbps Full Duplex, auto-negotiation complete.
eth0: IBM EMAC: MAC 00:04:ac:e3:1b:b5.
eth0: IBM EMAC: open completed
eth1: IBM EMAC: link up, 10 Mbps Half Duplex.
eth1: IBM EMAC: MAC 00:04:ac:e3:1b:b6.
eth1: IBM EMAC: open completed
Sending BOOTP requests . OK
IP-Config: Got BOOTP answer from 192.168.13.242, my address is
192.168.13.246
IP-Config: Complete:
device=eth0, addr=192.168.13.246, mask=255.255.255.0,
gw=255.255.255.255,
host=192.168.13.246, domain=, nis-domain=(none),
bootserver=192.168.13.242, rootserver=192.168.13.242,
rootpath=/hdb/mountpt
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 8192 blocks [1 disk] into ram disk... done.
Freeing initrd memory: 8192k freed
Kernel panic: VFS: Unable to mount root fs on 01:00
<0>Rebooting in 180 seconds..
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Kernel panic
2002-10-29 20:06 Kernel panic Aman
@ 2002-10-30 19:57 ` Matt Porter
0 siblings, 0 replies; 3+ messages in thread
From: Matt Porter @ 2002-10-30 19:57 UTC (permalink / raw)
To: Aman; +Cc: linuxppc embedded
On Wed, Oct 30, 2002 at 01:36:00AM +0530, Aman wrote:
>
> Hi All
>
> I am trying to build linux image with ramdisk and download to the PPC 440GP
> evalkit. Earlier the filesystem was using nfs mount, now I hv builded a
> zImage.initrd with ramdisk.image [I havent compressed the ramdisk image]. To
> build the ramdisk, I used the procedure defined by HHL.. I defined the
> ramdisk size as 8MB. However when I booted with the image built. I am
> getting a kernel panic error. I have pasted the output below. One question
> , how should we decide about the files to be loaded in ramdisk which will
> be needed by kernel image.
>
> Thanking you in advance.
> Regards
> Aman
>
>
> Loading file "zImage.initrd" ...
> Sending tftp boot request ...
> Transfer Complete ...
> Loaded successfully ...
> Entry point at 0x1000000 ...
> loaded at: 01000000 018821BC
> zimage at: 01005950 0107E2C9
> initrd at: 0107F000 0187F000
> avail ram: 00400000 00800000
>
> Linux/PPC load: root=/dev/ram ramdisk_size=8192
> Uncompressing Linux...done.
> Now booting the kernel
> Linux version 2.4.17_mvl21-ebony (root@hardhat) (gcc version 2.95.3 20010315
^^^^^^^^^^^^^^^^^^
Basic questions like this on a vendor-specific kernel (and a
"procedure defined by HHL") might be better answered by contacting
your vendor's support arm.
I have no problem with initrds using a ramdisk.image.gz created via
"dd if=/dev/zero ...", mke2fs, and populated via a loopback mount.
Looks like you have ramdisk size set properly...make sure the
filesytem (ext2) is built-in.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-10-30 19:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-10-29 20:06 Kernel panic Aman
2002-10-30 19:57 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2001-06-28 12:47 kernel panic karanth karanth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).