| 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
| ||
|
Message-ID: <4D7A1322.4050706@suse.cz> Date: Fri, 11 Mar 2011 13:18:42 +0100 From: Jiri Slaby <jslaby@...e.cz> To: Len Brown <lenb@...nel.org> CC: linux-pm <linux-pm@...ts.linux-foundation.org>, "x86@...nel.org" <x86@...nel.org>, Linux kernel mailing list <linux-kernel@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>, Jiri Slaby <jirislaby@...il.com> Subject: Why is max_cstate=1 still needed? Hello, there are still reports against the latest kernels, that people need to pass processor/intel_idle.max_cstate=1 to successfully boot the kernel. The symptoms are always the same, until the parameter is specified OR until the user presses a key, the system won't boot up. This started to appear between 2.6.31 and 2.6.34 (possibly a 2.6.33 regression) and continues to be reported against the latest stable 2.6.37.3. For example: https://bugzilla.kernel.org/show_bug.cgi?id=15289 https://bugzilla.novell.com/show_bug.cgi?id=579932 https://bugzilla.novell.com/show_bug.cgi?id=673589 https://bugzilla.novell.com/show_bug.cgi?id=675161 I see that there were some fixes in .38-rc in this bug report (they look unrelated): https://bugzilla.kernel.org/show_bug.cgi?id=29992 Should they give .38-rc a try? Any help would be appreciated. thanks, -- js suse labs -- 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