From: Pavel Machek <pavel@suse.cz>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: processors core stuck in full throttle after waking up from s2ram
Date: Sun, 23 Nov 2008 18:24:26 +0100 [thread overview]
Message-ID: <20081123172426.GA7447@ucw.cz> (raw)
In-Reply-To: <1227389306.3171.14.camel@LiNuX>
Hi!
> > > 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>
> 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.
Can you check with top that no process is running/eating time?
If you change cpufreq governor to powersave, will it react?
Can you check with powertop if the cpu is idle (C2/C3)or if it is
running something?
Actually, booting with nosmp might be useful. Is it always same core?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-11-23 17:26 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
2008-11-23 3:31 ` Justin P. Mattock
2008-11-23 3:59 ` Justin P. Mattock
2008-11-23 17:24 ` Pavel Machek [this message]
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=20081123172426.GA7447@ucw.cz \
--to=pavel@suse.cz \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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