mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Witek Krecicki <adasi@kernel.pl>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is initrd working?
Date: Sun, 13 Oct 2002 14:19:45 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44L.0210131418440.8712-100000@ep09.kernel.pl> (raw)
In-Reply-To: <20021013043121.A1300@adam.yggdrasil.com>

On Sun, 13 Oct 2002, Adam J. Richter wrote:

> Date: Sun, 13 Oct 2002 04:31:21 -0700
> From: Adam J. Richter <adam@yggdrasil.com>
> To: adasi@kernel.pl
> Cc: linux-kernel@vger.kernel.org
> 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


  reply	other threads:[~2002-10-13 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-13 11:31 Adam J. Richter
2002-10-13 12:19 ` Witek Krecicki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-13  9:45 Witek Krecicki

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.44L.0210131418440.8712-100000@ep09.kernel.pl \
    --to=adasi@kernel.pl \
    --cc=adam@yggdrasil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®