From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Yong Zhang <yong.zhang0@gmail.com>,
David Rientjes <rientjes@google.com>, Tejun Heo <tj@kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: WARNING: at kernel/lockdep.c:690 __lock_acquire+0x168/0x164b()
Date: Fri, 4 Nov 2011 12:31:24 +0300 [thread overview]
Message-ID: <20111104093123.GA2957@swordfish> (raw)
In-Reply-To: <20111104092520.GA16897@gere.osrc.amd.com>
On (11/04/11 10:25), Borislav Petkov wrote:
> > Understood. If someone can come up with a simple patch which could
> > cover the case I mentioned before, that would be great.
> > /me goes to poke at it.
>
> I dunno whether this is related but I get the following on 3.1:
>
I think this is different problem. Failed check that lockdep key is marked as `static'.
Sergey
> [ 5499.537074] INFO: trying to register non-static key.
> [ 5499.537080] the code is fine but needs lockdep annotation.
> [ 5499.537083] turning off the locking correctness validator.
> [ 5499.537088] Pid: 0, comm: kworker/0:1 Not tainted 3.1.0 #1
> [ 5499.537091] Call Trace:
> [ 5499.537094] <IRQ> [<ffffffff8107beed>] __lock_acquire+0x165d/0x1e30
> [ 5499.537109] [<ffffffff810321fc>] ? double_rq_lock+0x2c/0x80
> [ 5499.537115] [<ffffffff8107ccd3>] lock_acquire+0x93/0x160
> [ 5499.537120] [<ffffffff810321fc>] ? double_rq_lock+0x2c/0x80
> [ 5499.537126] [<ffffffff814d9866>] _raw_spin_lock+0x36/0x50
> [ 5499.537130] [<ffffffff810321fc>] ? double_rq_lock+0x2c/0x80
> [ 5499.537135] [<ffffffff810321fc>] double_rq_lock+0x2c/0x80
> [ 5499.537140] [<ffffffff81039195>] load_balance+0x215/0x6c0
> [ 5499.537146] [<ffffffff81039640>] ? load_balance+0x6c0/0x6c0
> [ 5499.537151] [<ffffffff810396fd>] rebalance_domains+0xbd/0x1d0
> [ 5499.537155] [<ffffffff81039640>] ? load_balance+0x6c0/0x6c0
> [ 5499.537161] [<ffffffff810398ec>] run_rebalance_domains+0xdc/0x130
> [ 5499.537166] [<ffffffff81048dcd>] __do_softirq+0xbd/0x290
> [ 5499.537173] [<ffffffff814dc42c>] call_softirq+0x1c/0x30
> [ 5499.537178] [<ffffffff81003eb5>] do_softirq+0x85/0xc0
> [ 5499.537183] [<ffffffff810492ce>] irq_exit+0x9e/0xc0
> [ 5499.537189] [<ffffffff8101ca9f>] smp_call_function_single_interrupt+0x2f/0x40
> [ 5499.537195] [<ffffffff814dbeb0>] call_function_single_interrupt+0x70/0x80
> [ 5499.537199] <EOI> [<ffffffff810096e6>] ? native_sched_clock+0x26/0x70
> [ 5499.537212] [<ffffffffa0038e1a>] ? acpi_idle_enter_simple+0xee/0x11f [processor]
> [ 5499.537221] [<ffffffffa0038e15>] ? acpi_idle_enter_simple+0xe9/0x11f [processor]
> [ 5499.537227] [<ffffffff813f8b1d>] cpuidle_idle_call+0xdd/0x350
> [ 5499.537233] [<ffffffff8100081f>] cpu_idle+0x6f/0xd0
> [ 5499.537238] [<ffffffff814cc665>] start_secondary+0x1ae/0x1b3
>
> --
> Regards/Gruss,
> Boris.
>
next prev parent reply other threads:[~2011-11-04 9:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 20:12 WARNING: at kernel/lockdep.c:690 __lock_acquire+0x168/0x164b() Sergey Senozhatsky
2011-10-15 21:42 ` David Rientjes
2011-10-15 22:23 ` Borislav Petkov
2011-10-15 22:32 ` David Rientjes
2011-10-16 5:09 ` Sergey Senozhatsky
2011-10-20 18:39 ` Borislav Petkov
2011-10-20 18:53 ` Sergey Senozhatsky
2011-10-20 19:07 ` Sergey Senozhatsky
2011-10-20 21:17 ` David Rientjes
2011-10-20 21:23 ` Tejun Heo
2011-10-20 21:31 ` David Rientjes
2011-10-20 21:36 ` Tejun Heo
2011-10-20 23:00 ` Sergey Senozhatsky
2011-10-21 9:14 ` David Rientjes
2011-10-21 9:26 ` Sergey Senozhatsky
2011-10-21 9:45 ` Yong Zhang
2011-11-03 7:17 ` Sergey Senozhatsky
2011-11-03 7:27 ` Yong Zhang
2011-11-03 7:45 ` Sergey Senozhatsky
2011-11-03 7:53 ` Yong Zhang
2011-11-04 9:25 ` Borislav Petkov
2011-11-04 9:31 ` Sergey Senozhatsky [this message]
2011-11-07 4:54 ` Yong Zhang
2011-11-07 8:43 ` Sergey Senozhatsky
2011-11-04 9:34 ` Yong Zhang
2011-11-04 9:51 ` Sergey Senozhatsky
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=20111104093123.GA2957@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=tj@kernel.org \
--cc=yong.zhang0@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.