From: Edouard Gomez <ed.gomez@wanadoo.fr>
To: lkml <linux-kernel@vger.kernel.org>
Subject: [BUG] Ramdisk is broken with 2.4.19-pre6/8
Date: Wed, 15 May 2002 18:43:43 +0200 [thread overview]
Message-ID: <20020515164343.GA412@wanadoo.fr> (raw)
Hello,
I've build a 2 disk set following the http://www.tldp.org/HOWTO/Bootdisk-HOWTO/
instructions. This works well with < 2.4.19-pre6 kernels but 2.4.19-pre6 just
doesn't read the 2nd floppy disk (the ramdisk).
I noticed that 2.4.19-pre6 try to read from floppy before prompting for the
ramdisk and <2.4.19-pre6 never did that.
Once i press enter with the 2.4.19-pre6, the kernel seems to do nothing. No
kernel panic, no oops. It just does nothing. The floppy leds is switched on
3s or 5s and then is switched off.
Alt+SysRq+T gives me 5 usual tasks in Sleeping mode :
[ksoftirqd_CPU0]
[kswapd]
[kupdated]
[keventd]
[bdflush]
and one active task called swapper (never heard about that one).
This last task is still in R state.
This bug is still present in 2.4.19-pre8 (tested, same behaviour).
Regards
PS : Can you cc me the answers as i not a lkml subscriber. Thx
--
Edouard Gomez
reply other threads:[~2002-05-15 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020515164343.GA412@wanadoo.fr \
--to=ed.gomez@wanadoo.fr \
--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