[OmniOS-discuss] Debugging crash dump

Dan McDonald danmcd at omniti.com
Tue May 12 13:02:28 UTC 2015


> On May 12, 2015, at 6:23 AM, Lawrence Giam <paladinemishakal at gmail.com> wrote:
> 
> Hi All,
> 
> I have a few time the server panic and auto-rebooted with crash dump. I am looking at this post http://wiki.illumos.org/display/illumos/How+To+Report+Problems but it seem the info is not updated.
> 
> When I run this:
> echo '::panicinfo\n::cpuinfo -v\n::threadlist -v 10\n::msgbuf\n*panic_thread::findstack -v\n::stacks' | mdb 5 > ~/crash.5
> 
> root at sgbk02:/var/crash/unknown# echo '::panicinfo\n::cpuinfo -v\n::threadlist -v 10\n::msgbuf\n*panic_thread::findstack -v\n::stacks' | mdb 5 > crash.5
> mdb: warning: dump is from SunOS 5.11 omnios-8c08411; dcmds and macros may not match kernel implementation
<SNIP!>

8c08411 is OmniOS r151010 -- that's where your dump is from.  Are you running the analysis on a later-release machine?  It looks like that's the case, and there have been mdb changes between 1-2 stable releases that would make reading 010 dumps difficult.

"$c" or "$C" show you the kernel stack, and "::msgbuf" shows you the in-kernel-memory dmesg(1M) output.

Dan



More information about the OmniOS-discuss mailing list