http://bugzilla.kernel.org/show_bug.cgi?id=8459
------- Comment #52 from [EMAIL PROTECTED] 2007-10-08 10:36 ------- Created an attachment (id=13081) --> (http://bugzilla.kernel.org/attachment.cgi?id=13081&action=view) dmesg of the patch from comment #51 I applied the patch from comment #51 to 2.6.23-rc8. In the dmesg the following two lines repeats: [ 203.467620] ACPI: EC: lost interrupt, switch to degraded mode [ 203.467634] ACPI: EC: interrupt mode is broken, switch it off [ 203.968668] ACPI: EC: lost interrupt, switch to degraded mode [ 203.968682] ACPI: EC: interrupt mode is broken, switch it off ... and so on. The result of the 1000 read of /proc/acpi/thermal_zone/THRM/temperature is: min: 0.003 avg: 0.310 max: 3.508 I don't really get your point: how can you solve the auto switch if there _is_ an interrupt after write, but there is _not_ after read. If the comment at the top of the patch is still true, the patch will see that there is an interrupt after write: OK, lets switch to interrupt mode. Then the read comes: timeout, lets switch to poll mode. Next time the write comes, it will switch again to interrupt mode. I can imagine two solution: 1. separate read and write interrupt 2. start from the interrupt mode, and if one single interrupt is missing, switch to poll mode permanently. In this case I would printk() a warning (if ever would some vendor use Linux to verify the ACPI EC, he/she would recongise that there is a deviation from the ACPI standard). Starting from poll mode would be difficult because you never know how the timing of the status register change and interrupt will be. If the status register already signals that the data is ready, the interrupt might not be lost but needs still needs a short time to come. Concerning the dumper patch I am pleased and happy to give it free. I would only ask you to put my 'Signed-off-by: Márton Németh <[EMAIL PROTECTED]>' line also to the patch. -- 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, or are watching someone who is. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
