From: Chuck Ebbert <cebbert@redhat.com>
To: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <balbir@in.ibm.com>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: System hangs on running kernbench
Date: Wed, 18 Jul 2007 11:08:18 -0400 [thread overview]
Message-ID: <469E2CE2.3070805@redhat.com> (raw)
In-Reply-To: <20070718094142.GA12330@linux.vnet.ibm.com>
On 07/18/2007 05:41 AM, Dhaval Giani wrote:
> On Wed, Jul 18, 2007 at 01:07:00AM -0700, Andrew Morton wrote:
>> On Wed, 18 Jul 2007 13:26:48 +0530 Dhaval Giani <dhaval@linux.vnet.ibm.com> wrote:
>>
>>> I was running kernbench on top of 2.6.22-rc6-mm1 and I got a Hangcheck
>>> alert (This is when kernbench reached make -j).
>> hm, never had a report of that before. It's the first time I've seen
>> hangcheck produce anything useful, frankly.
>>
>> Was the softlockup detector not enabled?
>
> I notice CONFIG_DETECT_SOFTLOCKUP=y
>>> Also make -j is hanging.
>> Please try to capture the full sysrq-T output when it is hung.
>
> Available at http://dhaval.giani.googlepages.com/sysrq-t-trace.bz2
>
> In the meantime I will go and check if it was there in 2.6.22-rc4-mm2
>
Softlockup is broken in 2.6.22.
=======================================================================
Subject: fix the softlockup watchdog to actually work
From: Ingo Molnar <mingo@elte.hu>
this Xen related commit:
commit 966812dc98e6a7fcdf759cbfa0efab77500a8868
Author: Jeremy Fitzhardinge <jeremy@goop.org>
Date: Tue May 8 00:28:02 2007 -0700
Ignore stolen time in the softlockup watchdog
broke the softlockup watchdog to never report any lockups. (!)
print_timestamp defaults to 0, this makes the following condition
always true:
if (print_timestamp < (touch_timestamp + 1) ||
and we'll in essence never report soft lockups.
apparently the functionality of the soft lockup watchdog was never
actually tested with that patch applied ...
[this is -stable material too.]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/softlockup.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
Index: linux/kernel/softlockup.c
===================================================================
--- linux.orig/kernel/softlockup.c
+++ linux/kernel/softlockup.c
@@ -79,10 +79,11 @@ void softlockup_tick(void)
print_timestamp = per_cpu(print_timestamp, this_cpu);
/* report at most once a second */
- if (print_timestamp < (touch_timestamp + 1) ||
- did_panic ||
- !per_cpu(watchdog_task, this_cpu))
+ if ((print_timestamp >= touch_timestamp &&
+ print_timestamp < (touch_timestamp + 1)) ||
+ did_panic || !per_cpu(watchdog_task, this_cpu)) {
return;
+ }
/* do not print during early bootup: */
if (unlikely(system_state != SYSTEM_RUNNING)) {
next prev parent reply other threads:[~2007-07-18 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 7:56 System hangs on running kernbench Dhaval Giani
2007-07-18 8:07 ` Andrew Morton
2007-07-18 9:41 ` Dhaval Giani
2007-07-18 14:46 ` Dhaval Giani
2007-07-19 6:28 ` Dhaval Giani
2007-07-19 6:34 ` Dhaval Giani
2007-07-18 15:08 ` Chuck Ebbert [this message]
2007-07-19 4:47 ` Dhaval Giani
2007-07-24 7:13 ` Srivatsa Vaddagiri
2007-07-24 8:19 ` Ingo Molnar
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=469E2CE2.3070805@redhat.com \
--to=cebbert@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vatsa@linux.vnet.ibm.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