From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Birger Lammering <lammering@planet-interkom.de>
Cc: linux-kernel@vger.kernel.org, birger.lammering@science-computing.de
Subject: Re: nfs problem: hp-server --- linux 2.4.13 client, ooops
Date: 16 Nov 2001 00:58:38 +0100 [thread overview]
Message-ID: <shssnbf37td.fsf@charged.uio.no> (raw)
In-Reply-To: <20011115222920.A9929@ludwig2.science-computing.de>
In-Reply-To: <20011115222920.A9929@ludwig2.science-computing.de>
>>>>> " " == Birger Lammering <lammering@planet-interkom.de> writes:
> Without the nfs patch I had a lot of trouble with Irix servers
> - now Irix, NetApp, Aix, Linux... nfs- servers are fine, but
> connecting to a HP server leads to statements like this in the
> syslog: NFS: short packet in readdir reply!
<snip>
> Unable to handle kernel paging request at virtual address
> fe01e000
> printing eip:
> f898eaed *pde = 00004063 *pte = 00000000 Oops: 0000 CPU: 1 EIP:
> 0010:[<f898eaed>] Not tainted EFLAGS: 00010296 eax: 01000000
> ebx: fe01dff8 ecx: fe01e000 edx: 00000019 esi: fe01e000 edi:
> 0000006c ebp: f537405c esp: f4e83c60 ds: 0018 es: 0018 ss: 0018
> Process ls (pid: 11091, stackpage=f4e83000) Stack: f4e83cec
> f518c200 f898ea4c f8956e07 f537405c f6a15240 f4e83d94 f4e83d40
> f4e83d54 f4e83cac 00000002 f895a18c f4e83cec f4e83cec
> fffffff5
> f4e83cec
> f518c200 f4e82000 f4e82000 00000000 f4e82000 f4e83d58
> f4e83d58
> f895a498 Call Trace: [<f898ea4c>] [<f8956e07>] [<f895a18c>]
> [<f895a498>] [<f895646e>]
> [<f8997520>] [<f89594e0>] [<f898e09e>] [<f8997520>]
> [<f898b89a>]
> [<c01299e8>]
> [<f898bc2b>] [<f898b7c0>] [<f898eb1c>] [<c0142bb4>]
> [<c0142f90>]
> [<c01430f3>]
That particular Oops should already be fixed in 2.4.14.
Cheers,
Trond
next prev parent reply other threads:[~2001-11-15 23:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 21:29 nfs problem: hp-server --- linux 2.4.13 client, ooops Birger Lammering
2001-11-15 23:58 ` Trond Myklebust [this message]
2001-11-16 11:24 ` nfs problem: hp|aix-server --- linux 2.4.15pre5 client Birger Lammering
2001-11-16 11:45 ` Trond Myklebust
2001-11-16 12:01 ` Miquel van Smoorenburg
2001-11-16 12:24 ` Trond Myklebust
2001-11-16 13:19 ` nfs problem: aix-server " Birger Lammering
[not found] ` <15349.39320.876188.274548@charged.uio.no>
2001-11-19 10:20 ` IPV4 socket layer, was: " Birger Lammering
2001-11-19 11:16 ` Alan Cox
2001-11-19 16:37 ` more tcpdumpinfo for nfs3 " Birger Lammering
2001-11-19 18:22 ` Trond Myklebust
2001-11-19 18:49 ` kuznet
2001-11-19 18:55 ` Trond Myklebust
2001-11-19 19:09 ` kuznet
2001-11-19 19:29 ` Trond Myklebust
2001-11-19 19:52 ` kuznet
2001-11-19 20:38 ` Trond Myklebust
2001-11-19 21:17 ` Trond Myklebust
2001-11-20 17:42 ` kuznet
2001-11-20 19:39 ` Trond Myklebust
2001-11-20 19:45 ` kuznet
2001-11-20 20:05 ` Trond Myklebust
2001-11-20 20:18 ` David S. Miller
2001-11-20 20:28 ` more tcpdumpinfo for nfs3 problem: aix-server --- linux kuznet
2001-11-20 20:29 ` more tcpdumpinfo for nfs3 problem: aix-server --- linux 2.4.15pre5 client Trond Myklebust
2001-11-21 10:07 ` Trond Myklebust
2001-11-21 17:05 ` kuznet
2001-11-20 17:41 ` kuznet
2001-11-20 9:26 ` Birger Lammering
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=shssnbf37td.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=birger.lammering@science-computing.de \
--cc=lammering@planet-interkom.de \
--cc=linux-kernel@vger.kernel.org \
/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.