linux-kernel - Re: iTCO watchdog timer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080306212820.GA2866@infomag.infomag.iguana.be>
Date:	Thu, 6 Mar 2008 22:28:20 +0100
From:	Wim Van Sebroeck <wim@...ana.be>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Stephen.Clark@...lark.us, linux-kernel@...r.kernel.org
Subject: Re: iTCO watchdog timer

Hi All,

Sorry but it's quite busy at the moment...

> > I have new Intel DG33FB mainboard.
> > 
> > 
> > Mar  2 20:47:19 joker1 kernel: iTCO_vendor_support: vendor-support=0
> > Mar  2 20:47:19 joker1 kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver 
> > v1.02 (26-Jul-2007)
> > Mar  2 20:47:19 joker1 kernel: iTCO_wdt: Found a ICH9DH TCO device 
> > (Version=2, TCOBASE=0x0460)
> > Mar  2 20:47:19 joker1 kernel: iTCO_wdt: initialized. heartbeat=30 sec 
> > (nowayout=0)
> > ...
> > Mar  4 14:22:59 joker1 kernel: iTCO_wdt: Unexpected close, not stopping 
> > watchdog!
> > 
> > 
> > I start watchdog.c and then kill it expecting the system to reboot - but 
> > it doesn't.
> > 
> > Isn't this how it is supposed to work?

This is indeed how it should work. It's indeed strange that the system doesn't
reboot. If I find some time I will give you some test code to run.

Greetings,
Wim.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/