mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>
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 23:19:09 +0200	[thread overview]
Message-ID: <6bffcb0e0608081419p4430b5cei7b4aa990cd0d4422@mail.gmail.com> (raw)
In-Reply-To: <20060808140511.def9b13c.akpm@osdl.org>

On 08/08/06, Andrew Morton <akpm@osdl.org> wrote:
> On Tue, 8 Aug 2006 22:29:03 +0200
> "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com> wrote:
>
> > Hi Andrew,
> >
> > On 08/08/06, akpm@osdl.org <akpm@osdl.org> wrote:
> > > The mm snapshot broken-out-2006-08-08-00-59.tar.gz has been uploaded to
> > >
> > >    ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2006-08-08-00-59.tar.gz
> > >
> > > It contains the following patches against 2.6.18-rc4:
> >
> > It appears very early. 2.6.18-rc3-mm2 was fine.
> >
> > DWARF2 unwinder stuck at error_code+0x39/0x40
>
> The novelty of this thing has worn off.  Guys, please let's not release 2.6.18 in
> this state.
>
> > Leftover inexact backtrace
> > [<c0104194>] show_stack_log_lvl+0x8c/0x97
> > [<c0104320>] show_registers+0x181/0x215
> > [<c0104576>] die+0x1c2/0x2dd
> > [<c0117419>] do_page_fault+ox410/0x4f3
> > [<c02f5271>] error_code+0x39/0x40
> > [<c0104194>] show_stack_log_lvl+0x8c/0x97
> > [<c0104320>] show_registers+0x181/0x215
> > [<c0104576>] die+0x1c2/0x2dd
> > [<c0117419>] do_page_fault+0x410/0x4f3
> > [<c02f5271>] error_code+0x39/0x40
> > [<c047b609>] start_kernel+0x224/0x3a2
> > [<c0100210>] 0xc0100210
> > Code: 00 39 .......
> > EIP:[<c01040ca>] show_trace_log_lvl+0x11b/0x159 SS:ESP 0068:c0479e74
> > <0> Kernel panic - not syncing: Attempted to kill idle task!
> >
> > http://www.stardust.webpages.pl/files/mm/2.6.18-rc4-mm1/mm-config
> >
>
> So I guess the dwarf unwinder oopsed and wrecked our oops.  Perhaps you'll
> get better info with CONFIG_UNWIND_INFO=n, CONFIG_STACK_UNWIND=n.
>
> Now, _perhaps_ it oopsed at "[<c047b609>] start_kernel+0x224/0x3a2".

eghm... typo.
[<c047d609>]

>  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();

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

  reply	other threads:[~2006-08-08 21:19 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 ` Michal Piotrowski
2006-08-08 21:05   ` Andrew Morton
2006-08-08 21:19     ` Michal Piotrowski [this message]
2006-08-08 21:37       ` Andrew Morton
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=6bffcb0e0608081419p4430b5cei7b4aa990cd0d4422@mail.gmail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®