linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gcc k6 testing account <caligula@cam029208.student.utwente.nl>
To: linux-kernel@vger.kernel.org
Subject: 2.5.32 bootfailure for nfsroot
Date: Wed, 28 Aug 2002 17:57:32 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0208281746170.21556-100000@cam029208.student.utwente.nl> (raw)


Ave people

The subject says it all. 
2.5.32 doesn't boot when using nfsroot.
same systems running fine with 2.4.19/2.5.31


SYSTEMS:
   athlon with/without preempt. (flatbak)
   i586 with preempt.           (cam029205)

The relevant configs/dmesg/lspci are on 
cam029208.student.utwente.nl/~caligula. 


SYMPTOMS:
I'm using loadlin to load the kernels. I see the kernel loading,unzipping 
and then...black screen followed by reboot.


Greetz Mu






             reply	other threads:[~2002-08-28 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28 15:57 Gcc k6 testing account [this message]
2002-09-02  8:44 ` 2.5.32 bootfailure for nfsroot Gcc k6 testing account
2002-09-27 17:33   ` Denis Vlasenko
2002-09-27 15:43     ` Gcc k6 testing account
2002-10-02  0:22       ` 2.5.40 : loadlin failure + analysys WAS : " caligula

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=Pine.LNX.4.44.0208281746170.21556-100000@cam029208.student.utwente.nl \
    --to=caligula@cam029208.student.utwente.nl \
    --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;
as well as URLs for NNTP newsgroup(s).