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]

Date:	Fri, 20 Feb 2009 22:58:30 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Philippe Grenard <philippe.grenard@...oste.net>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Cc:	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 <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
--
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/