Open bflanagin opened 3 years ago
Can you add this to the kernel parameters:
acpi.aml_debug_output=1
acpi.aml_debug_output=1 fails using sysctl -w
with:
sysctl: cannot stat /proc/sys/acpi/aml_debug_output: No such file or directory
This is with 5.11 however the input error happened on the older kernel as well.
Use sudo kernelstub -a acpi.aml_debug_output=1
and then reboot
I've experienced this same thing on a gaze15. This has typically happened under some sort of heavy load, such as compiling Unreal Engine 4 or most recently, running No Man's Sky. I've seen this resolved by leaving the laptop for about 10 minutes, then shutting it off and rebooting. Keyboard becomes responsive again and battery estimate is displayed.
This has happened under Nvidia Graphics; I haven't tried to replicate under Hybrid yet.
Kernel is 5.13.9-xanmod1
Following the advice of support, I used the same command as recommended by @jackpot51:
sudo kernelstub -a acpi.aml_debug_output=1
After entering the command into Terminal and rebooting, I've attempted to replicate the issue by playing through No Man's Sky over the last hour. Thus far, I haven't experienced the issue again. I will continue to test with both No Man's Sky and other games that may require shader compilation to see if I can cause the same issue again.
I was able to replicate this issue by simultaneously:
Attached are the logs generated by the System76 Driver application while the issue was occurring; I was able to bypass the problem by plugging in an external USB keyboard, which allowed the external keyboard to type normally; while the keyboard was plugged in, the on-board keyboard was still experiencing the issues described. Battery level was also displayed as "Estimating..." during this time.
I was finally able to replicate the issue on my gaze15 as well. keyboardIssue-08202021.txt
gaze15 owner here with (mostly) the same issue, only this time on firmware 2022-11-21_b337ac6
. I've observed this issue when booting Pop!_OS or Windows 11. My observations only cover the keyboard being delayed. While I have observed battery issues, I have not yet identified a probable cause.
My issue typically occurs after a reboot. The issue can be avoided if the user fully shuts down the machine and starts it back up, instead of rebooting.
Observed behaviour is slow keyboard input when entering a system's encryption password (Pop!_OS or Windows). After the system boots the OS feels sluggish and some things don't work right, such as a Bluetooth mouse in Pop!_OS.
I can easily spot when the issue is happening due to the aforementioned Bluetooth mouse issue.
Issue is hard to duplicate due to its seemingly random occurrence. However, once triggered the systems battery monitor can no longer estimate the time left on the battery. At the same time the input from the keyboard becomes delayed to the point where the user would be forced to power off the laptop in order to regain both battery monitoring and keyboard.
Here is the
journalctl -b0
output: keyboard_issue.txtThe system wasn't under load when the issue happened.