From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: sam@ravnborg.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: backtrace symbols are bolixed...
Date: Fri, 19 Jun 2009 01:01:51 -0700 (PDT) [thread overview]
Message-ID: <20090619.010151.83084255.davem@davemloft.net> (raw)
In-Reply-To: <20090619073053.GA5445@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Fri, 19 Jun 2009 09:30:53 +0200
> * David Miller <davem@davemloft.net> wrote:
>
>> Sometime in the last day or so backtrace symbol printouts
>> have become useless:
>>
>> [ 0.000000] WARNING: at mm/bootmem.c:535 __stop_notes+0xbb10/0x1d660()
>> [ 0.000000] Modules linked in:
>> [ 0.000000] Call Trace:
>> [ 0.000000] [00000000008611b4] __stop_notes+0xbb10/0x1d660
>> [ 0.000000] [000000000086195c] __stop_notes+0xc2b8/0x1d660
>> [ 0.000000] [0000000000861a28] __stop_notes+0xc384/0x1d660
>> [ 0.000000] [0000000000858678] __stop_notes+0x2fd4/0x1d660
>> [ 0.000000] [000000000085684c] __stop_notes+0x11a8/0x1d660
>> [ 0.000000] [00000000006e8bdc] _etext+0xfffffffffffe59f4/0xe18
>> [ 0.000000] [0000000000000000] (null)
>>
>> I'll try to bisect but maybe someone can figure it out quickly
>> meanwhile.
>
> I saw this too. One change that went upstream when i started seeing
> these weird backtraces is:
The patch from Mike Frysinger posted by Stephen Rothwell fixes
it for me.
prev parent reply other threads:[~2009-06-19 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 7:21 backtrace symbols are bolixed David Miller
2009-06-19 7:30 ` Stephen Rothwell
2009-06-19 8:01 ` David Miller
2009-06-19 7:30 ` Ingo Molnar
2009-06-19 8:01 ` David Miller [this message]
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=20090619.010151.83084255.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.