Subject: Re: Re: my cpu is MPC860, kernel version is 2.6.20.14, the kernel startinfo in the mail. why does the kernel panic?

From: "poorbeyond" <[email-masked]>
Date: Thu, 9 Aug 2007 23:27:17 +0800

it's now print below. it's too late here, sleep....

thanks

^_^=>bootm 300000

## Booting image at 00300000 ...
   Image Name:   Linux-2.6.20.14
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    839246 Bytes = 819.6 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Current stack ends at 0x01D5DB10 => set upper limit to 0x00800000
No initrd
## Transferring control to Linux (at address 00000000) ...
bootm1
Linux version 2.6.20.14 ([email-masked]) (gcc version 4.0.0 (DENX ELDK 4.0 4.0.0)) #2 Thu Aug 9 23:26:51 CST 2007
I2C/SPI/SMC1 microcode patch installed.
Zone PFN ranges:
  DMA             0 ->     2048
  Normal       2048 ->     2048
early_node_map[1] active PFN ranges
    0:        0 ->     2048
Built 1 zonelists.  Total pages: 2032
Kernel command line: 
PID hash table entries: 32 (order: 5, 128 bytes)
Decrementer Frequency = 187500000/60
Warning: real time clock seems stuck!
cpm_uart: console: compat mode
Dentry cache hash table entries: 1024 (order: 0, 4096 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory: 6164k available (1252k kernel code, 604k data, 84k init, 0k highmem)
Mount-cache hash table entries: 512
Zq001: start_kernel
------------[ cut here ]------------
Badness at arch/ppc/kernel/dma-mapping.c:345
Call Trace:
[00213E60] [00008BA0]  (unreliable)
[00213E90] [000A1370] 
[00213EA0] [0000388C] 
[00213ED0] [0000304C] 
[00213F90] [001A29B4] 
[00213FA0] [000022B0] 
[00213FF0] [00004A80] 
NET: Registered protocol family 16
Generic PHY: Registered new driver
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 256 (order: 0, 4096 bytes)
TCP bind hash table entries: 128 (order: -1, 2560 bytes)
TCP: Hash tables configured (established 256 bind 128)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(4294836223.218:1): initialized
audit: cannot initialize inotify handle
io scheduler noop registered (default)
Serial: CPM driver $Revision: 0.02 $
cpm_uart: WARNING: no UART devices found on platform bus!
cpm_uart: the driver will guess configuration, but this mode is no longer supported.
ttyCPM0 at MMIO 0xff000a80 (irq = 20) is a CPM UART
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
LXT970: Registered new driver
LXT971: Registered new driver
fs_enet.c:v1.0 (Aug 8, 2005)
------------[ cut here ]------------
kernel BUG at arch/ppc/kernel/dma-mapping.c:233!
Oops: Exception in kernel mode, sig: 5 [#1]
NIP: 00005584 LR: 00005538 CTR: 00000000
REGS: 00213e90 TRAP: 0700   Not tainted  (2.6.20.14)
MSR: 00029032 <EE,ME,IR,DR>  CR: 55222253  XER: A000247F
TASK = 00210ba0[1] 'swapper' THREAD: 00212000
GPR00: 00400165 00213F40 00210BA0 001EDD64 00000000 00000BDA 00269FFC 00000000 
GPR08: 00160648 00000001 00401000 00400164 00000000 41082001 02000000 00000001 
GPR16: 00000000 01FFFA54 FFFFFFFF 00000000 00800000 007FFF00 01FFAA14 00213F78 
GPR24: 005FF000 00160000 00000000 001EDD40 00001000 001E6000 00231220 001EDD20 
Call Trace:
[00213F40] [00005508]  (unreliable)
[00213F70] [001A3578] 
[00213FA0] [000022B0] 
[00213FF0] [00004A80] 
Instruction dump:
38630658 4813226d 7fc3f378 48050eb5 7fe3fb78 7f44d378 48041b35 48000078 
801d0000 5400066e 3160ffff 7d2b0110 <0f090000> 38000400 7d20f828 7d290378 
Kernel panic - not syncing: Attempted to kill init!
 <0>Rebooting in 180 seconds..

poorbeyond
2007-08-09

发件人： Scott Wood
发送时间： 2007-08-07 05:24:12
收件人： Dan Malek
抄送： poorbeyond; Linux-ppc mail list
主题： Re: my cpu is MPC860, kernel version is 2.6.20.14, the kernel startinfo in the mail. why does the kernel panic?

Dan Malek wrote:
> On Aug 6, 2007, at 8:52 AM, Scott Wood wrote:
> 
> > It wouldn't surprise me if the 8xx code has issues with PREEMPT; try
> > turning it off for now.
> 
> 
> What is your reason that 8xx would be any different?

It's just a suspicion based on my dealings with the CPM code, and the 
fact that the crash appeared to happen in the CPM ethernet driver.  It 
could be wrong, but it doesn't hurt to try without PREEMPT and see if 
the problem remains.

-Scott