Re: ichwd problem: watchdog doesn't "bark"

2008-12-05 Thread Dag-Erling Smørgrav
Andriy Gapon <[EMAIL PROTECTED]> writes: > When I start watchdogd I see the following messages: > timer enabled > timeout set to 28 ticks > and then a flow of messages: > timer reloaded > > Then I kill -9 watchdogd. > "timer reloded" messages are no longer produced. > And there are no other messag

Re: ichwd problem: watchdog doesn't "bark"

2008-12-05 Thread Garrett Cooper
On Fri, Dec 5, 2008 at 12:10 AM, <[EMAIL PROTECTED]> wrote: > [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. > >

Re: ichwd problem: watchdog doesn't "bark"

2008-12-05 Thread perryh
[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 int

Re: ichwd problem: watchdog doesn't "bark"

2008-12-04 Thread Andriy Gapon
on 28/11/2008 16:28 Andriy Gapon said the following: > uname: > FreeBSD 7.1-PRERELEASE r185311 amd64 > > dmesg: > ichwd0: on isa0 > ichwd0: Intel ICH9R watchdog timer (ICH9 or equivalent) > ichwd0: timer disabled > > pciconf: > [EMAIL PROTECTED]:0:31:0: class=0x060100 card=0x50448086 chip=0