Latest working kernel version: 2.6.25-rc2
Earliest failing kernel version:2.6.25-rc3
Steps to reproduce:
Created attachment 14986 [details]
Submitter : "Michael S. Tsirkin" <email@example.com>
Date : 2008-02-25 20:19
References : http://lkml.org/lkml/2008/2/25/282
Handled-By : Alexey Starikovskiy <firstname.lastname@example.org>
This entry is being used for tracking a regression from 2.6.24. Please don't
close it until the problem is fixed in the mainline.
Created attachment 14991 [details]
Please check if this patch helps
Created attachment 15060 [details]
Don't call _REG at early init
Please test this patch
The patch in comment #3 fixes my T61.
The patch in comment #4 does not have any effect on my T61.
Created attachment 15075 [details]
acpidump for T61 BIOS version 2.10
Created attachment 15076 [details]
confirmed that reverting patch noted in synopsys is patch fixed the T61
Created attachment 15141 [details]
Revert offending patch
Len, I would like to just revert offending patch.
We need to solve the original (non-fatal)
problem in some different way.
reverted from acpi test tree.
Len, can we please get this pushed upstream? It'd be a stupid regression to have in 2.6.25.
Reverting the commit in question doesn't bring back my volume keys on the x60 btw, they are still not working (where as in 2.6.24 and earlier they did).
I'm reopening this bug, it should not get closed until the patch is in Linus tree. Closing because it's in some private tree is a bad idea.
I can't reopen. So please reopen it.
This bug isn't "closed", it is "resolved", which is a state
that means a patch is available for review and testing.
It gets "closed" only when the patch is upstream.
If the volume keys on your x60 stopped working,
and continue to not work with the latest upstream
kernel, i urge you to file a (new) bug.
Thanks Len, just as long as the patch gets upstream I'm happy. Not sure why it has to take weeks for a simple revert to get in though, some faster turn-around for simple issues like this would be nice.
The volume keys work, but they don't generate events that are noticed. I'm told that is on purpose, though it sounds like a dumb way to break a working setup.
Fixed by: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4af8e10a6c57e7292862bd1703712f0565c7e429