<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - WARNING: CPU: 0 PID: 487 at drivers/gpu/drm/amd/amdgpu/../display /dc/gpio/gpio_base.c:64 dal_gpio_open_ex+0xc/0x30 [amdgpu]" href="https://bugs.freedesktop.org/show_bug.cgi?id=105725#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - WARNING: CPU: 0 PID: 487 at drivers/gpu/drm/amd/amdgpu/../display /dc/gpio/gpio_base.c:64 dal_gpio_open_ex+0xc/0x30 [amdgpu]" href="https://bugs.freedesktop.org/show_bug.cgi?id=105725">bug 105725</a> from <a class="email" href="mailto:marc@dragonfly.plus.com" title="Marc Thomas <marc@dragonfly.plus.com>"> Marc Thomas</a> <pre>(In reply to Alex Deucher from <a href="show_bug.cgi?id=105725#c9">comment #9</a>) > It's possible that there are issues with gpio-amdpt and pinctrl-amd that > lead to general system stability issues, but it should be noted the the gpio > stuff in amdgpu is completely unrelated to those modules. I think you're right - I still do get these warnings in 4.18.9 even with the modules blacklisted; just not all the time. Interestingly I found the other warning I get from amdgpu_dm/amdgpu_dm_mst_types.c can be provoked by running "xcmddc -lv". It seems udevd does this during boot. See also <a class="bz_bug_link bz_status_NEW " title="NEW - WARNING: CPU: 11 PID: 1137 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:88 dm_dp_aux_transfer+0xa5/0xc0 [amdgpu]" href="show_bug.cgi?id=107456">bug 107456</a>.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>