Brennan Vincent <[email protected]> writes: > On 10/21/20 9:56 PM, Ashton Fagg wrote: >> Brennan: >> >> I've experienced this also. I'm using different hardware than you >> (Thinkpad, with amdgpu). Here's my dmesg also in case it is useful. >> >> I would say it happens about 1 in 3 times I open the lid - and same >> thing, I either press the power button or a key on the keyboard and it >> comes back to life. >> > > Interesting. For me, it happens consistently.
Just following up on this (and also wondering if Brennan had any success in figuring this out). One of the suggestions was to run a kernel with ACPI_DEBUG enabled in order to try and capture debugging. Unfortunately with ACPI_DEBUG enabled it seems I can't reproduce this. This indicates to me that the slight timing changes introduced by printing the debug data is enough to mitigate/hide this problem. Without ACPI_DEBUG however it happens as I said roughly 1/3 times I open the lid. Are there any further steps I can take to try and capture debugging output to narrow this down?
