linux-kernel - Re: intel_idle causing 3.0.8 system reboot

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] [day] [month] [year] [list]

Date:	Tue, 17 Jan 2012 05:34:19 -0500
From:	Len Brown <lenb@...nel.org>
To:	Arkadiusz Miśkiewicz <a.miskiewicz@...il.com>
CC:	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
	Suresh Siddha <suresh.b.siddha@...el.com>
Subject: Re: intel_idle causing 3.0.8 system reboot

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@...ta ~]# 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@...ta ~]# 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@...ta ~]# 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
> 
> 


--
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/