From: Nikolay Borisov <kernel@kyup.com>
To: Mike Galbraith <umgwanakikbuti@gmail.com>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Cc: Jiri Slaby <jslaby@suse.cz>, Oleg Nesterov <oleg@redhat.com>,
tglx@linutronix.de,
SiteGround Operations <operations@siteground.com>
Subject: Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code
Date: Thu, 4 Feb 2016 13:51:16 +0200 [thread overview]
Message-ID: <56B33B34.6090508@kyup.com> (raw)
In-Reply-To: <1454585550.3407.126.camel@gmail.com>
On 02/04/2016 01:32 PM, Mike Galbraith wrote:
> On Wed, 2016-02-03 at 12:58 +0200, Nikolay Borisov wrote:
>>
>> So in this case the prev/next entries do not look like corrupted, whereas
>> when manipulating the list inside detach_timer they do. This is really
>> odd, any ideas how to further debug this?
>
> Suspiciously similar to https://lkml.org/lkml/2016/2/4/247
Right, I've been cursory following this thread but I was left with the
impression this only occurs on machines where the CPU can go offline,
currently the server on which this happened should never offline any of
its CPUs since the power management is disabled (though I will have to
double check this).
On a different note - is there a way to safely reproduce this so I can
test the suggested fix by Thomas?
>
> -Mike
>
next prev parent reply other threads:[~2016-02-04 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 10:58 crash in 3.12.51 (likely in 3.12.52 as well) in timer code Nikolay Borisov
2016-02-04 8:56 ` Thomas Gleixner
2016-02-04 11:32 ` Mike Galbraith
2016-02-04 11:51 ` Nikolay Borisov [this message]
2016-02-04 12:17 ` Mike Galbraith
2016-02-04 12:21 ` Nikolay Borisov
2016-02-04 12:27 ` Mike Galbraith
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=56B33B34.6090508@kyup.com \
--to=kernel@kyup.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=operations@siteground.com \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
/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