I was trying to run initrd on 2.5.41, 2.5.42, 2.5.42-mm{1,2}, 2.5.42-ac1
and it is not working in any case (oopsing just after RAMDISK: Compressed
image found...). I've sent decoded oops some time ago, without any
response. I cannot even try modular IDE because of that :/
Please help
--
* Witek Krecicki [email protected] [email protected] GG346981 +48502117580 *
* "None but ourselves can free our minds" - Bob Marley, Redemption Song *
* http://www.risingsun.org http://www.kernel.org http://www.pld.org.pl *
* http://risingsun.eu.org http://www.6bone.pl http://www.amnesty.org *
On 2002-10-13 at 9:45:38, Witek Krecicki wrote:
>I was trying to run initrd on 2.5.41, 2.5.42, 2.5.42-mm{1,2}, 2.5.42-ac1
>and it is not working in any case (oopsing just after RAMDISK: Compressed
>image found...). I've sent decoded oops some time ago, without any
>response. I cannot even try modular IDE because of that :/
>Please help
Make sure you are not running CONFIG_HIGHMEM64G. I believe there
is some kind of memory corruption problem under highmem=64g on x86 with
big ramdisks. I use a ~900kB initial ramdisk that expands to ~2.2MB.
With CONFIG_HIGHMEM4G or CONFIG_NOHIGHMEM, the problem disappears
for me. I am writing this email under 2.5.41 with CONFIG_HIGHMEM4G and
IDE as a module (with a patch that I posted to lkml).
--
Adam J. Richter __ ______________ 575 Oroville Road
[email protected] \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
On Sun, 13 Oct 2002, Adam J. Richter wrote:
> Date: Sun, 13 Oct 2002 04:31:21 -0700
> From: Adam J. Richter <[email protected]>
> To: [email protected]
> Cc: [email protected]
> Subject: Re: Is initrd working?
>
> On 2002-10-13 at 9:45:38, Witek Krecicki wrote:
> >I was trying to run initrd on 2.5.41, 2.5.42, 2.5.42-mm{1,2}, 2.5.42-ac1
> >and it is not working in any case (oopsing just after RAMDISK: Compressed
> >image found...). I've sent decoded oops some time ago, without any
> >response. I cannot even try modular IDE because of that :/
> >Please help
>
> Make sure you are not running CONFIG_HIGHMEM64G. I believe there
> is some kind of memory corruption problem under highmem=64g on x86 with
> big ramdisks. I use a ~900kB initial ramdisk that expands to ~2.2MB.
>
> With CONFIG_HIGHMEM4G or CONFIG_NOHIGHMEM, the problem disappears
> for me. I am writing this email under 2.5.41 with CONFIG_HIGHMEM4G and
> IDE as a module (with a patch that I posted to lkml).
I've checked this config option: CONFIG_HIGHMEM4G was enabled. I've
turned it to NOHIGHMEM, recompiled and it's still not working. ramdisk is
pretty small (just IDE)
WK