Comment 16 for bug 139701

I tried the ec_intr=0, as documented above with dmesg. Though I'm a bit nervous that I don't know how to check a running system to see if the command line "took" or not. Any tips?

It may have helped some, but I'm still seeing bad ACPI output.

Gutsy 32 bit, System76 Darter daru2, pretty up-to-date with updates....

Booted at about Feb 26 19:30 last night.

Ran this after boot:
( while true; do
    date; time acpi -V; sleep 300;
done ) 2>&1

Got normal results for about 6 hours, like this:
     Battery 1: charging, 90%, 00:17:50 until charged
     Thermal 1: ok, 60.0 degrees C
  AC Adapter 1: on-line

real 0m0.132s
user 0m0.000s
sys 0m0.028s

I watch the time output because the other big symptom for me has been very slow responses to the acpi command - e.g. 6 to 30 seconds.
That problem hasn't come back yet, even after doing a suspend resume.

Then I suddenly started getting odd results: sometimes says it was
off-line, missing Battery 1 data entirely, etc. like this.

 Wed Feb 27 01:42:22 MST 2008
     Battery 1: charged, 100%
     Thermal 1: ok, 52.0 degrees C
  AC Adapter 1: off-line

Wed Feb 27 01:47:22 MST 2008
     Thermal 1: ok, 210.0 degrees C
  AC Adapter 1: on-line

Wed Feb 27 02:17:22 MST 2008
     Battery 1: charging, 0%, 05:20:00 until charged
     Thermal 1: ok, 210.0 degrees C
  AC Adapter 1: on-line

And it is still doing that now....

I was asleep when the bad results started, and haven't run anything
cpu-intensive that I can think of.

I sometimes use this command to dump all the /proc/acpi files:

  more `find /proc/acpi -type f`

that output is attached