From: Vegard Nossum <vegard.nossum@gmail.com>
To: Johannes Weiner <hannes@saeurebad.de>,
Arjan van de Ven <arjan@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, linux-kernel@vger.kernel.org
Subject: [PATCH] softlockup: show irqtrace
Date: Wed, 25 Jun 2008 09:13:23 +0200 [thread overview]
Message-ID: <20080625071323.GA7987@damson.getinternet.no> (raw)
Hi,
Ingo, can you please drop the "softirq softlockup debugging" patch and
apply this instead? This much, much prettier, reuses existing debugging
infrastructure, and is a lot more generic.
(Compile tested on allyesconfig, allnoconfig, allnoconfig + softlockup
debugging.)
Vegard
From: Vegard Nossum <vegard.nossum@gmail.com>
Date: Wed, 25 Jun 2008 08:50:10 +0200
Subject: [PATCH] softlockup: show irqtrace
This patch adds some information about when interrupts were last
enabled and disabled to the output of the softlockup detector.
Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
---
kernel/softlockup.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/kernel/softlockup.c b/kernel/softlockup.c
index 01b6522..980f703 100644
--- a/kernel/softlockup.c
+++ b/kernel/softlockup.c
@@ -13,6 +13,7 @@
#include <linux/delay.h>
#include <linux/freezer.h>
#include <linux/kthread.h>
+#include <linux/lockdep.h>
#include <linux/notifier.h>
#include <linux/module.h>
@@ -115,6 +116,7 @@ void softlockup_tick(void)
printk(KERN_ERR "BUG: soft lockup - CPU#%d stuck for %lus! [%s:%d]\n",
this_cpu, now - touch_timestamp,
current->comm, task_pid_nr(current));
+ print_irqtrace_events(current);
if (regs)
show_regs(regs);
else
--
1.5.4.1
next reply other threads:[~2008-06-25 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 7:13 Vegard Nossum [this message]
2008-06-25 16:00 ` [PATCH] softlockup: show irqtrace Ingo Molnar
2008-06-25 17:11 ` Vegard Nossum
2008-06-25 21:15 ` Johannes Weiner
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=20080625071323.GA7987@damson.getinternet.no \
--to=vegard.nossum@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@linux.intel.com \
--cc=hannes@saeurebad.de \
--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.