ichwd problem: watchdog doesn't "bark"
perryh at pluto.rain.com
perryh at pluto.rain.com
Fri Dec 5 00:20:43 PST 2008
[dropped stable@ since I'm not on it and
I suspect it may not accept non-member posts]
> BTW, can someone knowledgeable tell me if watchdog better
> be firing SMI or NMI when it runs down?
> My bet is on NMI, but who knows.
It may depend on whether you want the BIOS, or FreeBSD, handling
the interrupt. Unless you are running *very* old h/w, there's a
good chance the BIOS intercepts SMI, even with a protected-mode
OS running, and I wouldn't be surprised if the BIOS' response to
a watchdog timeout were an immediate reboot. It might be good
to check the motherboard and/or BIOS manuals.
> Or maybe I am trying to ask a different question.
> I see that NMI2SMI_EN bit of TCO1_CNT is set 1 on my machine and
> our watchdog driver is careful to preserve this bit unmodified.
> This means that watchdog would try to cause SMI instead of NMI.
> On the other hand I see that bit GBL_SMI_EN of SMI_EN is set to
> zero, which means that chipset would never generate an SMI.
> So I think this is why I don't see anything happening.
>
> Now, would should try first - reset NMI2SMI_EN to zero or set
> GBL_SMI_EN to 1?
If you want to handle the interrupt in FreeBSD, I'd try resetting
NMI2SMI_EN to zero.
More information about the freebsd-hackers
mailing list