<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#c9">Comment # 9</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:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> Alex Deucher</a> <pre>(In reply to Marc Thomas from <a href="show_bug.cgi?id=105725#c8">comment #8</a>) > After some testing/experimentation/and scouring the internet, I've found > that blacklisting modules gpio_amdpt (gpio-amdpt.ko) & pinctrl_amd > (pinctrl-amd.ko) greatly reduce the likelihood of the gpio_base.c:64 & > gpio_service.c:488 dmesg warnings. I suspect some kind of race condition > during boot as the modules may load in any order. 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>