Yes and I'm getting utterly fed up of repeating how to get diagonostic
traces of this to people so they can find out why their specific system
crashed.
Boot without syslogk( or klogd as its sometimes called). Kernel messages
will go to screen - tough live with it for this one
Wait till the box dies - read any panic messages of screen (they may not
get logged to disk if for example it was a disk panic). If nothing is
going on hit right-alt scroll lock, right-shift scroll lock and
right-ctrl scroll lock. Write down the info. The CPU dump (the one,
starting EIP:) do about 20 times and write down the EIP value for each.
Reboot
Look the EIP values for each up in System.map package and mail. That way
a developer can see where there kernel is going at the time.
Alan