Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: "TWEDE,ROGER (HP-Boise,ex1)" <roger_twede@hp.com>
Cc: 'Ralf Baechle' <ralf@linux-mips.org>,
	"'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: NFS Root broken in 2.4.18?  Anyone successfully booted?
Date: Thu, 31 Oct 2002 11:44:49 -0800	[thread overview]
Message-ID: <20021031114449.A20815@lucon.org> (raw)
In-Reply-To: <CBD6266EA291D5118144009027AA63350A68F183@xboi05.boi.hp.com>; from roger_twede@hp.com on Thu, Oct 31, 2002 at 01:28:05PM -0500

On Thu, Oct 31, 2002 at 01:28:05PM -0500, TWEDE,ROGER (HP-Boise,ex1) wrote:
> Ralf et al,
> 
> I found that the 2.4.18 system boots fine when booting from standard devices
> (IDE disks etc.).
> 
> Init fails to execute successfully when booting from NFS.  The NFS booting
> success appears to have died with 2.4.18.
> 
> The NFS boot completes fine in 2.4.17 but in 2.4.18 the NFS root is mounted
> and /sbin/init and the ld.so.1 are at least accessed, but the system never
> executes far enough in user space to even print a message to the console.
> 
> I've tried two different network card types just to be sure it wasn't a
> single driver issue.
> 
> Has anyone noticed this or does anyone know what changes may have caused
> this in 2.4.18? 
> I'm curious whether anyone has successfully booted 2.4.18 over NFS.
> 

Works fine with 2.4.20-pre6 in CVS.


H.J.

  reply	other threads:[~2002-10-31 19:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 18:28 NFS Root broken in 2.4.18? Anyone successfully booted? TWEDE,ROGER (HP-Boise,ex1)
2002-10-31 19:44 ` H. J. Lu [this message]
2002-10-31 20:49 ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31 19:57 Saugata.Chatterjee

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=20021031114449.A20815@lucon.org \
    --to=hjl@lucon.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=roger_twede@hp.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