From: Borislav Petkov <bp@alien8.de>
To: John Stultz <john.stultz@linaro.org>
Cc: Brecht Machiels <brecht@mos6581.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jonathan Nieder <jrnieder@gmail.com>,
Heinz Wiesinger <HMWiesinger@gmx.at>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] 41c7f74 rtc: Disable the alarm in the hardware (v2)
Date: Mon, 2 Dec 2013 22:19:58 +0100 [thread overview]
Message-ID: <20131202211958.GE7380@pd.tnic> (raw)
In-Reply-To: <529CF1D5.6010406@linaro.org>
On Mon, Dec 02, 2013 at 12:47:17PM -0800, John Stultz wrote:
> Ok, sorry about this. I've been hoping we'd get some better insight
> into what's actually happening on these strange BIOSes where disabling
> the irq seems to cause it to scream (powering the system back on when
> its shutdown), in the hopes of having a proper workaround. But despite
> Borislav's efforts, he didn't seem to be able to root cause the issue.
Right, this bug is too nasty - you could generate good random numbers
just from how the hardware behaves. :) And I've been trying to make
sense of what happens but I failed, as you know. :(
I consider it a huge waste of time and efforts having to deal with such
b0rked hardware instead of throwing it out of the window into the poring
rain while it is still powered.
> Borislav, could you double check this patch still works on your
> hardware as well?
Well, we have the patch in SLES11:
http://kernel.opensuse.org/cgit/kernel/commit/?h=SLE11-SP3&id=835398eb94dca7d55acd1a2628372e602ae3252a
and it passed testing.
>From what I see below, your version is equivalent to the one above
with the logic reversed so it should work. I'll still try to get that
affected box and run your version on it but it'll take a while.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-12-02 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 21:03 [REGRESSION] 41c7f74 rtc: Disable the alarm in the hardware (v2) Brecht Machiels
2013-12-02 20:47 ` John Stultz
2013-12-02 21:19 ` Borislav Petkov [this message]
2013-12-05 11:51 ` Brecht Machiels
2013-12-12 19:39 ` John Stultz
2013-12-12 21:16 ` John Stultz
2013-12-12 21:24 ` Borislav Petkov
2013-12-12 22:35 ` John Stultz
2013-12-13 16:47 ` Borislav Petkov
2013-12-13 8:41 ` Brecht Machiels
2013-12-11 19:57 ` John Stultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131202211958.GE7380@pd.tnic \
--to=bp@alien8.de \
--cc=HMWiesinger@gmx.at \
--cc=brecht@mos6581.org \
--cc=john.stultz@linaro.org \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox