From: "Vegard Nossum" <vegard.nossum@gmail•com>
To: "Török Edwin" <edwintorok@gmail•com>
Cc: Ingo Molnar <mingo@elte•hu>, Takashi Iwai <tiwai@suse•de>,
linux-next@vger•kernel.org,
Linux Kernel <linux-kernel@vger•kernel.org>
Subject: Re: today's linux-next fails to boot
Date: Fri, 11 Jul 2008 16:54:04 +0200 [thread overview]
Message-ID: <19f34abd0807110754n1a095671ua9132471b6a81540@mail.gmail.com> (raw)
In-Reply-To: <487772B6.4090100@gmail.com>
On Fri, Jul 11, 2008 at 4:48 PM, Török Edwin <edwintorok@gmail•com> wrote:
>> One really simple way of getting some more info out of this is to take
>> the EIP value (here c0181ca0) and run it through addr2line:
>>
>> $ addr2line -e vmlinux -i c0181ca0
>
> Thanks for the hint, I rebuilt a failing kernel, and this is what
> addr2line says:
>
> $ addr2line -e vmlinux -i c0181ca0
>
> ??:0
> $ addr2line -e vmlinux -f c0181ca0
> kmem_cache_alloc
> ??:0
Ouch, sorry. You need CONFIG_DEBUG_INFO for this to really make any
sense. My habits are deceiving me, because I always build with
DEBUG_INFO. Ingo claims that this slows down his builds, so he never
does it. In the end, it is up to each one of us to choose his options,
but in general, I think it should be used when testing kernels.
If you're tired of rebuilding kernels now, I don't blame you. Another
lesson learned for me :-(
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-07-11 14:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 11:12 today's linux-next fails to boot Török Edwin
2008-07-11 13:03 ` Takashi Iwai
2008-07-11 13:13 ` Török Edwin
2008-07-11 13:59 ` Ingo Molnar
2008-07-11 14:48 ` Török Edwin
2008-07-11 14:53 ` Ingo Molnar
2008-07-11 15:10 ` Rafael J. Wysocki
2008-07-11 19:07 ` Ingo Molnar
2008-07-11 21:06 ` Rafael J. Wysocki
2008-07-12 0:50 ` Rafael J. Wysocki
2008-07-12 4:47 ` Ingo Molnar
2008-07-11 14:54 ` Vegard Nossum [this message]
2008-07-11 15:00 ` Vegard Nossum
2008-07-11 15:27 ` Török Edwin
2008-07-16 21:11 ` Thomas Meyer
2008-07-16 21:57 ` Frédéric Weisbecker
2008-07-11 13:04 ` Takashi Iwai
2008-07-11 13:36 ` Vegard Nossum
2008-07-15 2:11 ` Frédéric Weisbecker
2008-07-15 11:06 ` Takashi Iwai
2008-07-15 11:15 ` Bernhard Walle
2008-07-15 11:17 ` Bernhard Walle
2008-07-15 11:53 ` Takashi Iwai
2008-07-15 12:02 ` Bernhard Walle
[not found] ` <c62985530807150800l4f34a6a3m22d58d66316c1e09@mail.gmail.com>
2008-07-15 15:14 ` Bernhard Walle
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=19f34abd0807110754n1a095671ua9132471b6a81540@mail.gmail.com \
--to=vegard.nossum@gmail$(echo .)com \
--cc=edwintorok@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=tiwai@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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