Linux on V4FX100

Koss, Mike (Mission Systems) mike.koss at
Tue Jul 22 08:54:10 EST 2008

Hopefully beating the bushes in many arenas will help me ellict some

I have a system on a V4FX100 that is using both PPC405s. Each system is
an exact clone of the other, with some minor variations like how the
other's memory controller is mapped in. (They both can't be mapped to
0x0 :P).

I have a Linux 2.6.22 image (arch/ppc) that I've built that will run on
one and not the other. And by not run, I mean it boots successfully,
gives me a console, I run the applications and then in some point in
time in the near future the system crashes, semi-gracefully. The kernel
crashes and prints out the crash, hence the gracefully part, but its
dead in the water. What can an application that doesn't interface with
any special kernel things do to cause the crash? The applications use
only 'normal' things, no specific drivers (that haven't been completely
tested ;).

If I use a different software load, it runs fine with no problems. In
fact, I currently use it for running and developing other software.

Has anyone seen anything similar when using both PPCs? From what I can
tell it looks like it may be related to timers, but that's only guessing
and inconclusive. I don't have any extra timers (plb/opb/xps_timer)
built into either system.


Here's the crash output:
Oops: kernel access of bad area, sig: 11 [#1]
NIP: c002c960 LR: c002c960 CTR: 00000000
REGS: c1363d90 TRAP: 0300   Not tainted  (2.6.22-rc2-default)
MSR: 00021030 <ME,IR,DR>  CR: 48002488  XER: 20000055
DAR: 0000029b, DSISR: 00800000
TASK = c102f7b0[496] 'mmngr.exe' THREAD: c1362000
GPR00: c002c960 c1363e40 c102f7b0 c1363eb0 c01dd9e8 00000000 00000001
GPR08: 00368044 00000001 c103c580 00000000 e7433f04 10030ea8 ffffffff
GPR16: 7f9d1a04 65786563 10080000 7ff907f0 00000001 00000000 7ff90808
GPR24: 10002830 10015068 c1363f18 c1363eb0 00000000 00000000 0000027b
NIP [c002c960] __remove_hrtimer+0x3c/0x54
LR [c002c960] __remove_hrtimer+0x3c/0x54
Call Trace:
[c1363e40] [c002c960] __remove_hrtimer+0x3c/0x54 (unreliable)
[c1363e60] [c002c9d8] hrtimer_try_to_cancel+0x60/0x80
[c1363e70] [c002ca14] hrtimer_cancel+0x1c/0x3c
[c1363e80] [c0187af8] do_nanosleep+0x68/0xa4
[c1363ea0] [c002ce70] hrtimer_nanosleep+0x48/0x184
[c1363f10] [c002d044] sys_nanosleep+0x98/0xcc
[c1363f40] [c0002c30] ret_from_syscall+0x0/0x3c
Instruction dump:
90010024 7c9f2378 8004000c 7c7e1b78 7f801800 7cbd2b78 40be000c 480b0fed
907f000c 389f0008 7fc3f378 480b108d <93be0020> 80010024 bba10014
Oops: kernel access of bad area, sig: 11 [#2]
NIP: c00093bc LR: c00093d0 CTR: c0077d9c
REGS: c01efef0 TRAP: 0300   Not tainted  (2.6.22-rc2-default)
MSR: 00029030 <EE,ME,IR,DR>  CR: 24000082  XER: 00000055
DAR: 00000027, DSISR: 00000000
TASK = c01db980[0] 'swapper' THREAD: c01ee000
GPR00: 00000000 c01effa0 c01db980 00000000 c00088d4 00000000 c020b414
GPR08: 00000002 c01ee028 28002448 00000010 8a2c8992 ffffffff ffffffff
GPR16: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
GPR24: ffffffff ffffffff c0209000 c0200000 00000000 c01ee000 ffffffff
NIP [c00093bc] cpu_idle+0xc0/0xd8
LR [c00093d0] cpu_idle+0xd4/0xd8
Call Trace:
[c01effa0] [c00093d0] cpu_idle+0xd4/0xd8 (unreliable)
[c01effb0] [c0185f5c] rest_init+0x50/0x60
[c01effc0] [c01f09e4] start_kernel+0x2b4/0x2c8
[c01efff0] [c000225c] start_here+0x44/0xb0
Instruction dump:
60008000 7c000124 39200010 381f0028 7d600028 7d6b4b78 7c00022c 7d60012d
40a2fff0 4800000c 7c210b78 7ffffb78 <801f0028> 70090008 4182ff70
Kernel panic - not syncing: Attempted to kill the idle task!
Rebooting in 180 seconds..<NULL>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Linuxppc-embedded mailing list