Subject : my KDE-4.4.2 BAttery Monitor APplet dislike the ACPI changes in 2.6.34-rc3 betweeen f5284e7..cf90bfe Submitter : Toralf Förster <toralf.foerster@gmx.de> Date : 2010-04-08 16:12 Message-ID : 201004081812.10656.toralf.foerster@gmx.de References : http://marc.info/?l=linux-kernel&m=127074316624855&w=2 This entry is being used for tracking a regression from 2.6.33. Please don't close it until the problem is fixed in the mainline.
FWIW here's my reply to the initial mail with some dmesg info : http://marc.info/?l=linux-kernel&m=127074346725322&w=2
*** This bug has been marked as a duplicate of bug 15749 ***
I bisected the ACPI error message down to this : tfoerste@n22 ~/devel/linux-2.6 $ make scripts/kconfig/conf -s arch/x86/Kconfig -.. CC ipc/syscall.o ipc/syscall.c:17: error: conflicting types for ‘sys_ipc’ include/linux/syscalls.h:691: error: previous declaration of ‘sys_ipc’ was here make[1]: *** [ipc/syscall.o] Error 1 make: *** [ipc] Error 2 (reverse-i-search)`skip': cat ~/^Cipped tfoerste@n22 ~/devel/linux-2.6 $ git bisect skip There are only 'skip'ped commits left to test. The first bad commit could be any of: 1ee4d61fd9822fb89e63b88a66848477087cd82e bc73675b99fd9850dd914be01d71af99c5d2a1ae We cannot bisect more!
Toralf, Just use the patch from #15749.
(In reply to comment #4) > Toralf, > > Just use the patch from #15749. Yep - that solved it. Unfortunately I wasn't on Cc: at this bug report (or I ignored the appropriate mail) - b/c otherwise I wouldn't bisect a already discovered issue ... :-/