That's the thing. Because I didn't get the oops copied from the screen, where else could it be located? I looked in /var/log/messages, but the log ends just before the crash. last(1) shows my two sessions at the time of the crash as "crash", but I can't find anything anywhere that might be an oops file.

ahp

On Wednesday, January 15, 2003, at 04:13 AM, Herbert Poetzl wrote:

On Tue, Jan 14, 2003 at 08:40:39PM -0500, Adam H. Pendleton wrote:
The newvserver command that I reported yesterday actually caused a
kernel panic.  I couldn't see the full text of the panic, and I
couldn't scroll back or see more, because everytime I hit a key, it
caused the kernel to re-panic or at least print out the panic message
again.  Now that the machine is back up, what's the best way to figure
out what went wrong?
search for the kernel oops and put it through ksymoops
come back with the decoded message/trace and a complete
list of hardware/drivers/modules used as well as the
kernel version and patches applied ...

best,
Herbert

ahp

Attachment: PGP.sig
Description: PGP signature

Reply via email to