On 08/18/2011 05:10 PM, Jason Kwon wrote:
Attempting to boot a 3.0.3 kernel on a CN58XX board produced the following oops: CPU 4 Unable to handle kernel paging request at virtual address 0000000001c00000, epc == ffffffff811aa9f4, ra == ffffffff811aaa98 Oops[#1]: Cpu 4 $ 0 : 0000000000000000 0000000010008ce0 ffffffff821d2b80 0000000001c00000 $ 4 : 0000000001c00038 000000000000017c 0000000000080000 0000000000080072 $ 8 : 0000000000000008 0000000000000002 0000000000000003 a800000002284520 $12 : 0000000000000002 ffffffff8186ee80 ffffffffffffff80 0000000000000030 $16 : 0000000000080072 0000000000000001 0000000001bfa8f0 0000000001bfa928 $20 : a800000003aff8f0 00000000000f0000 ffffffff8186ee80 ffffffff821d2a80 $24 : 0000000000000001 0000000000000038 $28 : a80000041fc48000 a80000041fc4bd90 fffffffffffffffc ffffffff811aaa98 Hi : 0000000000000000 Lo : 0000000000000000 epc : ffffffff811aa9f4 setup_per_zone_wmarks+0x19c/0x2d8 Not tainted ra : ffffffff811aaa98 setup_per_zone_wmarks+0x240/0x2d8 Status: 10008ce2 KX SX UX KERNEL EXL Cause : 40808408 BadVA : 0000000001c00000 PrId : 000d0301 (Cavium Octeon+) Modules linked in: Process swapper (pid: 1, threadinfo=a80000041fc48000, task=a80000041fc44038, tls=0000000000000000) Stack : 0000000000000000 000000000006f75d ffffffff8186eec0 0000000000000001 0000000000000547 ffffffff81825598 ffffffff81a80000 ffffffff818b3e68 ffffffff818a40ac 0000000000000000 ffffffff81a80000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ffffffff818a40f0 ffffffff81a80000 ffffffff81100438 ffffffff818b4198 ffffffff818b3e68 ffffffff818b46c8 0000000000000000 0000000000000000 ffffffff818721d0 0000000000000000 0000000000000000 0000000000000000 ffffffff81109bb0 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ffffffff818720f8 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ... Call Trace: [<ffffffff811aa9f4>] setup_per_zone_wmarks+0x19c/0x2d8 [<ffffffff818a40f0>] init_per_zone_wmark_min+0x44/0xe0 [<ffffffff81100438>] do_one_initcall+0x38/0x160 [<ffffffff818721d0>] kernel_init+0xd8/0x178 [<ffffffff81109bb0>] kernel_thread_helper+0x10/0x18
It appears to be related to use of physical memory above the 16GB barrier. You could try reducing the amount of memory allocated to the kernel by passing 'mem=1700M' on the kernel command line.
David Daney
