linux-kernel - Re: PROBLEM: cannot get stable system since 2.6.28 kernel (amd64)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <49A0C693.6000407@zytor.com>
Date:	Sat, 21 Feb 2009 19:29:23 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Philippe Grenard <philippe.grenard@...oste.net>
CC:	Ingo Molnar <mingo@...e.hu>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, John Stoffel <john@...ffel.org>
Subject: Re: PROBLEM: cannot get stable system since 2.6.28 kernel (amd64)

Philippe Grenard wrote:
> On Friday 20 February 2009 22:58:30 Ingo Molnar wrote:
>> * Philippe Grenard <philippe.grenard@...oste.net> wrote:
>>> dc1e35c6e95e8923cf1d3510438b63c600fee1e2 is first bad commit
>>> commit dc1e35c6e95e8923cf1d3510438b63c600fee1e2
>>> Author: Suresh Siddha <suresh.b.siddha@...el.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 ?

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.

--
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/