public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Avuton Olrich <avuton@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: Fail to early boot with v2.6.27-rc2 to at least v2.6.29-rc2 due to dc1e35c
Date: Mon, 19 Jan 2009 12:11:16 -0800	[thread overview]
Message-ID: <20090119201115.GD31356@linux-os.sc.intel.com> (raw)
In-Reply-To: <4974DD86.2090300@zytor.com>

On Mon, Jan 19, 2009 at 12:07:34PM -0800, H. Peter Anvin wrote:
> Avuton Olrich wrote:
> > 2009/1/19 H. Peter Anvin <hpa@zytor.com>:
> >>> bisected to:
> >>> commit dc1e35c6e95e8923cf1d3510438b63c600fee1e2
> >>> Author: Suresh Siddha <suresh.b.siddha@intel.com>
> >>> Date:   Tue Jul 29 10:29:19 2008 -0700
> >>>
> >> Avuton, could you please compile the attached program and send us the
> >> output?
> > 
> > Sure whichever flavor you prefer:
> > http://avuton.googlepages.com/cpuid-out (3M)
> > http://avuton.googlepages.com/cpuid-out.bz2 (40K)
> 
> OK, that's an XSAVE-capable CPU, and yet the XSAVE code causes a crash. 
>   Not good...

Avuton, Does your bios has an option which says limit the cpuid
vector limit to '2' or something. Can you disable that option and
re-check? It will typically be located under cpu configuration settings.

My system which has same stepping etc works just fine. But my bios doesn't
have the cpuid limit option. I need to check if this issue is because
of the cpuid limit option that is enabled in the bios.

thanks,
suresh

  reply	other threads:[~2009-01-19 20:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19 14:04 Fail to early boot with v2.6.27-rc2 to at least v2.6.29-rc2 due to dc1e35c Avuton Olrich
2009-01-19 14:28 ` Avuton Olrich
2009-01-19 18:55 ` H. Peter Anvin
2009-01-19 19:31   ` Avuton Olrich
2009-01-19 20:07     ` H. Peter Anvin
2009-01-19 20:11       ` Suresh Siddha [this message]
2009-01-19 21:46         ` Avuton Olrich
2009-01-19 21:57           ` Suresh Siddha
2009-01-19 22:07             ` H. Peter Anvin
2009-01-19 22:14               ` Suresh Siddha
2009-01-19 22:24                 ` H. Peter Anvin
2009-01-21  5:20               ` Andi Kleen
2009-01-22 22:22                 ` Suresh Siddha
2009-01-22 22:40                   ` H. Peter Anvin
2009-01-22 22:56                     ` Suresh Siddha
2009-01-20  3:35             ` Valdis.Kletnieks
2009-01-20  6:36               ` H. Peter Anvin
2009-01-22  0:38 ` H. Peter Anvin
2009-01-22  2:26   ` Avuton Olrich
2009-01-22  8:28     ` Ingo Molnar

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=20090119201115.GD31356@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=avuton@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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