From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755754AbZBVDaE (ORCPT ); Sat, 21 Feb 2009 22:30:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752720AbZBVD3y (ORCPT ); Sat, 21 Feb 2009 22:29:54 -0500 Received: from terminus.zytor.com ([198.137.202.10]:58425 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752660AbZBVD3x (ORCPT ); Sat, 21 Feb 2009 22:29:53 -0500 Message-ID: <49A0C693.6000407@zytor.com> Date: Sat, 21 Feb 2009 19:29:23 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Philippe Grenard CC: Ingo Molnar , Suresh Siddha , Thomas Gleixner , linux-kernel@vger.kernel.org, John Stoffel Subject: Re: PROBLEM: cannot get stable system since 2.6.28 kernel (amd64) References: <200902131944.56634.philippe.grenard@laposte.net> <200902202108.55332.philippe.grenard@laposte.net> <20090220215830.GB30665@elte.hu> <200902211121.46292.philippe.grenard@laposte.net> In-Reply-To: <200902211121.46292.philippe.grenard@laposte.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Philippe Grenard wrote: > On Friday 20 February 2009 22:58:30 Ingo Molnar wrote: >> * Philippe Grenard wrote: >>> dc1e35c6e95e8923cf1d3510438b63c600fee1e2 is first bad commit >>> commit dc1e35c6e95e8923cf1d3510438b63c600fee1e2 >>> Author: Suresh Siddha >>> 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 ? OK, this is a completely different problem then. Any way you could do a "git bisect" to track down the exact place where this broke? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.