From: David Ford <david+powerix@blue-labs.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Oleg Drokin <green@namesys.com>, Hans Reiser <reiser@namesys.com>
Subject: Re: [OOPS] 100% repeatable OOPS, 2.5.61-66, NFS and reiserfs
Date: Tue, 08 Apr 2003 17:47:15 -0400 [thread overview]
Message-ID: <3E934363.3040507@blue-labs.org> (raw)
In-Reply-To: <16018.1797.59286.752771@notabene.cse.unsw.edu.au>
The latest 2.5 kernel being .67?
Yes, dev kernels are like that... but I'm not going to get into my
angst over 'release' kernels and NFS ;)
david
Neil Brown wrote:
>On Tuesday April 8, david+powerix@blue-labs.org wrote:
>
>
>>1. Power loss this morning
>>2. Fixed filesystems (reiserfstools is fscking useless on root filesystems)
>>3. Now server OOPSes when nfs client tries to stat/read files/dirs
>>
>>Unable to handle kernel NULL pointer dereference at virtual address 00000000
>> printing eip:
>>00000000
>>*pde = 00000000
>>Oops: 0000
>>CPU: 0
>>EIP: 0060:[<00000000>] Not tainted
>>
>>
>
>Development kernels are like that....
>
> This is a bug in the kernel which is triggered by using nfs-utils
> 1.0.3
>
> Either upgrade to the latest 2.5 kernel, or downgrade nfs-utils until
> you can upgrade the kernel.
>
>NeilBrown
>
>
next prev parent reply other threads:[~2003-04-08 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 16:31 [OOPS] 100% repeatable OOPS, 2.5.61-66, NFS and reiserfs David Ford
2003-04-07 23:17 ` Neil Brown
2003-04-08 21:47 ` David Ford [this message]
2003-04-08 3:38 ` Neil Brown
2003-04-08 3:44 ` David Ford
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=3E934363.3040507@blue-labs.org \
--to=david+powerix@blue-labs.org \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=reiser@namesys.com \
--cc=trond.myklebust@fys.uio.no \
/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.