[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f34abd0807110636u4502c112t56b97218eb8b30d@mail.gmail.com>
Date: Fri, 11 Jul 2008 15:36:33 +0200
From: "Vegard Nossum" <vegard.nossum@...il.com>
To: "Török Edwin" <edwintorok@...il.com>
Cc: linux-next@...r.kernel.org,
"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: today's linux-next fails to boot
On Fri, Jul 11, 2008 at 1:12 PM, Török Edwin <edwintorok@...il.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
Powered by blists - more mailing lists