On Monday 08 of August 2011 16:28:20 Herbert Poetzl wrote:
> ah, I forgot, yes there is a way (not the easiest though)
> to decode the output your ipmi console recorded:
>
> - extract the byte sequence listed as Code:
> - search for that sequence in your vmlinux
> - add the offset of <xx> relative to the first byte (44)
> - lookup the resulting address with addr2line or
> compare it with objdump -t vmlinux
i've copied v3.0+vserver vmlinuz + more stack traces to web site:
http://pluto.agmk.net/kernel/vmlinuz-3.0.0-vs2.3.1-pre8-dirty
http://pluto.agmk.net/kernel/vserver-crash.jpg
and i'll try these steps asap...
> note that the traces listed in the lkml posting show at
> least 3 different locations where something happened and
> I really wonder if those aren't three different perfectly
> fine stack traces which just get mangled by your ipmi
> setup ... maybe try to explicitely trigger a cpu/kernel
> trace with /proc/magic-sysrq and see if it logs properly
afaics there're no pretty stack traces on real console.
Received on Mon Aug 8 16:32:32 2011
