From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Ingo Molnar <mingo@elte.hu>, a.p.zijlstra@chello.nl
Cc: linux-kernel@vger.kernel.org
Subject: perf counter issue - WARN_ON_ONCE(!list_empty(&tsk->perf_counter_ctx.counter_list));
Date: Wed, 13 May 2009 22:24:33 +0530 [thread overview]
Message-ID: <20090513165433.GD16373@in.ibm.com> (raw)
I am hitting this warning in kernel/exit.c (latest -tip code):
WARN_ON_ONCE(!list_empty(&tsk->perf_counter_ctx.counter_list));
I was using perf counters against a java benchmark. Any suggestions for
me to try out?
Full stack-traceback is below:
WARNING: at kernel/exit.c:158 delayed_put_task_struct+0x34/0x7c()
Hardware name: IBM System x3550 -[79787AA]-
Modules linked in: autofs4 hidp rfcomm l2cap bluetooth sunrpc ipv6
cpufreq_ondemand acpi_cpufreq freq_table dm_mirror dm_multipath scsi_dh
sbs sbshc battery acpi_memhotplug ac parport_pc lp parport sg sr_mod
bnx2 ide_cd_mod cdrom button rtc_cmos rtc_core rtc_lib i2c_i801 i2c_core
i5000_edac edac_core pcspkr dm_region_hash dm_log dm_mod usb_storage
ata_piix libata shpchp aacraid sd_mod scsi_mod ext3 jbd uhci_hcd
ohci_hcd ehci_hcd [last unloaded: microcode]
Pid: 0, comm: swapper Not tainted 2.6.30-rc5-tip #12
Call Trace:
<IRQ> [<ffffffff8023eab8>] ? warn_slowpath_fmt+0xd9/0xf6
[<ffffffff80351233>] ? cpumask_next_and+0x2a/0x3b
[<ffffffff80233de3>] ? find_busiest_group+0x1e6/0x82a
[<ffffffff802535fc>] ? lock_hrtimer_base+0x1b/0x3c
[<ffffffff802886d6>] ? __perf_counter_sched_in+0x1c/0x143
[<ffffffff802181f0>] ? x86_pmu_enable+0x136/0x161
[<ffffffff80287a19>] ? counter_sched_in+0x26/0x8e
[<ffffffff8028804d>] ? group_sched_in+0x54/0xe2
[<ffffffff80256ec6>] ? getnstimeofday+0x56/0xb5
[<ffffffff80240193>] ? delayed_put_task_struct+0x34/0x7c
[<ffffffff80272af6>] ? __rcu_process_callbacks+0x101/0x1ac
[<ffffffff80272bc7>] ? rcu_process_callbacks+0x26/0x4a
[<ffffffff80243eed>] ? __do_softirq+0xa3/0x162
[<ffffffff8020ca3c>] ? call_softirq+0x1c/0x28
[<ffffffff8020dcc6>] ? do_softirq+0x2c/0x68
[<ffffffff8021e7b8>] ? smp_apic_timer_interrupt+0x8d/0x9d
[<ffffffff8020c413>] ? apic_timer_interrupt+0x13/0x20
<EOI> [<ffffffff80211ed0>] ? mwait_idle+0xa3/0xd1
[<ffffffff804cd309>] ? notifier_call_chain+0x29/0x4c
[<ffffffff8020aa1d>] ? cpu_idle+0x40/0x5e
---[ end trace 026134fcfb5c588d ]---
WARNING: at kernel/exit.c:158 delayed_put_task_struct+0x34/0x7c()
Hardware name: IBM System x3550 -[79787AA]-
Modules linked in: autofs4 hidp rfcomm l2cap bluetooth sunrpc ipv6
cpufreq_ondemand acpi_cpufreq freq_table dm_mirror dm_multipath scsi_dh
sbs sbshc battery acpi_memhotplug ac parport_pc lp parport sg sr_mod
bnx2 ide_cd_mod cdrom button rtc_cmos rtc_core rtc_lib i2c_i801 i2c_core
i5000_edac edac_core pcspkr dm_region_hash dm_log dm_mod usb_storage
ata_piix libata shpchp aacraid sd_mod scsi_mod ext3 jbd uhci_hcd
ohci_hcd ehci_hcd [last unloaded: microcode]
Pid: 0, comm: swapper Tainted: G W 2.6.30-rc5-tip #12
Call Trace:
<IRQ> [<ffffffff8023eab8>] ? warn_slowpath_fmt+0xd9/0xf6
[<ffffffff80351233>] ? cpumask_next_and+0x2a/0x3b
[<ffffffff80233de3>] ? find_busiest_group+0x1e6/0x82a
[<ffffffff80230df4>] ? update_curr+0x6f/0xab
[<ffffffff802303b4>] ? wakeup_preempt_entity+0xb5/0xc2
[<ffffffff8023b994>] ? check_preempt_wakeup+0x118/0x135
[<ffffffff802535fc>] ? lock_hrtimer_base+0x1b/0x3c
[<ffffffff8025359d>] ? hrtimer_init+0x18/0x5c
[<ffffffff80288d1a>] ? task_clock_perf_counter_enable+0x29/0x57
[<ffffffff80287eec>] ? perf_swcounter_enable+0x5/0x8
[<ffffffff80287a19>] ? counter_sched_in+0x26/0x8e
[<ffffffff8028804d>] ? group_sched_in+0x54/0xe2
[<ffffffff80256ec6>] ? getnstimeofday+0x56/0xb5
[<ffffffff80240193>] ? delayed_put_task_struct+0x34/0x7c
[<ffffffff80272af6>] ? __rcu_process_callbacks+0x101/0x1ac
[<ffffffff80272bc7>] ? rcu_process_callbacks+0x26/0x4a
[<ffffffff80243eed>] ? __do_softirq+0xa3/0x162
[<ffffffff8020ca3c>] ? call_softirq+0x1c/0x28
[<ffffffff8020dcc6>] ? do_softirq+0x2c/0x68
[<ffffffff8021e7b8>] ? smp_apic_timer_interrupt+0x8d/0x9d
[<ffffffff8020c413>] ? apic_timer_interrupt+0x13/0x20
<EOI> [<ffffffff80211ed0>] ? mwait_idle+0xa3/0xd1
[<ffffffff804cd309>] ? notifier_call_chain+0x29/0x4c
[<ffffffff8020aa1d>] ? cpu_idle+0x40/0x5e
---[ end trace 026134fcfb5c588e ]---
- vatsa
next reply other threads:[~2009-05-13 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 16:54 Srivatsa Vaddagiri [this message]
2009-05-13 16:57 ` perf counter issue - WARN_ON_ONCE(!list_empty(&tsk->perf_counter_ctx.counter_list)); Srivatsa Vaddagiri
2009-05-15 13:56 ` Ingo Molnar
2009-05-15 14:51 ` Arnaldo Carvalho de Melo
2009-05-15 15:58 ` Srivatsa Vaddagiri
2009-05-15 16:13 ` Peter Zijlstra
2009-05-15 17:37 ` Peter Zijlstra
2009-05-15 20:27 ` Peter Zijlstra
2009-05-18 4:45 ` Paul Mackerras
2009-05-22 6:25 ` Srivatsa Vaddagiri
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=20090513165433.GD16373@in.ibm.com \
--to=vatsa@in.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.