linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nilshar <nilshar@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Problem with 2.6.20 and highmem64
Date: Fri, 16 Feb 2007 09:38:46 +0100	[thread overview]
Message-ID: <639c60080702160038o516fd790n50923afcc136ea07@mail.gmail.com> (raw)
In-Reply-To: <639c60080702140711j1ec1b344p77133bb26f687e87@mail.gmail.com>

I can confirm that it works fine with 2.6.20-rc2.
Do you need me to try any other ? do you need any more info ?

2007/2/14, Nilshar <nilshar@gmail.com>:
> Hello,
> I have an issue with latest 2.6.20 kernel..
> my last kernel was a 2.6.18 and I wanted to upgrade to a 2.6.20, I
> copied .config and did a make menuconfig, then save/quit. I compiled
> new kernel, all went fine.
> I installed it and at boot time, I had a hang just after "Freeing
> unused kernel memory" where INIT is supposed to start.
> After searching the web, I found that it is usually the case when
> wrong process type is configured.. I verified that, but all was fine
> there.
> After 10ish compiled kernel, I found that it is when I select highmem64.
>
> Diff between working and non working kernel :
>
> 181,182c181,182
> < # CONFIG_HIGHMEM4G is not set
> < CONFIG_HIGHMEM64G=y
> ---
> > CONFIG_HIGHMEM4G=y
> > # CONFIG_HIGHMEM64G is not set
> 185d184
> < CONFIG_X86_PAE=y
> 191c190
> < CONFIG_RESOURCES_64BIT=y
> ---
> > # CONFIG_RESOURCES_64BIT is not set
>
> (I just witching highmem 4G and highmem64g).
>
> I'll attach the full .config.
>
> it used to work fine with highmem64g with a kernel 2.6.18 and 2.6.19
> (I'm sure it was ok with .20-rc2 but I'll double check that).
>
> Is this a bug ? or something I did wrong ?
>
> Oh, I probably should add that this hang doesn't occur on all
> hardware, but it happen on Dell PE 850 at least.
>
> If you need additional informations, just ask :)
>
>

  reply	other threads:[~2007-02-16  8:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 15:11 Problem with 2.6.20 and highmem64 Nilshar
2007-02-16  8:38 ` Nilshar [this message]
2007-02-16 15:42   ` Nilshar

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=639c60080702160038o516fd790n50923afcc136ea07@mail.gmail.com \
    --to=nilshar@gmail.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;
as well as URLs for NNTP newsgroup(s).