Battery stats only work intermittently on Surface Pro 2017 about surface-aggregator-module HOT 8 CLOSED

Apologies about the closing and reopening; my account was flagged by GitHub and I didn't think the actions would go through.

from surface-aggregator-module.

from surface-aggregator-module.

Alright, they appear to have finally rectified it after my account getting flagged a second time immediately after it was fixed once. Sorry about that again.

What do you mean by two-button reset? Something like REISUB? I did clean install at one point.

from surface-aggregator-module.

Glad you could get that resolved.

What do you mean by two-button reset?

Press and hold power and volume-up button (while powered on) until the device restarts. If you have a charger or dock connected, the led on that should turn off after a while and then back on (at that point you can also release the buttons and start the device normally). This completely resets the EC so we can make sure it's not some weird quirk.

As for your edits on your first comment:

1. There are a few devices involved, MSHW0084 is the Serial-Hub, so basically the communication master. MSHW0091 is the ACPI Notify device, which is basically a bridge from the Serial-Hub to ACPI. The final error message is displayed on MSHW0091 because that's actually the communication endpoint (i.e. it communicates via MSHW0084 with the EC). The serial0-0 device is actually the MSHW0084 device, which in this case re-tries the communication 2 additional times to handle sporadic I/O failures.

2. There haven't been many changes to the core since the first version. We've had a similar problem in the past, but this should be fixed since we switched to DMA. There are still sporadic I/O failures to be expected (mostly during boot or resume when the kernel is busy) due to the current DMA implementation for serial devices, which (if I remember correctly, may have changed) only uses one buffer instead of a rotating set. However, there should at most be two failures in succession (1 overflow due to full DMA buffer + 1 potential invalid start due to the emptied buffer arriving mid-transaction).

from surface-aggregator-module.

@hpfr Did the reset work?

from surface-aggregator-module.

Going to close this. a) there hasn't been any response to this for a while, b) I haven't heard of any other issues resembling this lately, and c) there have been quite a lot of changes in the SAM/SSH driver which should have made communication a bit more stable.

Feel free to comment if this issue still persists.

from surface-aggregator-module.

Sorry for the radio silence. Like you said, I believe the changes to the driver have eliminated this for me. Thanks!

from surface-aggregator-module.

Thanks for the feedback!

from surface-aggregator-module.