From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: war <war@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Panic (NFS, 2.4.2[0-1])
Date: 11 Aug 2003 08:07:15 -0700 [thread overview]
Message-ID: <shsd6fcz10c.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.56.0308101710110.10609@p500>
>From what I could see, the Oops you posted appeared rather to be
occurring in swapd before propagating to nfs. It would help if you
could decode it through ksymoops first though (see
linux/REPORTING-BUGS).
It would also help if you could try this out on the latest 2.4.22-rc kernel.
Cheers,
Trond
prev parent reply other threads:[~2003-08-11 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 21:16 Kernel Panic (NFS, 2.4.2[0-1]) war
2003-08-11 8:45 ` Stephan von Krawczynski
2003-08-11 12:55 ` war
2003-08-11 15:07 ` Trond Myklebust [this message]
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=shsd6fcz10c.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=war@lucidpixels.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox