wessel-novacustom
commented
2 months ago Some application or event must have caused an EC crash. I remember I had this once after tweaking TLP for a better battery life on my personal laptop.
Unluckily, we don't have an EC fallback stop yet in v1.7.2 for your laptop. This will be present in future updates, so that you can always turn off the laptop by holding the power button for 10 seconds.
For now, the only thing you can do to reset the laptop in such a situation is to remove the battery connector from the mainboard and to re-connect it.
Component
Dasharo firmware, EC firmware
Device
NovaCustom NS5x 12th Gen
Dasharo version
v1.7.2
Dasharo Tools Suite version
No response
Test case ID
No response
Brief summary
When suspending, the DUT stays on but the screen goes dark and the device no longer responds to any input, including pressing the power button. The kernel log reports that the EC is unresponsive.
How reproducible
Very rarely, only three times in total so far. (but twice within the last week)
How to reproduce
Expected behavior
The device suspends and resumes as normal
Actual behavior
The screen goes dark, but the device keeps running. It emits a noise similar to coil whining. No input is registered at all, including from the power button. There is no way to even power off the device.
Screenshots
No response
Additional context
The DUT runs the latest FW/EC versions (1.7.2) with suspend mode set to s0ix and the Management Engine enabled. Charge thresholds are configured to start/stop at 50%/60%. I suspect this is a EC problem, because the kernel reports that its attempts to control the EC time out. So far, the affected kernel versions include 6.8 and 6.10. (I'm running Gentoo) I am pretty sure that when the bug is triggered, the DUT does not even initiate the actual suspend process, as nothing to the indication is logged by the kernel and the device stays connected to WiFi. However, the fans seem to turn off and the device gets noticeably warm.
Relevant log snippet:
These errors keep on repeating every few seconds.
During the latest occurrence, the DUT's screen happened to wake up on its own, probably due to a notification from a terminal emulator about a closed ssh session? At least the touchpad worked, but the internal keyboard and all other buttons remained unresponsive. I was able to unlock the device using a USB keyboard. When attempting to suspend again, the kernel logged the following errors:
While I cannot spot anything out of the ordinary there, attached is also a dump of the coreboot log: coreboot.log
Solutions you've tried