Bug#524495: w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog!
On Fri, 2009-04-17 at 17:32 +0200, Adam Cécile (Le_Vert) wrote: Package: watchdog Version: 5.6-1 Severity: important Hello, Watchdog doesn't work anymore on my system. I'm not sure if the issue comes from watchdog daemon or from the kernel itself. Feel free to re-assign if I'm wrong. I'm using w83627hf_wdt and when I kill (-9) watchdog processus the kernel says: w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog! Of course, the system never restarts, which is quite annoying for a watchdog service ;-) Are you sure this is the right driver? What make and model of motherboard is in this system? Ben. -- Ben Hutchings DNRC Motto: I can please only one person per day. Today is not your day. Tomorrow isn't looking good either. signature.asc Description: This is a digitally signed message part
Bug#524495: w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog!
To the bug reporter: Are you sure your system needs w83627hf_wdt ? I believe Dedibox are VIA C7-based, and my VIA C7 mainboard definitely needs w83697hf_wdt (with a nine, not a two) at port address 0x4E. On my system (VIA en15000g), w83627hf_wdt loads at the default 0x2E but does nothing, with the same symptoms you described (also, all read to EFDR @ 0x2F returns 0xFF, so it's likely there is nothing there). Loading this driver at 0x4E causes a hard lockup: wrong driver. OTOH, w83697hf_wdt refuses to load at the default 0x2E, and works beautifully at 0x4E. FTR, I use option wdt_io=0x4E nowayout=1 timeout=240. Hope this helps. -- Romain Dolbeau rom...@dolbeau.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524495: w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog!
On Fri, Apr 17, 2009 at 05:32:42PM +0200, Adam Cécile wrote: I'm using w83627hf_wdt and when I kill (-9) watchdog processus the kernel says: w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog! Of course, the system never restarts, which is quite annoying for a watchdog service ;-) I'm pretty much sure that this is a kernel problem. Some reports on the web seem to suggest the same. After all the watchdog code didn't change in this regard. Anyway, do you have NOWAYOUT set? Also it would be nice if you could test with the software watchdog driver softdog just to see whether this is a driver issue. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: mes...@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524495: w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog!
Michael Meskes a écrit : On Fri, Apr 17, 2009 at 05:32:42PM +0200, Adam Cécile wrote: I'm using w83627hf_wdt and when I kill (-9) watchdog processus the kernel says: w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog! Of course, the system never restarts, which is quite annoying for a watchdog service ;-) I'm pretty much sure that this is a kernel problem. Some reports on the web seem to suggest the same. After all the watchdog code didn't change in this regard. Anyway, do you have NOWAYOUT set? Also it would be nice if you could test with the software watchdog driver softdog just to see whether this is a driver issue. Michael Hi, I just give a try with nowayout and it still have the same behavior. Apr 29 15:56:25 dedibox kernel: [17452.939017] WDT driver for the Winbond(TM) W83627HF/THF/HG Super I/O chip initialising. Apr 29 15:56:25 dedibox kernel: [17452.939095] w83627hf/thf/hg WDT: Watchdog already running. Resetting timeout to 60 sec Apr 29 15:56:25 dedibox kernel: [17452.939228] w83627hf/thf/hg WDT: initialized. timeout=60 sec (nowayout=1) Apr 29 15:56:49 dedibox watchdog[14009]: starting daemon (5.6): Apr 29 15:56:49 dedibox watchdog[14009]: int=10s realtime=yes sync=no soft=no mla=25 mem=0 Apr 29 15:56:49 dedibox watchdog[14009]: ping: no machine to check Apr 29 15:56:49 dedibox watchdog[14009]: file: /var/log/messages:0 Apr 29 15:56:49 dedibox watchdog[14009]: pidfile: no server process to check Apr 29 15:56:49 dedibox watchdog[14009]: interface: no interface to check Apr 29 15:56:49 dedibox watchdog[14009]: test=none(0) repair=none alive=/dev/watchdog heartbeat=none temp=none to=root no_act=no [..] Apr 29 15:57:47 dedibox kernel: [17534.954562] w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog! So I tried with softdog driver and I got the same message: Apr 29 16:00:43 dedibox kernel: [17711.068562] SoftDog: Unexpected close, not stopping watchdog! Then the server performed an hard reboot. Weird. Regards, Adam. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524495: w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog!
reassign 524495 linux-image-2.6.29-1-686 thanks On Wed, Apr 29, 2009 at 04:04:32PM +0200, Adam Cécile (Le_Vert) wrote: So I tried with softdog driver and I got the same message: Apr 29 16:00:43 dedibox kernel: [17711.068562] SoftDog: Unexpected close, not stopping watchdog! Then the server performed an hard reboot. Weird. It appears to me that this message means the kernel/hardware watchdog is not stopped, which means the reboot will come. Or in other words the softdog behaviour is correct. Which means the bug is in your driver as we already expected. Therefore I reassign the bug report to the latest sid kernel. If this proves to be incorrect please tell me. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: mes...@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524495: w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog!
Michael Meskes a écrit : reassign 524495 linux-image-2.6.29-1-686 thanks On Wed, Apr 29, 2009 at 04:04:32PM +0200, Adam Cécile (Le_Vert) wrote: So I tried with softdog driver and I got the same message: Apr 29 16:00:43 dedibox kernel: [17711.068562] SoftDog: Unexpected close, not stopping watchdog! Then the server performed an hard reboot. Weird. It appears to me that this message means the kernel/hardware watchdog is not stopped, which means the reboot will come. Or in other words the softdog behaviour is correct. Which means the bug is in your driver as we already expected. Therefore I reassign the bug report to the latest sid kernel. If this proves to be incorrect please tell me. Michael Sounds fine to me :) It fails with both 26.26-2-686 and 2.6.29-1-686 kernels. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524495: w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog!
Package: watchdog Version: 5.6-1 Severity: important Hello, Watchdog doesn't work anymore on my system. I'm not sure if the issue comes from watchdog daemon or from the kernel itself. Feel free to re-assign if I'm wrong. I'm using w83627hf_wdt and when I kill (-9) watchdog processus the kernel says: w83627hf/thf/hg WDT: Unexpected close, not stopping watchdog! Of course, the system never restarts, which is quite annoying for a watchdog service ;-) I tried with both 2.6.26-2-686 Squeeze kernel and 2.6.29-1-686 Sid one. Both watchdog 5.4 and 5.6 packages have been tested too. Best regards, Adam. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.29-1-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages watchdog depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii libc6 2.9-4 GNU C Library: Shared libraries ii makedev 2.3.1-88 creates device files in /dev ii udev 0.125-7/dev/ and hotplug management daemo watchdog recommends no packages. watchdog suggests no packages. -- debconf information: * watchdog/module: w83627hf_wdt * watchdog/run: true * watchdog/restart: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
