https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283113

SolarCatcher <solarcatc...@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |solarcatc...@gmx.de

--- Comment #6 from SolarCatcher <solarcatc...@gmx.de> ---
Seems like I am experiencing a similar problem: 

On a new Framework Laptop 13, with AMD Ryzen 5 7640U w/ Radeon 760M Graphics,
after loading amdgpu kernel module (manually or via rc.conf), I cannot
powerdown the laptop anymore (e.g. 'shutdown -p now').

At shutdown, everything looks good until the screen goes black. However, the
powerbutton remains active (light). I have to press it several seconds to force
a complete powerdown.

These are the additional kernel modules loaded when I issue a 'kldload amdgpu',
as per kldstat:

31    1 0xffffffff83e00000   666888 amdgpu.ko
32    2 0xffffffff84467000    85090 drm.ko
33    1 0xffffffff83df3000     22b8 iic.ko
34    2 0xffffffff83df6000     4120 linuxkpi_video.ko
35    3 0xffffffff844ed000     7350 dmabuf.ko
36    3 0xffffffff83dfb000     3378 lindebugfs.ko
37    1 0xffffffff844f5000     c338 ttm.ko
38    1 0xffffffff84502000    48a60 amdgpu_gc_11_0_1_mes_2_bin.ko
39    1 0xffffffff8454b000    3a890 amdgpu_gc_11_0_1_mes1_bin.ko
40    1 0xffffffff84586000     2ae0 amdgpu_psp_13_0_4_toc_bin.ko
41    1 0xffffffff84589000    446a0 amdgpu_psp_13_0_4_ta_bin.ko
42    1 0xffffffff845ce000    4ba00 amdgpu_dcn_3_1_4_dmcub_bin.ko
43    1 0xffffffff8461a000    225e0 amdgpu_gc_11_0_1_imu_bin.ko
44    1 0xffffffff8463d000    425e0 amdgpu_gc_11_0_1_pfp_bin.ko
45    1 0xffffffff84680000    425e0 amdgpu_gc_11_0_1_me_bin.ko
46    1 0xffffffff846c3000    29430 amdgpu_gc_11_0_1_rlc_bin.ko
47    1 0xffffffff846ed000    43a80 amdgpu_gc_11_0_1_mec_bin.ko
48    1 0xffffffff84731000     a7e0 amdgpu_sdma_6_0_1_bin.ko
49    1 0xffffffff8473c000    5bb00 amdgpu_vcn_4_0_2_bin.ko

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

Reply via email to