Sorry - just to further clarify, this is what would happen without the
patch...
1. wd_keepalive daemon is started early in the boot process, loads
ipmi_watchdog and opens + starts to write to /dev/watchdog
2. watchdog init script sends TERM to wd_keepalive daemon
3. watchdog init script
Ok, some more details. It reboots shortly after starting wd_keepalive,
early in the boot sequence. Maybe it is failing to keep up because of
all the disk activity during boot?
Maybe. The default is that the device has to be triggered once a minute which
seems like quite a lot of time for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Meskes wrote:
You mean that it reboots although watchdog is up and running?
Ok, some more details. It reboots shortly after starting wd_keepalive,
early in the boot sequence. Maybe it is failing to keep up because of
all the disk activity
On Wed, Nov 18, 2009 at 02:08:00PM +0100, Marcus Better wrote:
My HP Proliant server rebooted tonight for no apparent reason, after
weeks or months of uptime. After that it started rebooting during the
boot sequence at around the same point (shortly after going multiuser, I
think). I tracked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Meskes wrote:
You mean that it reboots although watchdog is up and running?
It would seem so.
I didn't see any watchdog-related error messages in the syslog, but then
I didn't have verbose mode enabled.
Could you please try with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My HP Proliant server rebooted tonight for no apparent reason, after
weeks or months of uptime. After that it started rebooting during the
boot sequence at around the same point (shortly after going multiuser, I
think). I tracked it to the watchdog
On Sat, Nov 07, 2009 at 10:26:24PM +, Ben Hutchings wrote:
1. EBUSY indicates that the watchdog is opening it more than once, which
is obviously incorrect behaviour.
To the best of my knowledge watchdog only opens the device once which obviously
makes your conclusion wrong as well.
2.
On Fri, Nov 06, 2009 at 04:00:08PM +, Tim Small wrote:
Package: linux-image-2.6.26-2-amd64
Version: 2.6.26-17lenny1
Severity: normal
Opening /dev/watchdog as provided by ipmi_watchdog on a Dell PowerEdge
860 running Lenny 5.0 (64 bit), frequently fails with EBUSY.
Could you please try
On Fri, 2009-11-06 at 16:00 +, Tim Small wrote:
Package: linux-image-2.6.26-2-amd64
Version: 2.6.26-17lenny1
Severity: normal
Opening /dev/watchdog as provided by ipmi_watchdog on a Dell PowerEdge
860 running Lenny 5.0 (64 bit), frequently fails with EBUSY.
Nov 5 11:50:09 kernel: [
On Sat, Nov 07, 2009 at 03:40:22PM +, Ben Hutchings wrote:
worse, if the module is loaded with the nowayout=1 - the machine then
gets hard-reset timeout seconds later!
The watchdog device cannot be closed if it was not successfully opened.
This is a problem with the watchdog daemon.
On Sat, 2009-11-07 at 22:45 +0100, Michael Meskes wrote:
On Sat, Nov 07, 2009 at 03:40:22PM +, Ben Hutchings wrote:
worse, if the module is loaded with the nowayout=1 - the machine then
gets hard-reset timeout seconds later!
The watchdog device cannot be closed if it was not
11 matches
Mail list logo
