https://bugzilla.kernel.org/show_bug.cgi?id=203035

--- Comment #21 from Derek J. Clark (derekjohn.cl...@gmail.com) ---
(In reply to leo60228 from comment #20)
> Created attachment 286979 [details]
> attachment-7455-0.html
> 
> Most of what I do is CPU-bound and my AC power jack is broken (the little
> plastic ring is gone so the cord doesn't stay in), so I'm more concerned
> about the battery status than GPU performance. I'm guessing that workaround
> doesn't help with that? Either way, good job.
> 
> On Sat, Jan 25, 2020, 9:00 PM <bugzilla-dae...@bugzilla.kernel.org> wrote:
> 
> > https://bugzilla.kernel.org/show_bug.cgi?id=203035
> >
> > --- Comment #19 from Derek J. Clark (derekjohn.cl...@gmail.com) ---
> > (In reply to Dave from comment #18)
> > > (In reply to Thanathan from comment #3)
> > > > Additionally I lost gui/tui output shortly after the kernel was loaded,
> > > > including ttys. Reverting to linux-firmware 20190424.4b and rebuilding
> > > > initramfs fixed the issues.
> > >
> > > I have found that I get similar hangs when the GPU is in the lowest
> > clock /
> > > memory clock state, as well as the highest state.  Disabling these two
> > > states via:
> > >
> > > echo "manual" >
> > /sys/class/drm/card0/device/power_dpm_force_performance_level
> > > echo "2 3" > /sys/class/drm/card0/device/pp_dpm_mclk
> > > echo "3 4 5 6" > /sys/class/drm/card0/device/pp_dpm_sclk
> > >
> > > Allows the laptop to avoid these hangs with the updated firmware (though
> > at
> > > a performance loss and higher idle power.)
> > >
> > > I also noticed that these hangs are a reliable way to trigger the power
> > > issue, where the cord isn't recognized, as it persists after boot
> > (sometimes
> > > for two or three boots before it is recognized again.)
> > >
> > > Additionally, this problem only appears after boot - while waiting at the
> > > dmcrypt prompt, for instance, power is always detected normally.
> >
> > Took your input and updated my workaround on github. Provides decent
> > operation
> > for now.
> >
> > https://github.com/pastaq/Acer-Ryzen-Helios-AC-Fix
> >
> > --
> > You are receiving this mail because:
> > You are on the CC list for the bug.

It seems like the GPU power states disabled by the workaround are not handled
by the drivers properly and it causes many power/performance related problems.
The symptoms include lower GPU performance, CPU state stuck at 500Mhz, and lid
closing causing the screen to have 100% distortion. This github workaround
appears to solve all of these issues. However its not 100% stable and can still
have some crashes. If you don't need (much) 3D acceleration and want the CPU to
work as normal, admgpu.dpm=0 as a kernel boot parameter will allow the CPU to
work as intended as it bypasses the buggy AMDGPU power state handling.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to