From: Danny Smith <dannys@cinesite.co.uk>
To: "Brasseur Valéry" <Valery.Brasseur@atosorigin.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: linux 2.4.20 oops
Date: Tue, 29 Apr 2003 10:44:42 +0100 [thread overview]
Message-ID: <3EAE498A.1000106@cinesite.co.uk> (raw)
In-Reply-To: <8147E1B07201DD41B6B9F0D31E07B384449055@srv-grp-s07.dev.atos.fr>
Brasseur Val=E9ry wrote:
>I have got this oops in my kernel (2.4.20 + NFS-ALL )
>note : the oops are not log in syslog (don't know why !)
>but the oops seems nfs-related, any ideas ?
>
We had almost identical oopses with the same setup on our dual render box=
es,
which would often panic almost immediately afterwards.
We used this patch from Ulrich Weigand (weigand@informatik.uni-erlangen.d=
e), and
haven't seen a problem since. See the archives for full details - basical=
ly seems
to be an SMP race in rpc_delete_timer(). If you're not on an SMP system,
it's probably NOT the right fix.
HTH,
Danny
Index: net/sunrpc/sched.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /home/cvs/linux-2.3/net/sunrpc/sched.c,v
retrieving revision 1.13
diff -u -p -r1.13 sched.c
--- net/sunrpc/sched.c 3 May 2001 16:18:18 -0000 1.13
+++ net/sunrpc/sched.c 8 Mar 2003 22:46:11 -0000
@@ -168,10 +168,8 @@ void rpc_add_timer(struct rpc_task *task
static inline void
rpc_delete_timer(struct rpc_task *task)
{
- if (timer_pending(&task->tk_timer)) {
+ if (del_timer_sync(&task->tk_timer))
dprintk("RPC: %4d deleting timer\n", task->tk_pid);
- del_timer_sync(&task->tk_timer);
- }
}
=20
/*
--=20
Danny Smith
Senior Systems Administrator, Cinesite (Europe) Ltd
020 7973 4000 - x4055 / dannys@cinesite.co.uk
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-04-29 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 9:18 linux 2.4.20 oops Brasseur Valéry
2003-04-29 9:44 ` Danny Smith [this message]
2003-04-29 16:31 ` Philippe Troin
2003-04-29 16:44 ` Danny Smith
2003-04-29 16:53 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2003-04-29 9:46 Brasseur Valéry
2003-04-29 16:56 Lever, Charles
2003-04-29 17:04 ` Trond Myklebust
[not found] <6440EA1A6AA1D5118C6900902745938E07D5559A@black.eng.netapp.com>
2003-04-29 17:21 ` Trond Myklebust
2003-04-29 17:24 Lever, Charles
2003-04-29 17:31 Lever, Charles
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=3EAE498A.1000106@cinesite.co.uk \
--to=dannys@cinesite.co.uk \
--cc=Valery.Brasseur@atosorigin.com \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.