linux-kernel - Re: processors core stuck in full throttle after waking up from s2ram

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]
Date:	Sat, 22 Nov 2008 13:28:26 -0800
From:	"Justin P. Mattock" <justinmattock@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: processors core stuck in full throttle after waking up from
 s2ram

On Sat, 2008-11-22 at 21:51 +0100, Rafael J. Wysocki wrote:
> On Thursday, 20 of November 2008, Justin P. Mattock wrote:
> > (before getting into this I need to see if somebody else with a macbook
> > pro(ATI with radeon drivers) is experiencing the same issue?)
> > I'm not sure I this is caused by the kernel or the program s2ram.
> > when I cat watch /proc/cpuinfo I see: (after waking up from suspend.)
> > 
> > Every 2.0s: cat /proc/cpuinfo
> > Wed Nov 19 23:49:13 2008
> > 
> > processor       : 0
> > vendor_id       : GenuineIntel
> > cpu family      : 6
> > model           : 15
> > model name      : Intel(R) Core(TM)2 CPU         T7400  @ 2.16GHz
> > stepping        : 6
> > cpu MHz         : 2167.000  
> > cache size      : 4096 KB
> > physical id     : 0
> > siblings        : 2
> > core id         : 0
> > cpu cores       : 2
> > apicid          : 0
> > initial apicid  : 0
> > fdiv_bug        : no
> > hlt_bug         : no
> > f00f_bug        : no
> > coma_bug        : no
> > fpu             : yes
> > fpu_exception   : yes
> > cpuid level     : 10
> > wp              : yes
> > flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
> > constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx
> >  est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow
> > bogomips        : 4322.49
> > clflush size    : 64
> > power management:
> > 
> > processor       : 1
> > vendor_id       : GenuineIntel
> > cpu family      : 6
> > model           : 15
> > model name      : Intel(R) Core(TM)2 CPU         T7400  @ 2.16GHz
> > stepping        : 6
> > cpu MHz         : 1000.000
> > cache size      : 4096 KB
> > physical id     : 0
> > siblings        : 2
> > core id         : 1
> > cpu cores       : 2
> > apicid          : 1
> > initial apicid  : 1
> > fdiv_bug        : no
> > hlt_bug         : no
> > f00f_bug        : no
> > coma_bug        : no
> > fpu             : yes
> > fpu_exception   : yes
> > cpuid level     : 10
> > wp              : yes
> > flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> > mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
> > constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx
> >  est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow
> > bogomips        : 4322.60
> > clflush size    : 64
> > power management:
> > 
> > 
> > the processor is full throttle on one of the cores.
> 
> Surely not.  The first core shows 2.16 GHz.
> 
> Anyway, it certainly is not related to the s2ram program in any way.
> 
> Thanks,
> Rafael


Normally I would see cpu MHz: 1000 under both entries,
this time upon wakeup theres 1000 and 2167.00. the 2167.00 doesn't move
down to 1000 i.g. example of system normally:
 cat /proc/cpuinfo <below>

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 CPU         T7400  @ 2.16GHz
stepping        : 6
cpu MHz         : 1000.000   
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc arch_perfmon                             pebs bts pni
dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm
tpr_shadow
bogomips        : 4322.48
clflush size    : 64
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 CPU         T7400  @ 2.16GHz
stepping        : 6
cpu MHz         : 1000.000
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 1
initial apicid  : 1
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc arch_perfmon                             pebs bts pni
dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm
tpr_shadow
bogomips        : 4322.51
clflush size    : 64
power management:

under normal use this 
will move between 2167.00 to 1000 simultaneously under load with both
cores, but then back down to 1000, for both when settled down.
in this situation as I reported, the 2167.00 just
stays at that number for one of the cores(if thats what I'm seeing) when
waking up from suspend for some reason or another. 

regards;


-- 
Justin P. Mattock <justinmattock@...il.com>

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