[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090119201115.GD31356@linux-os.sc.intel.com>
Date: Mon, 19 Jan 2009 12:11:16 -0800
From: Suresh Siddha <suresh.b.siddha@...el.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Avuton Olrich <avuton@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: Fail to early boot with v2.6.27-rc2 to at least v2.6.29-rc2 due to dc1e35c
On Mon, Jan 19, 2009 at 12:07:34PM -0800, H. Peter Anvin wrote:
> Avuton Olrich wrote:
> > 2009/1/19 H. Peter Anvin <hpa@...or.com>:
> >>> bisected to:
> >>> commit dc1e35c6e95e8923cf1d3510438b63c600fee1e2
> >>> Author: Suresh Siddha <suresh.b.siddha@...el.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists