public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carsten Emde <C.Emde@osadl.org>
To: Len Brown <lenb@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Asit Mallick <asit.k.mallick@intel.com>, Greg KH <gregkh@suse.de>,
	Mike Galbraith <efault@gmx.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Intel i7/X 980 freezes with CONFIG_INTEL_IDLE and frequency scaling
Date: Sat, 02 Apr 2011 09:33:27 +0200	[thread overview]
Message-ID: <4D96D147.60607@osadl.org> (raw)
In-Reply-To: <20110321204104.GA2702@kroah.com>

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);

  parent reply	other threads:[~2011-04-02  7:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 20:41 Linux 2.6.33.8 Greg KH
2011-03-21 20:41 ` Greg KH
2011-03-31 18:22 ` Carsten Emde
2011-04-01  4:35   ` Mike Galbraith
2011-04-02  9:14     ` Carsten Emde
2011-04-02 10:24       ` Alexander Holler
2011-04-02 11:27         ` Carsten Emde
2011-04-04  9:20           ` Alexander Holler
2011-04-02 21:08       ` Carsten Emde
2011-04-02 22:23       ` Thomas Gleixner
2011-04-02  7:33 ` Carsten Emde [this message]
2011-04-04 14:19   ` Intel i7/X 980 freezes with CONFIG_INTEL_IDLE and frequency scaling Carsten Emde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D96D147.60607@osadl.org \
    --to=c.emde@osadl.org \
    --cc=arjan@linux.intel.com \
    --cc=asit.k.mallick@intel.com \
    --cc=efault@gmx.de \
    --cc=gregkh@suse.de \
    --cc=hpa@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox