From: Emmett Pate <emmett@epate.com>
To: linux-kernel@vger.kernel.org
Subject: Re: rootfs on nfs : oops 2.5.63
Date: Tue, 25 Feb 2003 16:22:55 -0500 [thread overview]
Message-ID: <200302251622.55217.emmett@epate.com> (raw)
In-Reply-To: <20030225151337.358a6ee6.bert@ovh.net>
I'm having the same problem.
On my notebook (wireless PCMCIA, D-Link DWL650), 2.5.63 oopses immediately on
trying to mount an NFS filesystem. On my desktop it works fine. I can't
find any kernel configuration differences that look obvious. I'll be glad to
forward any relevant parts of the .config if it will be helpful.
I've read elsewhere that there's a simple patch that fixes this, but I haven't
been able to find it anywhere.
Emmett Pate
On Tuesday 25 February 2003 09:13 am, Bertrand wrote:
> Hello,
>
> I got a diskless station and i wanted to test the 2.5.* series.
>
> I got an Oops when the kernel tries to mount the rootfs on nfs.
>
> The kernel is build without modules, without ide, without scsi, with nfs
> and root on nfs option, devfs.
>
> The oops is shown bellow.
>
> Thank for advice.
>
> Bert.
next prev parent reply other threads:[~2003-02-25 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 14:13 rootfs on nfs : oops 2.5.63 Bertrand
2003-02-25 21:22 ` Emmett Pate [this message]
2003-02-25 22:11 ` Andrew Morton
2003-02-25 22:46 ` Emmett Pate
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=200302251622.55217.emmett@epate.com \
--to=emmett@epate.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox