From: Andrew Morton <akpm@osdl.org>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Andi Kleen" <ak@muc.de>,
"Jan Beulich" <jbeulich@novell.com>
Subject: Re: mm snapshot broken-out-2006-08-08-00-59.tar.gz uploaded
Date: Tue, 8 Aug 2006 14:37:51 -0700 [thread overview]
Message-ID: <20060808143751.42f8d87c.akpm@osdl.org> (raw)
In-Reply-To: <6bffcb0e0608081419p4430b5cei7b4aa990cd0d4422@mail.gmail.com>
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, 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.
- Might be something bad in numa_policy_init(). I assume you don't have
CONFIG_NUMA=y ;)
This'll be hard to diagnose without a full oops trace.
next prev parent reply other threads:[~2006-08-08 21:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200608080800.k7880noU028915@shell0.pdx.osdl.net>
2006-08-08 20:29 ` mm snapshot broken-out-2006-08-08-00-59.tar.gz uploaded Michal Piotrowski
2006-08-08 21:05 ` Andrew Morton
2006-08-08 21:19 ` Michal Piotrowski
2006-08-08 21:37 ` Andrew Morton [this message]
2006-08-08 22:11 ` Michal Piotrowski
2006-08-08 23:24 ` Michal Piotrowski
2006-08-08 23:42 ` Andrew Morton
2006-08-09 0:01 ` Michal Piotrowski
2006-08-09 6:21 ` Ravikiran G Thirumalai
2006-08-09 13:21 ` Michal Piotrowski
2006-08-09 1:43 ` Andi Kleen
2006-08-09 12:49 ` Michal Piotrowski
2006-08-09 1:42 ` Andi Kleen
2006-08-09 14:20 ` Michal Piotrowski
2006-08-09 22:44 ` Michal Piotrowski
2006-08-10 6:35 ` Jens Axboe
2006-08-10 13:06 ` Michal Piotrowski
2006-08-10 13:09 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060808143751.42f8d87c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@muc.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox