https://bugzilla.kernel.org/show_bug.cgi?id=44161

--- Comment #162 from Juan Manuel Cabo <juanmanuel.c...@gmail.com> ---
(In reply to Kieran Clancy from comment #160)
> @Joseph Salisbury
> 
> At this stage it's only been tested on a few machines. I'd like to give it a
> few more days, especially to see what kind of numbers come back from the
> "... EC events polled" messages.
> 
> If all goes well I plan to submit the patch.

----------------
Testing results with San build of Kieran patch (comment #149 and comment #155)
----------------

*) Boot with an old kernel. Suspend. Unplug/plug/....(more than 8 times).
Resume. Issue shows. Install new kernel (download, sudo dpkg -i *.deb). Reboot.
Result in /var/log/syslog and dmesg: 
     Clearing stale EC events
     8 EC events polled.
(as previously tested, Kieran patch continues to poll at boot. Good!)
Everything returned to normal, issue resolved.

*) Suspend with lid. Open lid while suspended (1 action). 
Result: "1 EC events polled.". 
I guess it was "lid open event". Will test without the lid so I don't have to
subtract its lid open event.

*) Suspend through menu (instead of lid). Resume without doing nothing. 
Result: "0 EC events polled."

*) Suspend through menu. Unplug/plug/unplug/plug (4 actions). 
Result: "4 EC events polled."

*) Suspend through menu. Unplug/plug... (6 actions). 
Result: "6 EC events polled."

*) Suspend through menu. Unplug/plug... (18 actions). 
Result: "8 EC events polled."


CONCLUSIONS: 

A) The patch keeps working perfectly, resolving all situations.

B) My Series 5 NP530U3C accumulates up to 8 events. Not more as I previously
thought.

C) I think 20 is a good number for ACPI_EC_CLEAR_ITER.


So I was wrong about the 16 events number. It is actually definitely 8. I
previously assumed it was double, because when unplugging with 'acpi_listen'
open, one can see both ADP1 and BAT1 devices being triggered (the CPU devices
are notified from the DSDT when the AC _Q51 or _Q52 methods are called, so they
don't count). So I assumed that two events were generated per plug. But it
seems not, or at least not during sleep.
    When I discovered that 8 unplug or plug actions were necessary to trigger
the problem state, I assumed that each accumulated two events, so I thought 16
total. I was wrong there. Definitely it's 8 max accumulated events.

Cheers!
--
Juan Manuel Cabo

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to