linux-kernel - watchdog (iTCO_wdt) heartbeat/timeout value is ignored after suspend-to-{RAM,disk}

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-next>] [day] [month] [year] [list]

Message-ID: <20120415163130.GA12802@aldebaran.gro-tsen.net>
Date:	Sun, 15 Apr 2012 18:31:30 +0200
From:	David Madore <david+ml@...ore.org>
To:	linux-kernel@...r.kernel.org
Subject: watchdog (iTCO_wdt) heartbeat/timeout value is ignored after
 suspend-to-{RAM,disk}

Dear list,

My motherboard's chipset (ICH7) has a watchdog handled by the iTCO_wdt
driver.  This module takes a "heartbeat" parameter which specifies the
timeout after which the system is reset.

It appears that this parameter no longer has an effect after the
system is suspended (to RAM or disk) and then resumed: I use
heartbeat=90, which initially works, but after a resume, the system is
rebooted despite the wd_keepalive daemon writing to the device every
30 seconds or so.

I imagine this is easy to fix.

-- 
     David A. Madore
   ( http://www.madore.org/~david/ )
--
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/