public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bruno Prémont" <bruno.premont@restena.lu>
To: Greg KH <gregkh@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Stefan Winter <stefan.winter@restena.lu>
Subject: Re: [2.6.27.4-5 stable regressions] Kernel boot early crash with low-64k reservation patches
Date: Tue, 9 Dec 2008 16:50:25 +0100	[thread overview]
Message-ID: <20081209165025.679fd673@pluto.restena.lu> (raw)
In-Reply-To: <20081209153654.GC25679@suse.de>

On Tue, 9 Dec 2008 07:36:54 -0800 Greg KH wrote:
> On Tue, Dec 09, 2008 at 08:34:40AM +0100, Bruno Prémont wrote:
> > Hi,
> > 
> > On a VMWare (ESX 3.5.0 Update 3) guest we get boot failure at the
> > very beginning of boot process. (Boot successful with 2.6.27.4,
> > failing with 2.6.27.x where x > 4 or just adding the 5 patches
> > below to 2.6.27.4)
> > 
> > State of config option
> >   CONFIG_X86_RESERVE_LOW_64K=y
> > or
> >   # CONFIG_X86_RESERVE_LOW_64K not set
> > does not make any difference.
> 
> Does the 2.6.27.8 kernel work better for you, or does it also fail?
> 
> Also, have you tried the 2.6.28-rc releases to see if the problem is
> also there?
> 
> thanks,
> 
> greg k-h

Any stable release after 2.6.27.4 is bad (that is 2.6.27.5,
2.6.27.6, 2.6.27.8 -- 2.6.27.7 has not been tested), they all produce
the same (not verified exact register/stack values) result.

We have not tried any 2.6.28-rc kernels yet.

Bruno

  reply	other threads:[~2008-12-09 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09  7:34 [2.6.27.4-5 stable regressions] Kernel boot early crash with low-64k reservation patches Bruno Prémont
2008-12-09 15:36 ` Greg KH
2008-12-09 15:50   ` Bruno Prémont [this message]
2008-12-09 16:46 ` Daniel Drake

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=20081209165025.679fd673@pluto.restena.lu \
    --to=bruno.premont@restena.lu \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=stefan.winter@restena.lu \
    /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