linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carsten Emde <C.Emde@osadl.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: 3.10.20-rt17, BUG and Oops
Date: Sat, 21 Dec 2013 22:23:01 +0100	[thread overview]
Message-ID: <52B606B5.70205@osadl.org> (raw)
In-Reply-To: <52AEB525.4060907@linutronix.de>

On 12/16/2013 09:09 AM, Sebastian Andrzej Siewior wrote:
> On 12/16/2013 12:50 AM, Carsten Emde wrote:
>> On 12/15/2013 03:53 PM, Sebastian Andrzej Siewior wrote:
>>> * Carsten Emde | 2013-11-30 23:47:25 [+0100]:
>>>> Will apply the fix and the warning - let's see.
>>> I do not want to urge anyone but just gentle ping to satisfy my
>>> curiosity about the patch.
>> I have applied the patch to a number of systems including the one that
>> regularly crashed after less than a week. No system crashed so far, and
>> uptime of the one that I initially monitored for the crashes is now 15
>> days. Please allow for another week of monitoring. If by next weekend
>> all patched systems still are up and running, I will submit the patch
>> along with a description and a short history when and how the race made
>> it into the code.
> Sounds great. Thanks.
Uptime is now 20 days, no problems any more.

Just wanted to write down the whole story and send the patch to LKML 
when I saw that the patch already made it into vanilla 3.12.5 and, thus, 
to RT. It is marked 3.8+ stable, so all is good now.

The mainline patch is:
ACPI / EC: Ensure lock is acquired before accessing ec struct members, 
commit 36b15875a7819a2ec4cb5748ff7096ad7bd86cbb.

	-Carsten.

  reply	other threads:[~2013-12-21 21:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30  7:56 3.10.20-rt17, BUG and Oops Fernando Lopez-Lezcano
2013-11-30 16:40 ` Carsten Emde
2013-11-30 20:39   ` Sebastian Andrzej Siewior
2013-11-30 22:47     ` Carsten Emde
2013-12-02  8:27       ` Sebastian Andrzej Siewior
2013-12-15 14:53       ` Sebastian Andrzej Siewior
2013-12-15 23:50         ` Carsten Emde
2013-12-16  8:09           ` Sebastian Andrzej Siewior
2013-12-21 21:23             ` Carsten Emde [this message]
2013-12-17 19:40         ` Fernando Lopez-Lezcano
2013-12-17 19:42           ` Sebastian Andrzej Siewior

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=52B606B5.70205@osadl.org \
    --to=c.emde@osadl.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=rostedt@goodmis.org \
    /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;
as well as URLs for NNTP newsgroup(s).