[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090807113349.GA31673@elte.hu>
Date: Fri, 7 Aug 2009 13:33:49 +0200
From: Ingo Molnar <mingo@...e.hu>
To: "Metzger, Markus T" <markus.t.metzger@...el.com>
Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"hpa@...or.com" <hpa@...or.com>,
"markus.t.metzger@...il.com" <markus.t.metzger@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [patch] x86, perf_counter, bts: add bts to perf_counter
* Ingo Molnar <mingo@...e.hu> wrote:
> * Metzger, Markus T <markus.t.metzger@...el.com> wrote:
>
> > Ingo, what exactly do you mean by "locks up"? Is the kernel
> > hanging or is perf record hanging?
>
> it was a hard hang - box was not pingable, etc.
the moment i tried kernel-mode BTS tracing (i.e. -e branches, not -e
branches:u) it hung hard again:
titan:~> perf record -o /dev/null -f -e branches -c 1 ./loop_1b_instructions
this time i had a serial console attached - there's a perfcounters
warning prior the hang - attached below. Peter, any ideas?
Ingo
[ 995.556131] ------------[ cut here ]------------
[ 995.557128] WARNING: at kernel/perf_counter.c:1191 __perf_counter_task_sched_out+0x48/0x6b()
[ 995.557128] Hardware name:
[ 995.557128] Modules linked in:
[ 995.557128] Pid: 2008, comm: perf Tainted: G M 2.6.31-rc5-tip #1350
[ 995.557128] Call Trace:
[ 995.557128] <IRQ> [<ffffffff810a20d9>] ? __perf_counter_task_sched_out+0x48/0x6b
[ 995.557128] [<ffffffff81044880>] warn_slowpath_common+0x77/0xa4
[ 995.557128] [<ffffffff810448bc>] warn_slowpath_null+0xf/0x11
[ 995.557128] [<ffffffff810a20d9>] __perf_counter_task_sched_out+0x48/0x6b
[ 995.557128] [<ffffffff810a4c75>] perf_counter_task_tick+0x61/0x9d
[ 995.557128] [<ffffffff810408b1>] scheduler_tick+0x112/0x237
[ 995.557128] [<ffffffff8104eb58>] update_process_times+0x4f/0x60
[ 995.557128] [<ffffffff81065186>] tick_sched_timer+0x6e/0x8e
[ 995.557128] [<ffffffff8105bff5>] __run_hrtimer+0x71/0xa5
[ 995.557128] [<ffffffff8105c23f>] hrtimer_interrupt+0xef/0x149
[ 995.557128] [<ffffffff810208b8>] smp_apic_timer_interrupt+0x83/0x96
[ 995.557128] [<ffffffff8100c6b3>] apic_timer_interrupt+0x13/0x20
[ 995.557128] <EOI> [<ffffffff811465ac>] ? __log_space_left+0x0/0x2f
[ 995.557128] [<ffffffff811439a6>] ? start_this_handle+0x302/0x373
[ 995.557128] [<ffffffff810a6e09>] ? lock_page+0x11/0x29
[ 995.557128] [<ffffffff81143b66>] ? journal_start+0x95/0xc5
[ 995.557128] [<ffffffff8113d67f>] ? ext3_journal_start_sb+0x4a/0x4c
[ 995.557128] [<ffffffff81135d3e>] ? ext3_write_begin+0x9c/0x1e2
[ 995.557128] [<ffffffff810a66ef>] ? generic_perform_write+0xb4/0x1a7
[ 995.557128] [<ffffffff810a7dc8>] ? generic_file_buffered_write+0x6d/0x10c
[ 995.557128] [<ffffffff810a825c>] ? __generic_file_aio_write_nolock+0x25e/0x292
[ 995.557128] [<ffffffff810efa74>] ? mntput_no_expire+0x24/0xe8
[ 995.557128] [<ffffffff810a86a4>] ? generic_file_aio_write+0x67/0xc3
[ 995.557128] [<ffffffff811313ff>] ? ext3_file_write+0x1e/0x9f
[ 995.557128] [<ffffffff810da4dc>] ? do_sync_write+0xe7/0x12d
[ 995.557128] [<ffffffff8111f6d4>] ? show_map_vma+0x1c1/0x1d0
[ 995.557128] [<ffffffff811dabfa>] ? __up_read+0x9e/0xa8
[ 995.557128] [<ffffffff81059a10>] ? autoremove_wake_function+0x0/0x38
[ 995.557128] [<ffffffff8111e941>] ? m_stop+0x2b/0x4d
[ 995.557128] [<ffffffff8119a140>] ? security_file_permission+0x11/0x13
[ 995.557128] [<ffffffff810daeb8>] ? vfs_write+0xab/0x105
[ 995.557128] [<ffffffff810dafd6>] ? sys_write+0x47/0x6f
[ 995.557128] [<ffffffff8100bbab>] ? system_call_fastpath+0x16/0x1b
[ 995.557128] ---[ end trace ff0d385da11eb1c5 ]---
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists