> On Fri, Jul 11, 2008 at 4:48 PM, Török Edwin 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 . (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++%ݶw{.n+{G{ayʇڙ,jfhz_(階ݢj"mG?&~iOzv^m ?I