Hey Won, On Wed, 2009-01-28 at 19:15 -0800, Won De Erick wrote: > > From: Al Chu <[email protected]> > > > > > Hey Won, > > > > On Tue, 2009-01-27 at 17:43 -0800, Won De Erick wrote: > > > #bmc-watchdog -d -u 4 -p 0 -n -i 300 -l 0 > > > > what is output from bmc-watchdog --get? You don't define a BMC action > > (i.e. power cycle, power down, do nothing), so it depends on what the > > default action is on that system. > > > > # bmc-watchdog --get > Timer Use: SMS/OS > Timer: Running > Logging: Enabled > Timeout Action: Hard Reset > Pre-Timeout Interrupt: None > Pre-Timeout Interval: 1 seconds > Timer Use BIOS FRB2 Flag: Clear > Timer Use BIOS POST Flag: Clear > Timer Use BIOS OS Load Flag: Clear > Timer Use BIOS SMS/OS Flag: Set > Timer Use BIOS OEM Flag: Clear > Initial Countdown: 240 seconds > Current Countdown: 201 seconds > > i just checked my script and my complete implementation was > > bmc-watchdog -d -u 4 -p 0 -n -l 0 -a 1 -i 240 > > and not the previous one, my typo. > > I think the SEL could justify that proper timeout action was invoked. > > 1:OEM defined = 00 00 00 00 00 E3 25 86 80 00 00 FF 00 > 2:OEM defined = 00 00 > 00 00 00 E3 25 86 80 00 00 FF 00 > 3:OEM defined = 02 00 00 FF 00 00 00 00 20 > 00 00 00 00 > 4:OEM defined = 00 00 00 00 00 E3 25 86 80 00 00 FF > 00 > 5:24-Jan-2009 17:09:30:Watchdog 2 Watchdog:Hard Reset > 6:OEM defined = > 00 00 00 00 00 E3 25 86 80 00 00 FF 00 >
Well, it seems this is the case then. The watchdog is what triggered the hard reset. It's hard to say why the BMC card locked-up/was busy all of the time. It probably could have been anything really. Al > > -- Albert Chu [email protected] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/freeipmi-users
