From: "Vegard Nossum" <vegard.nossum@gmail•com>
To: "Török Edwin" <edwintorok@gmail•com>
Cc: 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 15:36:33 +0200 [thread overview]
Message-ID: <19f34abd0807110636u4502c112t56b97218eb8b30d@mail.gmail.com> (raw)
In-Reply-To: <4877400B.1000400@gmail.com>
On Fri, Jul 11, 2008 at 1:12 PM, Török Edwin <edwintorok@gmail•com> wrote:
> Hi,
>
> Today's linux-next tree (commit
> 93847083e4791567931bd17c039cc35881cdad29) fails to boot:
> [built with gcc-4.2.4-3]
>
> BUG: Int 14: CR2 b0049dea
> EDI 00000082 ESI 00000000 EBP c059be88 ESP c059be5c
> EBX f000ec62 EDX 0000000e ECX c0595480 EAX f000ec62
> err 00000000 EIP c0181ca0 CS 00000060 flg 00010082
> Stack: 00000040 c06a2ba0 000080d0 c0595480 c0000f19c c000f180 c0581120
> c059bea8
> c02bf19b 00000000 00000080 c059beb8 c0000f194 c000f180 0000000a
> c059beb8
> c03a1059 00000000 00000000 c059bed8 c05c4c7c 0009efff 00000000
> c04f4df4
Hi,
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
But you need to make sure that the bzImage/vmlinux you booted
corresponds to the vmlinux you are running addr2line against.
This will tell you the source line which produced the page fault and
will probably give a good clue as to what went wrong.
Thanks for reporting :-)
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 13:36 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
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 [this message]
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=19f34abd0807110636u4502c112t56b97218eb8b30d@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 \
/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