Hi !
I'm happy to say that watchdog for P4SCi is detected
fine with my 2.6.9-freevps-1.5-1 kernel (centos 4.1 patched with freevps
1.5-1)
[root@shinwey ~]# uname -a
Linux shinwey 2.6.9-freevps-1.5-1 #1 SMP Sun Sep 25 23:07:51 CEST 2005
i686 i686 i386 GNU/Linux
Sep 26 10:55:18 shinwey kernel: WDT500/501-P driver 0.10 at 0x0240
(Interrupt 11). heartbeat=60 sec (nowayout=0)
Sep 26 10:55:18 shinwey kernel: wdt: Fan Tachometer is Disabled
Sep 26 10:55:18 shinwey kernel: w83877f_wdt: cannot register miscdev on minor=130 (err=-16)
Sep 26 10:55:18 shinwey kernel: WDT driver for the Winbond(TM) W83627HF Super I/O chip
initialising.
Sep 26 10:55:18 shinwey kernel: w83627hf WDT: cannot register miscdev on minor=130 (err=-16)
Unfortunatelly, I set up a 4 minutes delay in the bios, the server takes
less than 2 minutes to boot and detect the watchdog chip, but reboot takes
place ...
I don't get what's happening, my /dev/watchdog is existing and conform to
the devices.txt;
[root@shinwey Documentation]# ls -l /dev/watchdog
crw------- 1 root root 10, 130 Sep 26 2005 /dev/watchdog
Any tip ?
Sincere Regards,
Olivier Kaloudoff
On Mon, Sep 26, 2005 at 07:32:03PM +0200, Olivier Kaloudoff wrote:
> Hi !
>
>
> I'm happy to say that watchdog for P4SCi is detected
> fine with my 2.6.9-freevps-1.5-1 kernel (centos 4.1 patched with freevps
> 1.5-1)
>
Sorry to disappoint you, but check the linux-kernel archives for discussion
about supermicro motherboard and watchdog..
the watchdog of this motherboard is not (yet) supported by linux..
Or do the latest watchdog patches for 2.6.13/14 already support this mb?
-- Pasi K?rkk?inen
> [root@shinwey ~]# uname -a
> Linux shinwey 2.6.9-freevps-1.5-1 #1 SMP Sun Sep 25 23:07:51 CEST 2005
> i686 i686 i386 GNU/Linux
>
>
> Sep 26 10:55:18 shinwey kernel: WDT500/501-P driver 0.10 at 0x0240
> (Interrupt 11). heartbeat=60 sec (nowayout=0)
>
> Sep 26 10:55:18 shinwey kernel: wdt: Fan Tachometer is Disabled
> Sep 26 10:55:18 shinwey kernel: w83877f_wdt: cannot register miscdev on
> minor=130 (err=-16)
>
> Sep 26 10:55:18 shinwey kernel: WDT driver for the Winbond(TM) W83627HF
> Super I/O chip initialising.
>
> Sep 26 10:55:18 shinwey kernel: w83627hf WDT: cannot register miscdev on
> minor=130 (err=-16)
>
>
> Unfortunatelly, I set up a 4 minutes delay in the bios, the server takes
> less than 2 minutes to boot and detect the watchdog chip, but reboot takes
> place ...
>
> I don't get what's happening, my /dev/watchdog is existing and conform to
> the devices.txt;
>
> [root@shinwey Documentation]# ls -l /dev/watchdog
> crw------- 1 root root 10, 130 Sep 26 2005 /dev/watchdog
>
>
> Any tip ?
>
>
>
> Sincere Regards,
>
>
> Olivier Kaloudoff
>
Olivier Kaloudoff wrote:
> Hi !
>
>
> I'm happy to say that watchdog for P4SCi is detected
> fine with my 2.6.9-freevps-1.5-1 kernel (centos 4.1 patched with freevps
> 1.5-1)
Note detected is too strong a word.
Watchdog driver generally can't detect that
the appropriate watchdog hardware is present.
>
> [root@shinwey ~]# uname -a
> Linux shinwey 2.6.9-freevps-1.5-1 #1 SMP Sun Sep 25 23:07:51 CEST 2005
> i686 i686 i386 GNU/Linux
>
>
> Sep 26 10:55:18 shinwey kernel: WDT500/501-P driver 0.10 at 0x0240
> (Interrupt 11). heartbeat=60 sec (nowayout=0)
>
> Sep 26 10:55:18 shinwey kernel: wdt: Fan Tachometer is Disabled
> Sep 26 10:55:18 shinwey kernel: w83877f_wdt: cannot register miscdev on
> minor=130 (err=-16)
>
> Sep 26 10:55:18 shinwey kernel: WDT driver for the Winbond(TM) W83627HF
> Super I/O chip initialising.
>
> Sep 26 10:55:18 shinwey kernel: w83627hf WDT: cannot register miscdev on
> minor=130 (err=-16)
>
>
> Unfortunatelly, I set up a 4 minutes delay in the bios, the server takes
> less than 2 minutes to boot and detect the watchdog chip, but reboot takes
> place ...
I notice you are loading multiple watchdog drivers
which will probably clash with each other.
You need to identify the watchdog on the motherboard
and only load the appropriate module. Google suggests
the driver could be i8xx-tco or w83627hf?
I wrote the w83627hf driver and did a recent change
to fix immediate reboot on module loading on certain systems.
The cause was when the BIOS starts the watchdog with
a timeout of X minutes, the hardware is in "minute mode".
However when the watchdog loads in changes it to "seconds mode",
causing a reboot within 4 seconds in your case.
The good news is if the machine is rebooting within 4 seconds
of loading the w83627hf module then you know that it is
the appropriate module to load, and a fix is available.
Other watchdog drivers may have the same issue.
P?draig.