summaryrefslogtreecommitdiff
path: root/Documentation/riscom8.txt
diff options
context:
space:
mode:
authorAndi Kleen <andi@firstfloor.org>2008-08-29 18:06:23 (GMT)
committerLinus Torvalds <torvalds@linux-foundation.org>2008-08-29 21:46:29 (GMT)
commit316d9679f33caf7e683471647d1472bfe133d858 (patch)
tree46271cdd7405468fbc4e9abbaf65e01edd6ae0a3 /Documentation/riscom8.txt
parentb4609472116bb806a95e98d04767189406c74c70 (diff)
downloadlinux-fsl-qoriq-316d9679f33caf7e683471647d1472bfe133d858.tar.xz
Don't trigger softlockup detector on network fs blocked tasks
Pulling the ethernet cable on a 2.6.27-rc system with NFS mounts currently leads to an ongoing flood of soft lockup detector backtraces for all tasks blocked on the NFS mounts when the hickup takes longer than 120s. I don't think NFS problems should be all that noisy. Luckily there's a reasonably easy way to distingush this case. Don't report task softlockup warnings for tasks in TASK_KILLABLE state, which is used by the network file systems. I believe this patch is a 2.6.27 candidate. Signed-off-by: Andi Kleen <ak@linux.intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/riscom8.txt')
0 files changed, 0 insertions, 0 deletions