From: Philippe Troin <phil@fifi.org>
To: Danny Smith <dannys@cinesite.co.uk>
Cc: "Brasseur Valéry" <Valery.Brasseur@atosorigin.com>,
nfs@lists.sourceforge.net
Subject: Re: linux 2.4.20 oops
Date: 29 Apr 2003 09:31:08 -0700 [thread overview]
Message-ID: <87of2pxo37.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <3EAE498A.1000106@cinesite.co.uk>
Danny Smith <dannys@cinesite.co.uk> writes:
> Brasseur Val=E9ry wrote:
>=20
> >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 ?
>=20
> We had almost identical oopses with the same setup on our dual
> render boxes, which would often panic almost immediately afterwards.
>=20
> We used this patch from Ulrich Weigand
> (weigand@informatik.uni-erlangen.de), and haven't seen a problem
> since. See the archives for full details - basically 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.
Has this been pushed to 2.4.21?
Phil.
-------------------------------------------------------
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 16:31 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
2003-04-29 16:31 ` Philippe Troin [this message]
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=87of2pxo37.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=Valery.Brasseur@atosorigin.com \
--cc=dannys@cinesite.co.uk \
--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.