On 4 March 2012 01:28, Brendon Higgins blhigg...@gmail.com wrote:
Any more ideas? As I said, I tried getting kdump working but have been having
trouble getting it to behave.
One more thought, but it's a bit of a long shot as to whether you have
the equipment. The most watertight way I know of
On 2012-03-04 09:16 +0100, Jason Heeris wrote:
On 4 March 2012 01:28, Brendon Higgins blhigg...@gmail.com wrote:
Any more ideas? As I said, I tried getting kdump working but have been having
trouble getting it to behave.
One more thought, but it's a bit of a long shot as to whether you have
Hi,
Jason Heeris wrote (Sun March 4, 2012):
The most watertight way I know of to capture kernel
output is a serial port and another computer. If, by any chance, you
have one on your machine
Not really an option (at least, not an easy one), I'm afraid. I only have two
machines, and neither of
Hi again,
Charles Krinke wrote (Thu March 1, 2012):
On the next boot, /var/log/messages shoild contain the last printk's from
the kernel which would include any panic.
Thanks. I'd already checked there, though, and no dice. The log just skips
from the last innocuous kernel message to messages
On the next boot, /var/log/messages shoild contain the last printk's from
the kernel which would include any panic.
So, one should be able to tail /var/log messages and see what the kernel
did at the time of the freeze.
Remembdr that the fresh boot is appendex to /var/log/messages, so you need
On 2 March 2012 12:50, Charles Krinke charles.kri...@gmail.com wrote:
So, one should be able to tail /var/log messages and see what the kernel did
at the time of the freeze.
I've had problems with write caching causing the last few messages to
be lost after a panic*, so if you don't see
6 matches
Mail list logo
