[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Analyzing a 4.0/amd64 panic
I'm trying to analyze a panic on our 4.0/amd64 file server.
Unfortunately, I don't have the panic string. The colleague who rebooted the
machine from ddb forgot to take a screen picture.
Fortunately, I do have a dump. Unfortunately, the message buffer in the dump
is completely filled by the dump block countdown, so I don't have the panic
string from the message buffer either.
Unfortunately, gdb doesn't give me a backtrace. The rip is 0x100. My knowledge
of 8086 assembler is, ehm, limited.
So I dumped memory at rsp and looked for addresses that could be saved ip's.
What I get is approximately the following:
I don't understand why I have ddb's internal procedures in that backtrace but
apart from that it looks like the compiler optimized a call from knote (called
by logwakeup) and there was a trap inside that function.
Any hints how I can analyze this further?
Would it be possible to have the dump block countdown not fill the message
Main Index |
Thread Index |