On Mon, Feb 07, 2005 at 05:22:03PM +0200, Pasi Kärkkäinen wrote: > On Mon, Feb 07, 2005 at 04:01:02PM +0100, P.O. Gaillard wrote: > > Pasi Kärkkäinen > > >Hi! > > > > > >I have P8SCi motherboard, and I just tried the watchdog with Linux 2.6.10. > > > > > >I loaded w83627hf_wdt driver, and the watchdog was detected: > > > > > >WDT driver for the Winbond(TM) W83627HF Super I/O chip initialising. > > >w83627hf WDT: initialized. timeout=60 sec (nowayout=0) > > > > > >But it is not working. I tried setting the timeout to 1 minute, and to > > >8 minute in the BIOS, but the machine reboots after the delay no matter > > >what > > >the delay is.. the watchdog driver is loaded before the timeout of course. > > > > > >For some reason, the driver is not working. > > > > > >I mailed supermicro support about this, and they told me one of their > > >customers is using watchdog with Debian 2.6.10 kernel. > > >So it should work, but.. > > > > > >Is there some patches I could try? > > Hi ! > > I am so glad to find somebody interested in this issue ;-) > > > > Me too :) > > > I am not sure about which watchdog is working in the P8SCi. On my P4Sci, > > the working watchdog was the one in Intel's southbridge with the i8xx-tco > > driver. I tried to use this driver with the P8SAA. To do that I had to use > > 2.6.11rc2bk9 to get ICH6 support in the i8xx-tco driver. But as you may > > know, the watchdog is not working on the P8SAA. > > > > This might be a good bet for you. > > > > Currently building 2.6.11rc3 i8xx-tco driver to test this.. > > I'll let you know what happens. >
i8xx-tco driver from 2.6.11rc3 doesnt seem to work either on P8SCi :( Machine rebooted after the timeout set in BIOS. btw. I'm running watchdog-drivers in xen-dom0 kernel (2.6.10-xen0).. could that cause problems? -- Pasi Kärkkäinen ^ . . Linux / - \ Choice.of.the .Next.Generation. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/