lkml.org 
[lkml]   [2012]   [Sep]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: lockdep WARNING for run_timer_softirq()
From
Date
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
> ever have CONFIG_PARAVIRT or CONFIG_TRACE_BRANCH_PROFILING, let alone
> both.
>

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

I'll forward it to you.

-- Steve




\
 
 \ /
  Last update: 2012-09-05 20:02    [W:0.058 / U:1.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site