public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Rafael David Tinoco <inaddy@ubuntu.com>, Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@codemonkey.org.uk>,
	Davidlohr Bueso <dave@stgolabs.net>,
	jason.low2@hp.com, Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: sched: softlockups in multi_cpu_stop
Date: Fri, 06 Mar 2015 10:46:30 -0500	[thread overview]
Message-ID: <54F9CBD6.1030300@oracle.com> (raw)
In-Reply-To: <54F9BD90.60301@oracle.com>

On 03/06/2015 09:45 AM, Sasha Levin wrote:
> On 03/06/2015 09:34 AM, Rafael David Tinoco wrote:
>> Are you sure about this ? I have a core dump locked on the same place
>> (state machine for powering cpu down for the task swap) from a 3.13 (+
>> upstream patches) and this commit wasn't backported yet.
> 
> bisect took me to that same commit twice, and I'm running a -next with that
> commit reverted and not seeing those hangs anymore.
> 
> I also didn't see the hang up until a month or so ago (which matches with that
> commit date), and definitely not back in 3.13.

I just remembered that I was seeing something similar back then, which was fixed:

	http://lists.openwall.net/linux-kernel/2014/05/12/725


Thanks,
Sasha


  reply	other threads:[~2015-03-06 15:47 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02  7:45 sched: softlockups in multi_cpu_stop Sasha Levin
     [not found] ` <CAMiJ5CVWvUhGK=MWYB_CTNs901p=jsT4i5gkWTaHih7qdQdkFQ@mail.gmail.com>
2015-03-04  5:44   ` Rafael David Tinoco
2015-03-06 11:27 ` Sasha Levin
2015-03-06 12:32   ` Ingo Molnar
2015-03-06 14:34     ` Rafael David Tinoco
2015-03-06 14:45       ` Sasha Levin
2015-03-06 15:46         ` Sasha Levin [this message]
2015-03-06 17:19     ` Davidlohr Bueso
2015-03-06 18:02       ` Sasha Levin
2015-03-06 21:59         ` Sasha Levin
2015-03-06 18:57       ` Jason Low
2015-03-06 19:05         ` Linus Torvalds
2015-03-06 19:20           ` Davidlohr Bueso
2015-03-06 19:32             ` Linus Torvalds
2015-03-06 19:45               ` Davidlohr Bueso
2015-03-06 19:55               ` Davidlohr Bueso
2015-03-06 20:00                 ` Davidlohr Bueso
2015-03-06 21:42                 ` Linus Torvalds
2015-03-06 19:29           ` Jason Low
2015-03-06 21:12             ` Jason Low
2015-03-06 21:24               ` Linus Torvalds
2015-03-07  1:53                 ` Jason Low
2015-03-06 22:15               ` Davidlohr Bueso
2015-03-07  1:55                 ` Ming Lei
2015-03-07  2:07                   ` Davidlohr Bueso
2015-03-07  2:10                     ` Ming Lei
2015-03-07  2:26                       ` Davidlohr Bueso
2015-03-07  2:29                         ` Davidlohr Bueso
2015-03-07  2:55                           ` Ming Lei
2015-03-07  3:10                             ` Davidlohr Bueso
2015-03-07  3:19                               ` Ming Lei
2015-03-07  3:41                                 ` Davidlohr Bueso
2015-03-07  2:56                       ` Jason Low
2015-03-07  3:08                         ` Ming Lei
2015-03-07  3:10                           ` Davidlohr Bueso
2015-03-07  3:17                           ` Jason Low
2015-03-07  3:39                             ` Ming Lei
2015-03-07  3:53                               ` Jason Low
2015-03-07  1:58                 ` Jason Low
2015-03-07  4:31               ` Jason Low
2015-03-07  4:44                 ` Davidlohr Bueso
2015-03-07  6:45                   ` Jason Low
2015-03-07  5:54                 ` Ming Lei
2015-03-07  6:57                   ` Jason Low

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=54F9CBD6.1030300@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=dave@stgolabs.net \
    --cc=davej@codemonkey.org.uk \
    --cc=inaddy@ubuntu.com \
    --cc=jason.low2@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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