From: Doug Alcorn <lathi@seapine.com>
To: linux-kernel@vger.kernel.org
Subject: Intel Speedstep bug in 2.4.17?
Date: 05 Feb 2002 22:19:33 -0500 [thread overview]
Message-ID: <87eljzb8l6.fsf@localhost.localdomain> (raw)
I have an IBM Thinkpad A22m with an Intel Pentium III (Coppermine)
800Mhz. I custom compiled a 2.4.17 kernel. I'm also using Sawfish
1.0.1-6. I have a problem with the mouse input in my XFree86 4.1.0.
Sometimes it doesn't register mouse clicks (requiring me to click
three or four times). Also, the focus follows mouse seems off.
Most times I have to move the mouse in and out of a window several
times before the focus actually switches. I originally thought this
was a bug in sawfish, so I asked there. They said it was actually a
kernel issue. I'm not sure I really understand that; however, when I
boot the machine with the AC plugged in I never see these symptoms.
If I boot the machine on battery power the symptoms show up right
away. Also, if I boot on AC but later suspend and then resume on
battery power I don't see any of the symptoms. Can anyone shed any
light on this? Is it a known issue? Is it fixable?
Here are my APM configuration variables for my kernel:
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
CONFIG_APM_CPU_IDLE=y
CONFIG_APM_DISPLAY_BLANK=y
CONFIG_APM_RTC_IS_GMT=y
CONFIG_APM_ALLOW_INTS=y
# CONFIG_APM_REAL_MODE_POWER_OFF is not set
# CONFIG_ACPI is not set
--
(__) Doug Alcorn (mailto:doug@lathi.net http://www.lathi.net)
oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543
|_/ If you're a capitalist and you have the best goods and they're
free, you don't have to proselytize, you just have to wait.
next reply other threads:[~2002-02-06 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 3:19 Doug Alcorn [this message]
2002-02-06 14:20 ` Intel Speedstep bug in 2.4.17? Shaya Potter
2002-02-06 16:26 ` Bill Davidsen
2002-02-07 18:24 ` Shaya Potter
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=87eljzb8l6.fsf@localhost.localdomain \
--to=lathi@seapine.com \
--cc=linux-kernel@vger.kernel.org \
/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