Dell 1950 Unexplained Reboots
Lazy
lazy404 at gmail.com
Tue May 19 01:53:06 CDT 2009
__
Lazy
W dniu 2009-05-19, o godz. 04:29, Gordon Stronach <gordy at lansoho.com>
napisał(a):
> Stephen Dowdy wrote:
>> Gordy,
>>
>> Since you're not able to get the hardware to fail under stress, and
>> you're
>> on independent UPSs...
>>
>> Is it possible you're hitting a kernel panic and have panic_reboot
>> enabled?
>> (panic won't be able to log/flush-buffers so it's deadly and silent)
>>
>> cat /proc/sys/kernel/panic
>> cat /proc/cmdline
>>
>> for panic settings.
>>
>> Too bad we don't still have LA120 DecWriter's for consoles so we can
>> see what happened the night before ;) But you can always hook up a
>> serial console redirection connection to another machine to log it
>> to be sure that's not what's happening.
>>
>> I think you did say you have all BIOS/BMC updates, right?
>>
>> --stephen
>
> Stephen,
>
> Here are the panic settings:
>
> [gstronach at db2-www ~]$ cat /proc/sys/kernel/panic
> 60
> [gstronach at db2-www ~]$ cat /proc/cmdline
> ro root=/dev/vgSys/lvRoot panic=60
>
> Yes to the BIOS (2.5.0) DRAC (1.45) BMC (01.33)
>
Check the drac there is an option which saves last crash screens,
bootmsg etc.
> How would be the best way to do a console redirection to another
> machine
> and log it to a file ?
Try netconsole (kernel module)
More information about the Linux-PowerEdge
mailing list