Messages in this thread | | | Date | Wed, 9 Aug 2006 00:11:38 +0200 | From | "Michal Piotrowski" <> | Subject | Re: mm snapshot broken-out-2006-08-08-00-59.tar.gz uploaded |
| |
On 08/08/06, Andrew Morton <akpm@osdl.org> wrote: > On Tue, 8 Aug 2006 23:19:09 +0200 > "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com> wrote: > > > > You > > > can look these things up in gdb or using addr2line, provided you have > > > CONFIG_DEBUG_INFO=y. > > > > > > > > > > (gdb) list *0xc047d609 > > 0xc047d609 is in start_kernel (/usr/src/linux-work1/init/main.c:577). > > 572 cpuset_init_early(); > > 573 mem_init(); > > 574 kmem_cache_init(); > > 575 setup_per_cpu_pageset(); > > 576 numa_policy_init(); > > 577 if (late_time_init) > > 578 late_time_init(); > > 579 calibrate_delay(); > > 580 pidmap_init(); > > 581 pgtable_cache_init(); > > hm. > > - Try to get the full oops record,
BUG: unable to handle kernel paging request at virtual address 01020304 printing eip: c041b95c *pde= 00000000 Oops: 0000 [#1] 4K_STACK PREEMPT SMP last sysfs file: Modules linked in: CPU 0 EIP: 0060: [<c041b95c>] Not tainted VLI EFLAGS: 00010202 EIP is at kmem_cache_init+0x389/0x3f0 [..] Call Trace: [<c0104063>] show_stack_log_lvl+0x8c/0x97 [<c010422b>] show_registers+0x181/0x215 [<c0104481>] die+0x1c2/0x2dd [<c0117419>] do_page_fault+0x410/0x4f3 [<c02f40a1>] error_code+0x39/0x40 [<c040b604>] start_kernel+0x21f/0x39d [<c0100210>] 0xc0100210 [..] EIP: [<c041b95c>] kmem_cache_init+0x389/0x3f0 SS:ESP0068:c0409fc4 <0> Kernel panic - not syncing: Attempted to kill idle task!
(gdb) list *0xc041b95c 0xc041b95c is in kmem_cache_init (/usr/src/linux-work1/mm/slab.c:714). 709 lockdep_set_class(&l3->list_lock, &on_slab_l3_key); 710 alc = l3->alien; 711 if (!alc) 712 continue; 713 for_each_node(r) { 714 if (alc[r]) 715 lockdep_set_class(&alc[r]->lock, 716 &on_slab_alc_key); 717 } 718 }
> find out what the faulting address is > ("unable to handle kernel paging request at virtual address xxxx") and > see if that lines up with any symbol in .vmlinux.
Did you mean "list 01020304"?
> > - Might be something bad in numa_policy_init(). I assume you don't have > CONFIG_NUMA=y ;)
No, I don't.
> > > This'll be hard to diagnose without a full oops trace. >
Regards, Michal
-- Michal K. K. Piotrowski LTG - Linux Testers Group (http://www.stardust.webpages.pl/ltg/wiki/) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |