public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mandeep Singh Baines <msb@google.com>
Subject: [PATCH] softlockup: re-increase hung tasks check from 2 minutes to 8 minutes
Date: Fri, 06 May 2011 11:35:26 -0400	[thread overview]
Message-ID: <4DC4153E.5020304@suse.com> (raw)

 Commit e162b39a, which moved the soft lockup code around a bit,
 accidentally reverted commit fb822db4, which extended the soft lockup
 timeout from 2 minutes to 8 minutes.

 This patch restores it to 8 minutes.

 From the original patch:
 >Andrew says:
 >
 >> Seems that about 100% of the reports we get of this warning triggering
 >> are sys_sync, transaction commit, etc.
 >
 >increase the timeout. If it still triggers for people, we can kill it.

Originally-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
---

 kernel/hung_task.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/kernel/hung_task.c
+++ b/kernel/hung_task.c
@@ -33,7 +33,7 @@ unsigned long __read_mostly sysctl_hung_
 /*
  * Zero means infinite timeout - no checking done:
  */
-unsigned long __read_mostly sysctl_hung_task_timeout_secs = 120;
+unsigned long __read_mostly sysctl_hung_task_timeout_secs = 480;
 
 unsigned long __read_mostly sysctl_hung_task_warnings = 10;
 
-- 
Jeff Mahoney
SUSE Labs

             reply	other threads:[~2011-05-06 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 15:35 Jeff Mahoney [this message]
2011-05-06 19:18 ` [PATCH] softlockup: re-increase hung tasks check from 2 minutes to 8 minutes Ingo Molnar
2011-05-06 19:48   ` Jeff Mahoney
2011-05-10  7:57     ` Ingo Molnar
2011-05-09 20:57 ` Andrew Morton

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=4DC4153E.5020304@suse.com \
    --to=jeffm@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=msb@google.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