public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philippe Grenard <philippe.grenard@laposte.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, John Stoffel <john@stoffel.org>
Subject: Re: PROBLEM: cannot get stable system since 2.6.28 kernel (amd64)
Date: Sat, 21 Feb 2009 11:21:46 +0100	[thread overview]
Message-ID: <200902211121.46292.philippe.grenard@laposte.net> (raw)
In-Reply-To: <20090220215830.GB30665@elte.hu>

On Friday 20 February 2009 22:58:30 Ingo Molnar wrote:
> * Philippe Grenard <philippe.grenard@laposte.net> wrote:
> > dc1e35c6e95e8923cf1d3510438b63c600fee1e2 is first bad commit
> > commit dc1e35c6e95e8923cf1d3510438b63c600fee1e2
> > Author: Suresh Siddha <suresh.b.siddha@intel.com>
> > Date:   Tue Jul 29 10:29:19 2008 -0700
> >
> >     x86, xsave: enable xsave/xrstor on cpus with xsave support
>
> [...]
>
> > A bit of googling gave me this :
> > http://lkml.org/lkml/2009/1/19/161
> > which exactly corresponds to my problem with 2.6.28 !
> >
> > A "solution" proposed was to try to check the bios setting
> > "cpuid value limit" and disable it if enabled. This did help
> > me to boot 2.6.28 or previously failing kernel compiled during
> > git-bisect, but gave me the "random freeze" any way....
>
> Note that the workaround for that BIOS bug is already in the
> latest upstream kernel, i.e. in 2.6.29-rc5.
>
> Could you please try -rc5, whether it works out of box?
>
> If you still see freezes, could you try the "nofxsr" boot
> option? That will turn off the new FPU code both in the hw and
> in the kernel.
>
> 	Ingo

Hello Ingo, thanks for your reply,

I've tried to boot 2.6.29-rc5 with both "Max CPUID Value" Enabled and 
Disabled, and tried for both case the "nofxsr" option without better result...

As I said before, I use the default dsdt table : can this be a problem too ?

Philippe

  reply	other threads:[~2009-02-21 10:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 18:44 PROBLEM: cannot get stable system since 2.6.28 kernel Philippe Grenard
2009-02-13 18:56 ` Len Brown
2009-02-13 19:56   ` Philippe Grenard
2009-02-13 20:48     ` John Stoffel
2009-02-14  8:17       ` Philippe Grenard
2009-02-14  9:20         ` Jaswinder Singh Rajput
2009-02-14  9:24         ` Jaswinder Singh Rajput
2009-02-15 12:17           ` Philippe Grenard
2009-02-16  0:21             ` John Stoffel
2009-02-16 18:25               ` PROBLEM: cannot get stable system since 2.6.28 kernel (amd64) Philippe Grenard
2009-02-17  4:46                 ` John Stoffel
2009-02-17 16:51                   ` Philippe Grenard
2009-02-20 20:08                   ` Philippe Grenard
2009-02-20 21:58                     ` Ingo Molnar
2009-02-21 10:21                       ` Philippe Grenard [this message]
2009-02-21 23:17                         ` Suresh Siddha
2009-02-22  3:29                         ` H. Peter Anvin
2009-02-22  9:11                           ` Philippe Grenard
2009-02-24 20:00                           ` Philippe Grenard
2009-02-13 20:43   ` PROBLEM: cannot get stable system since 2.6.28 kernel Philippe Grenard

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=200902211121.46292.philippe.grenard@laposte.net \
    --to=philippe.grenard@laposte.net \
    --cc=hpa@zytor.com \
    --cc=john@stoffel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    /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