From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: processors core stuck in full throttle after waking up from s2ram
Date: Sat, 22 Nov 2008 23:33:06 +0100 [thread overview]
Message-ID: <200811222333.06459.rjw@sisk.pl> (raw)
In-Reply-To: <1227389306.3171.14.camel@LiNuX>
On Saturday, 22 of November 2008, Justin P. Mattock wrote:
> 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.
>
> 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.
Ah, ok. So the problem is that core remains at the highest frequency.
What cpufreq driver is used on this box?
Rafael
next prev parent reply other threads:[~2008-11-22 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 8:11 processors core stuck in full throttle after waking up from s2ram Justin P. Mattock
2008-11-22 20:51 ` Rafael J. Wysocki
2008-11-22 21:28 ` Justin P. Mattock
2008-11-22 22:33 ` Rafael J. Wysocki [this message]
2008-11-23 3:31 ` Justin P. Mattock
2008-11-23 3:59 ` Justin P. Mattock
2008-11-23 17:24 ` Pavel Machek
2008-11-23 19:57 ` Justin P. Mattock
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=200811222333.06459.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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