From: Len Brown <lenb@kernel.org>
To: "Arkadiusz Miśkiewicz" <a.miskiewicz@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: intel_idle causing 3.0.8 system reboot
Date: Tue, 17 Jan 2012 05:34:19 -0500 [thread overview]
Message-ID: <4F154EAB.8080008@kernel.org> (raw)
In-Reply-To: <201111130854.56201.a.miskiewicz@gmail.com>
On 11/13/2011 02:54 AM, Arkadiusz Miśkiewicz wrote:
> On Sunday 13 of November 2011, Len Brown wrote:
>>> intel_idle.max_cstate=2 also makes the problem go away.
>>
>> Is the system running with BIOS SETUP defaults?
>
> Tried also with "safe defaults (F8)" but that didn't help.
>
>> Are there any BIOS SETUP options related to CPU idle states?
>
> Yes, there are
>
> "C state package limit setting" with values possible: Auto, C1, C3, C6, C7
> (set to "Auto" here)
> "Intel EIST technology" -> Enabled
> "C1E support" -> Enabled
> "Intel C-STATE tech" -> Enabled
> "C1 Auto Demotion" -> Enabled
> "C3 Auto Demotion" -> Enabled
>
>> please boot with intel_idle.max_cstate=0
>> and send the output of these two commands:
>>
>> dmesg |grep idle
>> grep . /sys/devices/system/cpu/cpu0/cpuidle/*/*
>
> [root@berta ~]# dmesg |grep idle
> [ 0.000000] Command line: auto BOOT_IMAGE=pld3.0.8test ro root=812
> console=tty0 console=ttyS2,38400n81 panic=60 selinux=0 intel_idle.max_cstate=0
> [ 0.000000] Kernel command line: auto BOOT_IMAGE=pld3.0.8test ro root=812
> console=tty0 console=ttyS2,38400n81 panic=60 selinux=0 intel_idle.max_cstate=0
> [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
> [ 0.278494] using mwait in idle threads.
> [ 4.330321] intel_idle: disabled
> [ 5.794456] cpuidle: using governor ladder
> [ 5.806755] cpuidle: using governor menu
> [root@berta ~]# LC_ALL=C grep . /sys/devices/system/cpu/cpu0/cpuidle/*/*
> grep: /sys/devices/system/cpu/cpu0/cpuidle/*/*: No such file or directory
>
> There are only:
> [root@berta ~]# LC_ALL=C grep . /sys/devices/system/cpu/cpuidle/*
> /sys/devices/system/cpu/cpuidle/current_driver:none
> /sys/devices/system/cpu/cpuidle/current_governor_ro:menu
very strange.
now that it is back up...
Please file a bug report at bugzilla.kernel.org against idle/intel_idle
and assign it to me.
Please attach the complete output from dmesg -s 64000
and attach your .config
It appears that you have no acpi_idle driver installed.
If your kernel is missing
CONFIG_ACPI_PROCESSOR=y
please add it and collect the info above.
thanks,
-Len
>>
>> thanks,
>> Len Brown, Intel Open Source Technology Center
>>
>>>> # cat /proc/cpuinfo
>>>> processor : 0
>>>> vendor_id : GenuineIntel
>>>> cpu family : 6
>>>> model : 30
>>>> model name : Intel(R) Xeon(R) CPU X3430 @ 2.40GHz
>>>> stepping : 5
>
>
prev parent reply other threads:[~2012-01-17 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 21:27 if nolapic not used then system reboots after loading first module (possibly first irq using module) Arkadiusz Miśkiewicz
2011-10-28 17:15 ` intel_idle causing 3.0.8 system reboot (was: if nolapic not used then system reboots after loading first module (possibly first irq using module)) Arkadiusz Miśkiewicz
2011-10-28 17:54 ` Arkadiusz Miśkiewicz
2011-11-13 6:33 ` Len Brown
2011-11-13 7:54 ` Arkadiusz Miśkiewicz
2012-01-17 10:34 ` Len Brown [this message]
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=4F154EAB.8080008@kernel.org \
--to=lenb@kernel.org \
--cc=a.miskiewicz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=suresh.b.siddha@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;
as well as URLs for NNTP newsgroup(s).