summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorIngo Molnar <mingo@elte.hu>2008-08-20 11:17:40 +0200
committerIngo Molnar <mingo@elte.hu>2008-09-10 09:08:51 +0200
commitfb822db465bd9fd4208eef1af4490539b236c54e (patch)
treeb2fdd23878b0a6d082ad3e9f70ee5c0e1a96b96c /kernel
parent1b2439dbb703ae8d95a9ce7ece6b7800b80f41f0 (diff)
downloadlinux-fb822db465bd9fd4208eef1af4490539b236c54e.tar.gz
linux-fb822db465bd9fd4208eef1af4490539b236c54e.tar.bz2
linux-fb822db465bd9fd4208eef1af4490539b236c54e.zip
softlockup: increase hung tasks check from 2 minutes to 8 minutes
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. Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel')
-rw-r--r--kernel/softlockup.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/softlockup.c b/kernel/softlockup.c
index b75b492fbfcf..17a058065331 100644
--- a/kernel/softlockup.c
+++ b/kernel/softlockup.c
@@ -164,7 +164,7 @@ unsigned long __read_mostly sysctl_hung_task_check_count = 1024;
/*
* 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;