hotkey-setup (0.1-17ubuntu19) gutsy; urgency=low
* Fix number of '.' in 'grep' mask string
* Set the top 8-bits of the mask and see if the they stick
* Add back in 'thinkpad-keys' lockfile logic
* 'thinkpad-keys': Move open(fifo) into loop to reduce
code duplication.
* Roll
The new acpi-support (0.101) and hotkey-setup (0.1-17ubuntu15) packages
stop thinkpad-keys from running so the 2% CPU usage dropped which is
good.
However, none of the hotkeys were working. After a quick investigation,
it seems that the thinkpad_acpi kernel module wasn't being loaded. A
simple
Confirmed on a T60p, 2% of CPU all time...
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I have a T60 and run Kubuntu. I used to see 2% CPU. I changed some
settings on my system and it went off mostly after I disabled arts in
the kcontrol center (Enable sound system - uncheck), though I'm not
entirely sure if it was arts.
However, if I compile a newer kernel and install it, it
Confirmed on a T43. thinkpad-keys hogs around 2-3% CPU time when running
without the patch. Patched is much better.
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received this bug notification because you are a member of Ubuntu
Bugs, which
I did not see that problem in feisty. I am not sure if thinkpad-keys was
running, but the volume keys worked. In gutsy it uses 2% cpu time on my
laptop and battery is drained a lot faster.
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You
Seeing this on a Thinkpad T30, too. top and powertop both show that
thinkpad-keys is using a lot of CPU.
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
By the way, I've only noticed this since upgrading to gutsy, but it may
have been there before since I didn't go looking for it.
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received this bug notification because you are a member of
Is this patch going to be applied to hotkey-setup anytime soon?
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
I just tested here, you're right:
echo 0x | sudo tee /proc/acpi/ibm/hotkey
acpi_listen
now we get the rest of the events:
0x1001 FN_F1
...
0x100c FN_F12
0x100d FN_BACKSPACE
0x100e FN_INSERT
0x100f FN_DELETE
0x1010 FN_HOME (brightness)
0x1011 FN_END (brightness) ---
Whoopie: That sounds great! Just what is needed. (But does it work on any
thinkpad model, older ones in particular?)
Also, I think thinkpad-keys will be with us for some time still, and as such
should be patched ASAP anyway to provide a general fix that it not dependent on
a recent kernel
Kristian: it also works with the thinkpad_acpi version in 2.6.22-rc,
although the output of /proc/acpi/ibm/hotkey doesn't show the whole
0xfff. But that's just a cosmetic issue.
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received
Confirmed here too on my X60s... and just to amplify on what Benjamin
Pineau mentioned, on my system, PowerTOP shows thinkpad-keys on my
system is responsible for ~20 wakeups/second (exactly what you would
expect with a 50 msec timer), which is currently about 10% of all the
wakeups on my system.
Hi,
the thinkpad_acpi kernel module generate an ACPI event when echo
0x /proc/acpi/ibm/hotkey. So, we don't need thinkpad-keys
anymore which polls nvram. we could have ACPI event scripts for this.
I'm attaching my proof-of-concept scripts.
Best regards,
Whoopie
--
thinkpad-keys on
** Attachment added: /etc/acpi/events/ibm-buttons
http://launchpadlibrarian.net/8198340/ibm-buttons
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
** Attachment added: /etc/acpi/ibm-buttons.sh
http://launchpadlibrarian.net/8198341/ibm-buttons.sh
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Patch works great here too. (X60s)
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Ben Collins : yes.
I'm running this on 2.6.22-rc5 on a Thinkpad X40, and:
1) This Thinkpad model is also affected, indeed.
2) The bug is still present on the original unpatched package (it's even more
visible because of dynticks, see above).
3) The Kristian Berge Nessa's patch works flawlesly,
Heck! At least now we know why the effect of a slow NVRAM is so
amplified. Why on earth does the '/dev'/nvram' need to check the
checksum *each* time.
I'm not sure we can avoid the lseek() overhead, though I guess if this
is the way the 'nvram' driver is working, it *would* actually be cheaper
I don't see anything showing this was actually tested on 2.6.22. Can
someone confirm this is the correct target?
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: linux-source-2.6.22 = linux-source-2.6.20
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
Update: After running the patched thinkpad-keys for 24 hours, CPU time
is a meagre 1 sec, just a tad better than the 25 minutes it used to
spend a day...
This just seemed to good to be true. So, to verify the correctness of
the patch, here's some background:
The tpb source (from which
I had the same behaviour on my T60p and X60t, thinkpad-keys using ~2% cpu at
all times:
$ uptime ; ps aux | awk '/[t]hinkpad-keys/{print$11,$10}'
12:37:57 up 6 days, 19:39, 1 user, load average: 0.17, 0.14, 0.11
/usr/sbin/thinkpad-keys 189:07
The attached patch bundles the 4 read+seek
Sorry, please disregard the above ^ patch, this is the correct one.
Applies to latest release (0.1-17ubuntu9).
cd hotkey-setup-0.1
patch hotkey-setup_0.1-17ubuntu9_optimize+CFLAGS.patch
** Attachment added: bundle nvram reads, POLL_DELAY 100ms, add DEBUG define,
default -O2
** Attachment removed: add DEBUG define, default -O2
http://librarian.launchpad.net/7398541/hotkey-
setup_0.1-17ubuntu9_CFLAGS.patch
--
thinkpad-keys on ThinkPad X60* uses a large amount of CPU
https://bugs.launchpad.net/bugs/45404
You received this bug notification because you are a member
getting the same behavior on an R40.
R40-2722 with pentium-m 1.7Ghz, using acpi.
I've taken to killing the thinkpad-keys process after startup. All the
buttons continue working with including osd for volume control, access-
ibm, brightness, thinklight, etc. (I'm using kde).
--
thinkpad-keys
26 matches
Mail list logo
