[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Fwd: Debian bug#524495: confirmation w83627hf_wdt not rebooting



Hi,

I wanted to provide more details on this closed bug, as I ran into 
(I think) the same problem. Could this bug be re-opened?

Best regards,
Jaap Eldering


----- Forwarded message from Jaap Eldering <eldering@a-eskwadraat.nl> -----

From: Jaap Eldering <eldering@a-eskwadraat.nl>
Date: Fri, 30 Jul 2010 21:03:50 +0200
To: 524495@bugs.debian.org, Michael Meskes <meskes@debian.org>
Subject: confirmation w83627hf_wdt not rebooting
User-Agent: Mutt/1.5.18 (2008-05-17)

Hi,

Not sure I can (or should) reopen this bug, but I can confirm the
reported behaviour that the w83627hf_wdt watchdog module doesn't
reboot my machine when the watchdog deamon is killed.

More details: I'm running Debian Lenny i386 with backports.org kernel
linux-image-2.6.32-bpo.5-686 version 2.6.32-15~bpo50+1.

My system has a Jetway NF76-N1GL-LF motherboard (with VIA VX800
chipset). Loading 'modprobe w83627hf_wdt' gives dmesg output:

[   25.126132] WDT driver for the Winbond(TM) W83627HF/THF/HG Super I/O chip initialising.
[   25.126239] w83627hf/thf/hg WDT: Watchdog already running. Resetting timeout to 60 sec
[   25.127701] w83627hf/thf/hg WDT: initialized. timeout=60 sec (nowayout=0)

As suggested by Romain Dolbeau I've tried loading w83697hf_wdt
instead, both without address and with 0x4E, but it reports:

[ 1229.681655] w83697hf/hg WDT: WDT driver for W83697HF/HG initializing
[ 1229.681743] w83697hf/hg WDT: Looking for watchdog at address 0x4e
[ 1229.681771] w83697hf/hg WDT: watchdog not found at address 0x4e
[ 1229.681843] w83697hf/hg WDT: No W83697HF/HG could be found

[ 1278.900732] w83697hf/hg WDT: WDT driver for W83697HF/HG initializing
[ 1278.900801] w83697hf/hg WDT: Looking for watchdog at address 0x2e
[ 1278.900822] w83697hf/hg WDT: watchdog not found at address 0x2e
[ 1278.900881] w83697hf/hg WDT: No W83697HF/HG could be found

When I use the softdog driver and kill watchdog and wd_keepalive, the
system nicely reboots, while with w83627hf_wdt it doesn't, even with
nowayout=1 set:

[  279.527568] WDT driver for the Winbond(TM) W83627HF/THF/HG Super I/O chip initialising.
[  279.527675] w83627hf/thf/hg WDT: Watchdog already running. Resetting timeout to 60 sec
[  279.529725] w83627hf/thf/hg WDT: initialized. timeout=60 sec (nowayout=1)

$ /etc/init.d/watchdog stop
[  305.708787] w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog!

$ killall wd_keepalive
[  353.919846] w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog!

I'd be glad to provide more information, or try to reproduce this
under squeeze, if requested.

Best regards,
Jaap

----- End forwarded message -----


Reply to: