Re: today's linux-next fails to boot

["Vegard Nossum" <vegard.nossum@gmail.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1367 bytes --]

> 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
BTW, did the new kernel fail in exactly the same place? If not, youshould also replace the EIP in the new crash report on the addr2linecommand line, so in general: addr2line -e vmlinux -f -i <EIP here>.
(I don't think it really makes sense for the kernel to crash inkmem_cache_alloc() this early in the boot process, so I'm guessing youhave a different EIP.)
(Also don't rebuild a bad kernel just to try this out again, but ifyou happen to run across another bad one for example during bisection,you can try it then.)

Vegard
-- "The animistic metaphor of the bug that maliciously sneaked in whilethe programmer was not looking is intellectually dishonest as itdisguises that the error is the programmer's own creation."	-- E. W. Dijkstra, EWD1036ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥