Re: Wake from sleep kinda broken-ish? (ThinkPad Carbon X1 6th gen)

On Mon, Oct 12, 2020 at 5:22 PM Eirik Øverby <ltning_at_anduin.net> wrote:
>
> On Wednesday, September 16, 2020 9:05:43 AM CEST Warner Losh wrote:
> > I too can report this for my Lenovo Yoga running code as of September 13,
> > but with manu's latest drm...  It used to work fine, but my last build on
> > the system was from May. Most likely a new panic in that code path, but
> > I've not chased down further...
>
> So I got a gen8 to play with, and the list of grievances is long - but I have
> one observation that may be of interest:
> The gen8 would be usable (at least seemingly so) with a 13-kernel from lat
> 2019 or very early 2020. Then around the end of January - I've bisected it
> down to around Jan 24, give or take, it would start wedging _hard_ after a
> minute or two of heavy load (compiling, cat /dev/random, that sort of thing).
> It was a problem prior to that too but it was _much_ harder to trigger, at
> least based on my tests this weekend.
>
> The "solution" is to add
>   hint.hwpstate_intel.0.disabled="1"
> to /boot/loader.conf. This obviously has disastrous impact on battery life.
> The emt module takes over, so power management is a lot more rudimentary
> (powerd now does nearly nothing, while powerd++ kills interactivity). Battery
> life is much shorter than on my gen6, and it gets hotter.
>
> BUT: This thing - gen8 - would get stuck in the acpi_beep before adding this
> to loader.conf. After adding the hint, I have not had a single failure when
> resuming. It's behaving much better than my gen6.

Recently I got an interesting observation: if I suspend with `zzz`,
(which is basically doing `acpiconf -s S3`), and resuming by pushing
the power button, there is 95% chance of resuming failure.
However, if I use close/open the lid to suspend/resume, I haven't hit
any failure since last week.

I suppose that these 2 suspend/resume methods are basically doing the
same thing?  My hw.acpi.lid_switch_state sysctl is S3.

I have tried suspending with `zzz` then closing the lid, there is
about 50% failure rate, but the sample number is very small.

Is there any idea about what makes the difference between these 2
suspend/resume methods?

I'm running 13.0-CURRENT r367582, with drm-devel-kmod-5.4.62.g20201109
and gpu-firmware-kmod-g20200920. My /boot/loader.conf has
hw.i915kms.enable_psr=0 but no hint.hwpstate_intel.0.disabled=1

Best,
Li-Wen