* initrd broken???
@ 2000-10-30 8:24 Jeff Chua
0 siblings, 0 replies; only message in thread
From: Jeff Chua @ 2000-10-30 8:24 UTC (permalink / raw)
To: linux-kernel
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/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2000-10-30 8:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-10-30 8:24 initrd broken??? Jeff Chua
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.