archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <>
To: Peter Zijlstra <>
Cc: Fengguang Wu <>,
	Thomas Gleixner <>,
	john stultz <>, Ingo Molnar <>,
	LKML <>
Subject: Re: lockdep WARNING for run_timer_softirq()
Date: Wed, 05 Sep 2012 13:14:58 -0400	[thread overview]
Message-ID: <1346865298.27919.58.camel@gandalf.local.home> (raw)
In-Reply-To: <1346864947.2600.33.camel@twins>

On Wed, 2012-09-05 at 19:09 +0200, Peter Zijlstra wrote:
> On Wed, 2012-09-05 at 10:20 -0400, Steven Rostedt wrote:
> > Well, the branch tracer was active. That means all 'if()'s were being
> > traced. It comes down to how you define 'if' ;-) 
> Yeah, I tried making an argument for:
>   we tell lockdep irqs are enabled hit an if() end up in lockdep code
> through the branch tracer and find borken state, or vice-versa.
> Just couldn't find it in the provided stack-trace. Might be I didn't
> look hard enough, might be there's something else entirely.
> All I know is I've never seen it on real hardware, then again, I hardly
> both.

This looks very familiar to Fengguang's previous bug report. I can't
seem to find it on Probably because of the two attachments
(dmesg and config) caused lkml to nuke it.

I'll forward it to you.

-- Steve

  reply	other threads:[~2012-09-05 17:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31  7:21 lockdep WARNING for run_timer_softirq() Fengguang Wu
2012-08-31  7:32 ` Fengguang Wu
2012-09-05 11:47 ` Peter Zijlstra
2012-09-05 14:20   ` Steven Rostedt
2012-09-05 17:09     ` Peter Zijlstra
2012-09-05 17:14       ` Steven Rostedt [this message]
2012-09-05 17:19         ` Peter Zijlstra
2012-09-05 19:23           ` Steven Rostedt

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1346865298.27919.58.camel@gandalf.local.home \ \ \ \ \ \ \ \

* 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).