From: "Jeff Chua" <jchua@fedex.com>
To: <linux-kernel@vger.kernel.org>
Subject: initrd broken???
Date: Mon, 30 Oct 2000 16:24:26 +0800 [thread overview]
Message-ID: <00a901c0424a$d5b388e0$589ca19b@corp.fedex.com> (raw)
I'm posting this hoping that someone will fix this soon ...
On Sat, 28 Oct 2000, Jeff Chua wrote:
> freeram /dev/ram0
> File freeram.c: Line 41: ioctl /dev/ram0: Error 16: Device or resource
busy
this should not happen.
> I cannot free the old initrd root partition under 2.4.0-testx, but it
works
> fine on 2.2.17.
hmm, as initrd now is used by almost evry Linux distributor, there for
sure will be a fix sooner or later if it is broken ;-)
... just wait a bit or complain on linux-kernel@vger.kernel.org
Hans
<lermen@fgan.de>
original message ...
Any chance to fix the following bug in 2.4.x
dmesg (from bootup message) ...
change_root: old root has d_count=3
freeram /dev/ram0
File freeram.c: Line 41: ioctl /dev/ram0: Error 16: Device or resource busy
I cannot free the old initrd root partition under 2.4.0-testx, but it works
fine on 2.2.17. I used loadlin to boot up
ramdisk initrd first, load the ide driver, and boot up the real linux.
I hope you guys are still the one maintaining initrd, if not, please point
me to someone who can help,
or send me a few lines as to how I can fix this.
Thanks,
Jeff
[ jchua@fedex.com ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-10-30 8:22 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='00a901c0424a$d5b388e0$589ca19b@corp.fedex.com' \
--to=jchua@fedex.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.