linux-kernel - [REGRESSION] 41c7f74 rtc: Disable the alarm in the hardware (v2)

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: <20131201220343.2285b12ee1c1e54252dc7dd9@mos6581.org>
Date:	Sun, 1 Dec 2013 22:03:43 +0100
From:	Brecht Machiels <brecht@...6581.org>
To:	linux-kernel@...r.kernel.org
Cc:	John Stultz <john.stultz@...aro.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Borislav Petkov <bp@...en8.de>,
	Jonathan Nieder <jrnieder@...il.com>,
	Heinz Wiesinger <HMWiesinger@....at>
Subject: [REGRESSION] 41c7f74 rtc: Disable the alarm in the hardware (v2)

Hi,

I recently installed (Arch x86_64) Linux with the 3.12.1 kernel on a Toshiba Satellite L300 laptop. After shutting down Linux, the laptop will spontaneously boot up after about five minutes. This seems to be consistent. There are no options in the BIOS for en/disabling or configuring the RTC wakeup alarm. After 'shudown --halt' and shutting down the laptop manually (pressing the power button for 3 seconds), it will not spontaneously boot up. I understand Linux is configuring the RTC alarm on shutdown? 

After finding some other reports of similar problems, I have built a custom 3.12.1 kernel after reverting commit 41c7f74 (rtc: Disable the alarm in the hardware (v2)) [1]. This seems to solve the problem for me.

Related discussions and bug reports:
* http://thread.gmane.org/gmane.linux.kernel/1527538
  refers to: https://bugzilla.novell.com/show_bug.cgi?id=812592
             https://bugzilla.novell.com/show_bug.cgi?id=805740
* http://thread.gmane.org/gmane.linux.kernel/1275165/focus=1388471
  refers to: http://bugs.debian.org/691902

Both LKML threads seem to have died without any action being taken.

Setting the RTC alarm time way in the future, as suggested in [2] didn't work for me.

Output of dmidecode is attached. Please let me know if any other information could be useful.

[1] https://github.com/torvalds/linux/commit/41c7f74
[2] https://forums.computers.toshiba-europe.com/forums/thread.jspa?messageID=256816

Best regards
-- 
Brecht Machiels

View attachment "dmidecode_toshiba_pslb8e.log" of type "text/plain" (11484 bytes)