From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: [PATCH 2/6] Unified trace buffer
Date: Tue, 30 Sep 2008 13:53:15 +0200 [thread overview]
Message-ID: <20080930115315.GA2779@elte.hu> (raw)
In-Reply-To: <20080930094516.GA1276@elte.hu>
a third type of lockdep splat surfaced in -tip testing:
=============================================
[ INFO: possible recursive locking detected ]
2.6.27-rc8-tip #37560
---------------------------------------------
swapper/0 is trying to acquire lock:
(&cpu_buffer->lock){.+..}, at: [<ffffffff802906ac>] ring_buffer_lock+0x46/0x5e
but task is already holding lock:
(&cpu_buffer->lock){.+..}, at: [<ffffffff802906ac>] ring_buffer_lock+0x46/0x5e
other info that might help us debug this:
2 locks held by swapper/0:
#0: (&rq->lock){++..}, at: [<ffffffff80754540>] schedule+0x16f/0x839
#1: (&cpu_buffer->lock){.+..}, at: [<ffffffff802906ac>] ring_buffer_lock+0x46/0x5e
stack backtrace:
Pid: 0, comm: swapper Not tainted 2.6.27-rc8-tip #37560
Call Trace:
[<ffffffff802743b6>] __lock_acquire+0xb2a/0x116f
[<ffffffff80274a88>] lock_acquire+0x8d/0xba
[<ffffffff802906ac>] ring_buffer_lock+0x46/0x5e
[<ffffffff80756b7c>] _spin_lock+0x29/0x34
[<ffffffff802906ac>] ring_buffer_lock+0x46/0x5e
[<ffffffff8039d992>] __next_cpu+0x19/0x28
[<ffffffff802906ac>] ring_buffer_lock+0x46/0x5e
[<ffffffff80290762>] ring_buffer_reset+0x1c/0x58
[<ffffffff802942b9>] update_max_tr+0x5f/0x7f
[<ffffffff802954e0>] probe_wakeup_sched_switch+0x175/0x189
[<ffffffff80754aa8>] schedule+0x6d7/0x839
[<ffffffff80273de2>] __lock_acquire+0x556/0x116f
[<ffffffff807567bb>] trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff802732c8>] trace_hardirqs_on_caller+0xb4/0xd7
[<ffffffff807567bb>] trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff80269ea4>] ktime_get_ts+0x21/0x4a
[<ffffffff8026c44f>] getnstimeofday+0x38/0x98
[<ffffffff80269ea4>] ktime_get_ts+0x21/0x4a
[<ffffffff80227fc8>] native_sched_clock+0x8c/0xa6
[<ffffffff8026b485>] sched_clock_tick+0x78/0x80
[<ffffffff8027020f>] tick_nohz_restart_sched_tick+0x16b/0x178
[<ffffffff802732c8>] trace_hardirqs_on_caller+0xb4/0xd7
[<ffffffff8021fd70>] cpu_idle+0x77/0x79
driver: '2-0:1.0': driver_bound: bound to device 'hub'
Ingo
next prev parent reply other threads:[~2008-09-30 11:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 3:02 [PATCH 0/6] ftrace: port to the new ring_buffer Steven Rostedt
2008-09-30 3:02 ` [PATCH 1/6] ftrace: give time for wakeup test to run Steven Rostedt
2008-09-30 3:02 ` [PATCH 2/6] Unified trace buffer Steven Rostedt
2008-09-30 9:45 ` Ingo Molnar
2008-09-30 11:53 ` Ingo Molnar [this message]
2008-09-30 12:06 ` Steven Rostedt
2008-09-30 3:02 ` [PATCH 3/6] ring_buffer: add paranoid check for buffer page Steven Rostedt
2008-09-30 3:02 ` [PATCH 4/6] ring_buffer: reset buffer page when freeing Steven Rostedt
2008-09-30 3:02 ` [PATCH 5/6] ftrace: make work with new ring buffer Steven Rostedt
2008-09-30 3:02 ` [PATCH 6/6] ftrace: take advantage of variable length entries Steven Rostedt
2008-09-30 17:33 ` Pekka Paalanen
2008-09-30 17:45 ` Steven Rostedt
2008-10-01 4:42 ` Steven Rostedt
2008-10-01 7:54 ` Ingo Molnar
2008-10-01 14:52 ` Steven Rostedt
2008-10-01 14:52 ` [PATCH] ftrace: type cast verifier Steven Rostedt
2008-10-01 17:42 ` Ingo Molnar
2008-10-01 17:47 ` Ingo Molnar
2008-09-30 7:45 ` [PATCH 0/6] ftrace: port to the new ring_buffer Ingo Molnar
2008-09-30 8:23 ` Ingo Molnar
2008-09-30 8:30 ` Ingo Molnar
2008-09-30 9:13 ` Ingo Molnar
2008-09-30 12:04 ` Steven Rostedt
2008-09-30 12:04 ` 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:
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=20080930115315.GA2779@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox