Skip to contentSkip to conversation

Post-mortem crash analysis on SNB laptop?

DISCUSSION Dan McCabe 3 participants 5 messages Jun 22, 2011

lore
Share & tools
lore

Dan McCabe

author
#0 lore raw

My SNB laptop completely locks up every now and then (maybe twice a day). Is there any good way to look at post-mortem data to help my diagnose this issue.

I've seen discussions suggesting that I ssh into the machine, but I can't even do that.

TIA

cheers, danm

#1 lore raw
Quoted 6 lines · Dan McCabe

My SNB laptop completely locks up every now and then (maybe twice a day). Is there any good way to look at post-mortem data to help my diagnose this issue.

I've seen discussions suggesting that I ssh into the machine, but I can't even do that.

The best that I found is to run netconsole and listen for any random oops. Having been bitten by hard hangs with early SNB chips, my systems all have i915.reset=0 which helped at that time, and may still help if the hard hang is due to us doing something stupid whilst trying to reset the chip. -Chris

Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre
#2 lore raw
In reply to Dan McCabe
Quoted 10 lines · Dan McCabe

My SNB laptop completely locks up every now and then (maybe twice a day). Is there any good way to look at post-mortem data to help my diagnose this issue.

I've seen discussions suggesting that I ssh into the machine, but I can't even do that.

TIA

cheers, danm

Netconsole is nice for capturing the last dying breaths (with the appropriate drm.debug flags, I usually use 0x6, but I guess 0xe is the safest).

Assuming netconsole is built as a module, you can run something like this on the crashing machine:
modprobe netconsole netconsole=6665@${IP_ADDRESS}/eth0,6666@${REMOTE_IP}/${REMOTE_MAC}

And this on some remote machine:
netcat -u -l -p 6666

#3 lore raw
Quoted 2 lines · Ben Widawsky

And this on some remote machine:
netcat -u -l -p 6666

One issue that I found with netcat (at least in the incarnation above) is that it fails to listen for more than one connection (even on UDP). Am I doing it wrong? I ended up using a very simple UDP reader instead. -Chris

Signature · 1 line
Chris Wilson, Intel Open Source Technology Centre
#4 lore raw
Quoted 8 lines · Chris Wilson
Quoted 2 lines · Ben Widawsky

And this on some remote machine:
netcat -u -l -p 6666

One issue that I found with netcat (at least in the incarnation above) is that it fails to listen for more than one connection (even on UDP). Am I doing it wrong? I ended up using a very simple UDP reader instead. -Chris

I normally use different ports for different machines to avoid this. I actually have a script which I run that does the correct stuff based on the hostname.

Quoted 3 lines
Signature · 2 lines
-- 
Chris Wilson, Intel Open Source Technology Centre