[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121105091118.GA12721@elie.Belkin>
Date: Mon, 5 Nov 2012 01:11:18 -0800
From: Jonathan Nieder <jrnieder@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
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: [regression] Re: [ 049/149] rtc: Disable the alarm in the hardware
(v2)
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.
Known problem? An acpidump and kernel log can be found at [2].
Looking forward to your thoughts,
Jonathan
[1] http://bugs.debian.org/691902
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=78;bug=691902
--
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/
Powered by blists - more mailing lists