On Sunday November 6, [email protected] wrote:
> Hi
>
> I regularly get these on the current 2.6.14 kernel under heavy load.
> Backtrace differs, but nfsd is always involved:
>
> Nov 4 12:46:44 p133 kernel: BUG: soft lockup detected on CPU#0!
This seems to suggest that the nfsd thread is always runnable, which
implies a read-only load with everything in cache - at least for the
10 seconds leading up to each of these errors. Is that likely?
The following patch might fix it. Please let me know the result.
Thanks,
NeilBrown
Signed-off-by: Neil Brown <[email protected]>
### Diffstat output
./net/sunrpc/svcsock.c | 1 +
1 file changed, 1 insertion(+)
diff ./net/sunrpc/svcsock.c~current~ ./net/sunrpc/svcsock.c
--- ./net/sunrpc/svcsock.c~current~ 2005-11-07 08:53:40.000000000 +1100
+++ ./net/sunrpc/svcsock.c 2005-11-07 08:53:48.000000000 +1100
@@ -1181,6 +1181,7 @@ svc_recv(struct svc_serv *serv, struct s
arg->tail[0].iov_len = 0;
try_to_freeze();
+ cond_resched();
if (signalled())
return -EINTR;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
