From: Chuansheng Liu <chuansheng.liu@intel.com>
To: tglx@linutronix.de, mingo@kernel.org, a.p.zijlstra@chello.nl
Cc: linux-kernel@vger.kernel.org, fei.li@intel.com,
yanmin_zhang@linux.intel.com, chuansheng.liu@intel.com
Subject: [PATCH] hrtimer: Printing timer info when hitting BUG_ON()
Date: Mon, 29 Oct 2012 19:02:31 +0800 [thread overview]
Message-ID: <1351508551.15558.1428.camel@cliu38-desktop-build> (raw)
We encounted one BUG_ON() issue at function __run_hrtimer(),
but the panic info is not enough to find out which hrtimer
users use the hrtimer wrongly.
(in this BUG_ON case, it is callback running at the same time
hrtimer_start() is executed on different context.)
We can print basic timer info before BUG(), it is easy to find
out which hrtimer user has fault, the output info is like below:
<3>[ 41.118552] timer info: state/3, func/test_timer_cb
<3>[ 41.118618] timer stats: pid/786(sh), site/hrtimer_start
<0>[ 41.118670] ------------[ cut here ]------------
<2>[ 41.118691] kernel BUG at /root/r4_code/hardware/intel/linux-2.6/kernel/hrtimer.c:1260!
<0>[ 41.118715] invalid opcode: 0000 [#1] PREEMPT SMP
The infos of callback/state are very helpful for debugging this BUG_ON().
Signed-off-by: Li Fei <fei.li@intel.com>
Signed-off-by: liu chuansheng <chuansheng.liu@intel.com>
---
kernel/hrtimer.c | 34 +++++++++++++++++++++++++++++++++-
1 files changed, 33 insertions(+), 1 deletions(-)
diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index 6db7a5e..388e8b2 100644
--- a/kernel/hrtimer.c
+++ b/kernel/hrtimer.c
@@ -1204,6 +1204,35 @@ int hrtimer_get_res(const clockid_t which_clock, struct timespec *tp)
}
EXPORT_SYMBOL_GPL(hrtimer_get_res);
+/*
+ * dump_hrtimer_callinfo - print hrtimer information including:
+ * state, callback function, pid and start_site.
+*/
+static void dump_hrtimer_callinfo(struct hrtimer *timer)
+{
+
+ char symname[KSYM_NAME_LEN];
+
+ if (lookup_symbol_name((unsigned long)(timer->function), symname) < 0) {
+ pr_err("timer info: state/%lx, func/%pK\n",
+ timer->state, timer->function);
+ } else {
+ pr_err("timer info: state/%lx, func/%s",
+ timer->state, symname);
+ }
+
+#ifdef CONFIG_TIMER_STATS
+ if (lookup_symbol_name((unsigned long)(timer->start_site),
+ symname) < 0) {
+ pr_err("timer stats: pid/%d(%s), site/%pK\n",
+ timer->start_pid, timer->start_comm, timer->start_site);
+ } else {
+ pr_err("timer stats: pid/%d(%s), site/%s\n",
+ timer->start_pid, timer->start_comm, symname);
+ }
+#endif
+}
+
static void __run_hrtimer(struct hrtimer *timer, ktime_t *now)
{
struct hrtimer_clock_base *base = timer->base;
@@ -1235,7 +1264,10 @@ static void __run_hrtimer(struct hrtimer *timer, ktime_t *now)
* hrtimer_start_range_ns() or in hrtimer_interrupt()
*/
if (restart != HRTIMER_NORESTART) {
- BUG_ON(timer->state != HRTIMER_STATE_CALLBACK);
+ if (timer->state != HRTIMER_STATE_CALLBACK) {
+ dump_hrtimer_callinfo(timer);
+ BUG();
+ }
enqueue_hrtimer(timer, base);
}
--
1.7.0.4
next reply other threads:[~2012-10-29 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 11:02 Chuansheng Liu [this message]
2012-10-29 9:05 ` Peter Zijlstra
2012-10-30 4:55 ` Liu, Chuansheng
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=1351508551.15558.1428.camel@cliu38-desktop-build \
--to=chuansheng.liu@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=fei.li@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=yanmin_zhang@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®