http://bugzilla.kernel.org/show_bug.cgi?id=9147
--- Comment #161 from Daniele C. <legolas...@users.sourceforge.net> 2009-07-03 13:07:05 --- Created an attachment (id=22191) --> (http://bugzilla.kernel.org/attachment.cgi?id=22191) bug 9147 test results on kernels 2.6.29 (w/o fedora11 patches), 2.6.29-5 (w/o fedora11 patches), 2.6.30 >From my tests (see attachment) it can clearly be deduced that the bug is not triggered when using built-in ACPI modules; I have not yet triggered it with builtin ac,battery,thermal,container,processor built-in modules and I will keep using this kernel. I will add a comment if I trigger the bug. I invite other testers to use a kernel with such built-in ACPI modules to see if the bug appears; I assume it is very hard to trigger when modules are built-in, when instead can be easily triggered with my test script when modules are separated from kernel. Can somebody please explain why there is such difference? It has apparently become more deep from previous kernels, since bug was easily triggered also with built-in ACPI modules with previous kernels. So right now the best workaround is to compile the above mentioned modules as builtin. To make the point: Fedora10/Fedora11 do not have any patch which addresses bug 9147 as side effect, it's just that they compile the guilty modules as built-in making the bug gone or very hard to trigger. Also, I haven't yet been able to enable (via kernel .config) the correct options to show again the dmesg messages when a key gets stuck. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. ------------------------------------------------------------------------------ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
