linux-kernel - Re: [regression] Re: [ 049/149] 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121105101331.GA24688@kroah.com>
Date:	Mon, 5 Nov 2012 11:13:31 +0100
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Jonathan Nieder <jrnieder@...il.com>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	alan@...rguk.ukuu.org.uk, John Stultz <john.stultz@...aro.org>,
	Rabin Vincent <rabin.vincent@...ricsson.com>,
	Janne Boman <janne.m.boman@...il.com>,
	Heinz Wiesinger <HMWiesinger@....at>,
	rtc-linux@...glegroups.com
Subject: Re: [regression] Re: [ 049/149] rtc: Disable the alarm in the
 hardware (v2)

On Mon, Nov 05, 2012 at 01:11:18AM -0800, Jonathan Nieder wrote:
> Hi,
> 
> In March, Greg KH wrote:
> 
> > 3.2-stable review patch.  If anyone has any objections, please let me know.
> 
> Sorry, I'm a little late.  This seems to be causing spurious wakeups
> after shutdown on some systems just like v1 did. :/
> 
> Janne Boman reports[1], using an HP EliteBook 8530w:
> 
> | I'm unable to shutdown my system via normal means. The system
> | completes the shutdown process, all hardware lights are off, but then
> | somehow it restarts.
> 
> Based on a quick web search, Heinz Wiesinger, using the same model,
> ran into the same problem and bisected it to this patch:
> 
>   https://bugzilla.kernel.org/show_bug.cgi?id=44261
> 
> Janne confirmed the same by testing kernels closely based on 3.2.13
> and 3.2.14 --- 3.2.13 shut down fine, while on 3.2.14 "shutdown -h
> now" behaved roughly speaking like "reboot".  A kernel close to 3.6.4
> was also affected.

So is 3.6.6 still and issue?  How about 3.7-rc4?  3.4.18?  Figuring out
if this is still an issue in Linus's tree would be the best thing to do
first.

thanks,

greg k-h
--
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/