From: Andi Kleen <andi@firstfloor.org>
To: Milan Plzik <milan.plzik@gmail.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: Timer unstability on when using C2 and deeper sleep states (Dell Latitude XT)
Date: Wed, 13 Aug 2008 22:17:36 +0200 [thread overview]
Message-ID: <87proczn33.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1218625125.4304.7.camel@localhost> (Milan Plzik's message of "Wed, 13 Aug 2008 12:58:45 +0200")
Milan Plzik <milan.plzik@gmail.com> writes:
> I apologize for replying on my own mail (and also for top-posting, but
> this information is global update, not exactly fitting any of topics
> mentioned below).
>
> After playing for a longer while I found out that the system ends
> sometimes in state where, in order to do anything useful, I need to
> press keys on keyboard.
This usually means it is using the wrong timer in a deeper idle state.
Some idle states cannot be woken up by e.g. the APIC timer and then
you get that effect: you only make progress when you wake up the
CPU in some other way like pressing a key. Then on wake up the
timers get processed.
This is usually a bug in the kernel timer selection. It should be chosing
a timer that always wakes up from the deepest idle state used.
You should post the full boot log
-Andi
next prev parent reply other threads:[~2008-08-13 20:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 18:33 Timer unstability on when using C2 and deeper sleep states (Dell Latitude XT) Milan Plzik
2008-08-13 10:58 ` Milan Plzik
2008-08-13 13:05 ` Pavel Machek
2008-08-13 14:33 ` Milan Plzik
2008-08-13 14:16 ` Possible CPU_IDLE bug [WAS: Re: Timer unstability on when using C2 and deeper sleep states (Dell Latitude XT)] Milan Plzik
2008-08-13 18:14 ` Pallipadi, Venkatesh
2008-08-13 20:21 ` Milan Plzik
2008-08-13 21:22 ` Pallipadi, Venkatesh
2008-08-14 8:05 ` Milan Plzik
2008-08-14 9:00 ` Thomas Gleixner
2008-08-14 11:40 ` Milan Plzik
2008-08-14 13:28 ` Milan Plzik
2008-08-15 11:46 ` Milan Plzik
2008-08-13 20:17 ` Andi Kleen [this message]
2008-08-13 21:04 ` Timer unstability on when using C2 and deeper sleep states (Dell Latitude XT) Milan Plzik
[not found] <fa.BPxGhvxOK2Rcn4TTNlAMe2XzVYk@ifi.uio.no>
[not found] ` <fa.s5pgfnYl3W8cOu+PDLbvAcv4X9c@ifi.uio.no>
[not found] ` <fa.2qnH5HZa4bnjN4HRRidEAUj5jxk@ifi.uio.no>
[not found] ` <fa.b1y/njcuV4QYZ2xTsVkHQ55Ni7Y@ifi.uio.no>
2008-08-14 5:12 ` Robert Hancock
2008-08-14 8:10 ` Milan Plzik
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=87proczn33.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=milan.plzik@gmail.com \
--cc=tglx@linutronix.de \
/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