All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Plzik <milan.plzik@gmail.com>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Timer unstability on when using C2 and deeper sleep states (Dell Latitude XT)
Date: Wed, 13 Aug 2008 16:33:14 +0200	[thread overview]
Message-ID: <1218637994.5250.22.camel@localhost> (raw)
In-Reply-To: <20080813130558.GE6995@ucw.cz>

On St, 2008-08-13 at 15:05 +0200, Pavel Machek wrote:
> Hi!

  Hello,

  I apologize, I have not seen your reply, the newest update already
describes my situation.

> 
> >   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. Otherwise, the system just stalls and does
> > nothing. I have no idea why does this happen (especially when I know
> 
> I have seen it before with NOHZ problems. Try nohz=off, highres=off ?
> 

  I tried nohz=off; result was stably working system, but the cause
could be that it virtually did not enter any of deeper C states (I also
had HZ configured to 1000, but I'm not sure whether that matters when
calculating efficieny of switching to Cx state). I also tried to disable
hpet at all, and to disable support for high resolution timers in
kernel, but result was the same, IIRC. Unless I wasn't entering C2 or
C3, the system was stable.

	Milan


  reply	other threads:[~2008-08-13 14:33 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 [this message]
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   ` Timer unstability on when using C2 and deeper sleep states (Dell Latitude XT) Andi Kleen
2008-08-13 21:04     ` 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=1218637994.5250.22.camel@localhost \
    --to=milan.plzik@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.