[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130711101632.GD25631@dyad.programming.kicks-ass.net>
Date: Thu, 11 Jul 2013 12:16:32 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Rolf Eike Beer <eike-kernel@...tec.de>,
linux-kernel@...r.kernel.org, dhowells@...hat.com,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: Hard lockups using 3.10.0
On Thu, Jul 11, 2013 at 12:07:21PM +0200, Borislav Petkov wrote:
> On Thu, Jul 11, 2013 at 11:38:37AM +0200, Rolf Eike Beer wrote:
> > Hi,
> >
> > I'm running 3.10.0 (from openSUSE packages) on an "Intel(R) Core(TM) i7-2600
> > CPU @ 3.40GHz". I got a hard lockup on one of my CPUs twice, once with
> > backtrace (see attached image). Graphics is the builtin Intel, used with X 7.6
> > and KDE 4.10beta2 (basically current openSUSE 12.3+KDE).
> >
> > I'm not aware that I had done anything special, just "normal" desktop and
> > development usage, but no heavy compile work at the moment the lockups
> > happened.
>
> Hmm, I can see commit_creds() doing some rcu pointers assignment and rcu
> calling into the scheduler which screams about a cpu runqueue of the
> task we're about to reschedule not being locked. Let's add some more
> people who should know better.
-ENOIMAGE
--
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