From: Milan Plzik <milan.plzik@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Venkatesh <venkatesh.pallipadi@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Possible CPU_IDLE bug [WAS: Re: Timer unstability on when using C2 and deeper sleep states (Dell Latitude XT)]
Date: Thu, 14 Aug 2008 13:40:14 +0200 [thread overview]
Message-ID: <1218714014.7111.7.camel@localhost> (raw)
In-Reply-To: <alpine.LFD.1.10.0808141100100.3243@apollo.tec.linutronix.de>
On Št, 2008-08-14 at 11:00 +0200, Thomas Gleixner wrote:
> On Thu, 14 Aug 2008, Milan Plzik wrote:
> > I tried it just now, is performs a bit better than 2.6.26 (e.g. I
> > don't get that "press any key unless nothing happens" states), even
> > reports a bit more reasonable values of wakeups, but the system
> > sometimes becomes rather slow (e.g. when playing video). I was not able
> > to compile fglrx driver, so I had to change it to radeon one. And also,
> > the number of wakeups reported is not very convincing, though, it
> > changes from 300 to 600 (which is ~ two times the sum of wakeups)
> > without any reason, and sometimes goes even higher.
> >
> > I tried to use nolapic_timer option, but it didn't help.
>
> Can you please try "hpet=disable" on the kernel command line ?
Looks like this has helped; after cold reboot hpet=disable seems to
help the system to run properly (on 2.6.26 kernel). I wonder what could
cause these problems. In the meanwhile I learned that this machine
doesn't do proper cleanup during reboot -- it seems that state before
reboot affects the state after reboot, so I should probably do some
re-testing with cold reboot after each attempt. I guess I tried
hpet=disable some time ago and after quick reboot it did not work
properly.
>
> Thanks,
> tglx
Thank you,
Milan
next prev parent reply other threads:[~2008-08-14 11:40 UTC|newest]
Thread overview: 15+ 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 [this message]
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
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=1218714014.7111.7.camel@localhost \
--to=milan.plzik@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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