From: Andi Kleen <andi@firstfloor.org>
To: Zbigniew Baniewski <zb@ispid.com.pl>
Cc: linux-acpi@vger.kernel.org
Subject: Re: ACPI-related bug caused poor responsitivity (2.6.26.x line)
Date: Fri, 15 Aug 2008 04:20:11 +0200 [thread overview]
Message-ID: <8763q3yq78.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080814211348.GA6268@sarge.my.own.domain.no-net> (Zbigniew Baniewski's message of "Thu, 14 Aug 2008 23:13:49 +0200")
Zbigniew Baniewski <zb@ispid.com.pl> writes:
> There are so many issues reported during last 3 months, that I'm not sure,
> whether (or not) someone wrote about the problem. But few words anyway:
>
> I noticed, that using new kernels (tested 2.6.26 and 2.6.26.2), there are
> typical for ACPI-related problems troubles with responsitivity. For example:
> if I'm opening "bloated" web page using Opera, one can't move the mouse
> cursor smoothly around the screen; there is a "jitter" during the movement,
> and any output (like GKrellm's diagrams created in real time) for that 2-3
> seconds is "frozen". As I've found googling around, these are rather typical
> ACPI-related problems, and indeed: forcing "acpi=off" was the cure.
I assume you double checked that? As in you removed the option again
and the problem reappeared? And you add it again and it disappeared
again? If not do so please.
If it's checked please put a full report into http://bugzilla.kernel.org
Might be some kind of power saving issue. Does it happen when
you boot with processor.max_cstate=1? (without acpi=off) Does it happen when you
disable CPUIDLE in the config?
Thanks
-Andi
next prev parent reply other threads:[~2008-08-15 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 21:13 ACPI-related bug caused poor responsitivity (2.6.26.x line) Zbigniew Baniewski
2008-08-15 2:20 ` Andi Kleen [this message]
2008-08-15 11:03 ` Zbigniew Baniewski
2008-08-15 2:35 ` Zhang Rui
2008-08-15 11:08 ` Zbigniew Baniewski
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=8763q3yq78.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-acpi@vger.kernel.org \
--cc=zb@ispid.com.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