linux-kernel - Intel i7/X 980 freezes with CONFIG_INTEL

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: <4D96D147.60607@osadl.org>
Date:	Sat, 02 Apr 2011 09:33:27 +0200
From:	Carsten Emde <C.Emde@...dl.org>
To:	Len Brown <lenb@...nel.org>
CC:	linux-kernel@...r.kernel.org,
	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Asit Mallick <asit.k.mallick@...el.com>,
	Greg KH <gregkh@...e.de>, Mike Galbraith <efault@....de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Intel i7/X 980 freezes with CONFIG_INTEL_IDLE and frequency scaling

Len,

after upgrading a Fedora 14 based Intel i7/X 980 box to 2.6.39-rc1, the 
system freezes when frequency scaling is started. Looks like a complete 
CPU halt, since neither SysRq nor anything else can convince the box to 
provide any information.

Loading acpi_cpufreq is save, but selecting the performance 
scaling_governor immediately freezes the system. Selecting the ondemand 
scaling_governor freezes the system when load is generated for the first 
time, presumably when the frequency is increased. Fortunately, when the 
kernel was built with another config file, the system did not freeze. 
After enabling and disabling some suspicious config items (before going 
through the hassle and bisect the config using ktest.pl), the culprit 
was found to be CONFIG_INTEL_IDLE. Fedora 14 enables it.

CPU info:
vendor_id	: GenuineIntel
cpu family	: 6
model		: 44
model name	: Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz
stepping	: 2

Excluding this CPU model from being initialized helps but is, of course, 
no solution. Do you have a real solution?

Thanks,
	Carsten.

--
Index: linux-2.6.39-rc1/drivers/idle/intel_idle.c
===================================================================
--- linux-2.6.39-rc1.orig/drivers/idle/intel_idle.c
+++ linux-2.6.39-rc1/drivers/idle/intel_idle.c
@@ -338,7 +338,9 @@ static int intel_idle_probe(void)
  	case 0x2E:	/* Nehalem-EX Xeon */
  	case 0x2F:	/* Westmere-EX Xeon */
  	case 0x25:	/* Westmere */
+#ifdef WESTMERE_MAY_FREEZE
  	case 0x2C:	/* Westmere */
+#endif
  		cpuidle_state_table = nehalem_cstates;
  		auto_demotion_disable_flags =
  			(NHM_C1_AUTO_DEMOTE | NHM_C3_AUTO_DEMOTE);
--
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/