From: Frederic Weisbecker <fweisbec@gmail.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [BUG] perf: hard lockup when using perf-sched
Date: Fri, 26 Mar 2010 22:45:44 +0100 [thread overview]
Message-ID: <20100326214542.GF7166@nowhere> (raw)
In-Reply-To: <1269634924.6488.6.camel@marge.simson.net>
On Fri, Mar 26, 2010 at 09:22:04PM +0100, Mike Galbraith wrote:
> [ 427.931717] <IRQ>
> [ 427.931717] [<ffffffff811403f4>] __delay+0xa/0xc
> [ 427.931717] [<ffffffff81143e42>] do_raw_spin_lock+0xd2/0x13c
> [ 427.931717] [<ffffffff812dbc18>] _raw_spin_lock+0x34/0x3b
> [ 427.931717] [<ffffffff81026e03>] ? task_rq_lock+0x7c/0x97
> [ 427.931717] [<ffffffff8105f2b1>] ? trace_hardirqs_on+0xd/0xf
> [ 427.931717] [<ffffffff81026e03>] task_rq_lock+0x7c/0x97
> [ 427.931717] [<ffffffff8102d4a5>] try_to_wake_up+0x26/0x266
> [ 427.931717] [<ffffffff8102d704>] wake_up_process+0x10/0x12
> [ 427.931717] [<ffffffff810392f4>] wakeup_softirqd+0x2a/0x2c
> [ 427.931717] [<ffffffff81039771>] __do_softirq+0x21e/0x220
> [ 427.931717] [<ffffffff8104b6a0>] ? __task_pid_nr_ns+0x0/0xad
> [ 427.931717] [<ffffffff81002e0c>] call_softirq+0x1c/0x28
> [ 427.931717] [<ffffffff81004b73>] do_softirq+0x38/0x81
> [ 427.931717] [<ffffffff8103983a>] irq_exit+0x45/0x87
> [ 427.931717] [<ffffffff81016f86>] smp_apic_timer_interrupt+0x88/0x96
> [ 427.931717] [<ffffffff810028d3>] apic_timer_interrupt+0x13/0x20
> [ 427.931717] <EOI>
> [ 427.931717] [<ffffffff8105eae6>] ? lock_acquire+0x108/0x117
> [ 427.931717] [<ffffffff8104b6a0>] ? __task_pid_nr_ns+0x0/0xad
> [ 427.931717] [<ffffffff810892f9>] ? perf_output_begin+0x0/0x24d
> [ 427.931717] [<ffffffff8104b6dc>] __task_pid_nr_ns+0x3c/0xad
> [ 427.931717] [<ffffffff8104b6a0>] ? __task_pid_nr_ns+0x0/0xad
> [ 427.931717] [<ffffffff8108668a>] perf_event_tid+0x26/0x28
> [ 427.931717] [<ffffffff8108960f>] perf_event_task_output+0x74/0x9f
> [ 427.931717] [<ffffffff81089675>] perf_event_task_ctx+0x3b/0x5b
> [ 427.931717] [<ffffffff810896e8>] perf_event_task_event+0x53/0xca
> [ 427.931717] [<ffffffff81089695>] ? perf_event_task_event+0x0/0xca
> [ 427.931717] [<ffffffff810897da>] perf_event_task+0x7b/0x86
> [ 427.931717] [<ffffffff8108a90e>] perf_event_fork+0x10/0x12
Aaah, I see now. That happens during a fork event!
So that looks indeed the right fix.
next prev parent reply other threads:[~2010-03-26 21:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 7:21 [BUG] perf: hard lockup when using perf-sched Li Zefan
2010-03-24 5:52 ` Li Zefan
2010-03-24 7:32 ` Mike Galbraith
2010-03-24 8:17 ` Mike Galbraith
2010-03-25 8:04 ` Li Zefan
2010-03-25 9:27 ` Mike Galbraith
2010-03-25 9:54 ` Peter Zijlstra
2010-03-26 10:11 ` Mike Galbraith
2010-03-26 17:23 ` Frederic Weisbecker
2010-03-26 19:10 ` Mike Galbraith
2010-03-26 19:27 ` Frederic Weisbecker
2010-03-26 20:22 ` Mike Galbraith
2010-03-26 21:41 ` Frederic Weisbecker
2010-03-26 21:45 ` Frederic Weisbecker [this message]
2010-03-29 2:01 ` Li Zefan
2010-04-02 19:07 ` [tip:perf/core] perf: Fix 'perf sched record' deadlock tip-bot for Mike Galbraith
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=20100326214542.GF7166@nowhere \
--to=fweisbec@gmail.com \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.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