Date: Thu, 11 Jul 2013 12:07:21 +0200
From: Borislav Petkov <bp@alien8.de>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: linux-kernel@vger.kernel.org, dhowells@redhat.com,
        "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
        Peter Zijlstra <peterz@infradead.org>
Subject: Re: Hard lockups using 3.10.0
Message-ID: <20130711100721.GA28131@pd.tnic>
References: <8484013.LsABBJRIOx@devpool02>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <8484013.LsABBJRIOx@devpool02>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1114
Lines: 28

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.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/