https://bugs.freedesktop.org/show_bug.cgi?id=105725

hjpriester@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |x86-64 (AMD64) CC| |hjpriester@gmail.com OS|All |Linux (All)

https://bugs.freedesktop.org/show_bug.cgi?id=105725

--- Comment #2 from hjpriester@gmail.com --- Is there a guide a build the 4.15.x kernel using the drm-4.17-wip? I can try to compile/test it next weekend.

The problem I have is that when I display a certain png with "imagemagick display" X11 hangs. The screen is not longer updated and only a reboot helps.

When I run the program using strace the last system call displayed is:

ioctl(6, DRM_IOCTL_AMDGPU_WAIT_CS.

That is why I am thinking it might have to do with the amdgpu.

https://bugs.freedesktop.org/show_bug.cgi?id=105725

--- Comment #4 from hjpriester@gmail.com --- Harry,

I have build a kernel using the:

git clone -b drm-next-4.17-wip git://people.freedesktop.org/~agd5f/linux

I did the clone about 2018-29-03 20:00 UTC

The warnings are still there. root@hjp2:~# dmesg | grep -i Warning [ 0.000000] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20180105/tbfadt-658) [ 5.351226] WARNING: CPU: 1 PID: 491 at drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_base.c:64 dal_gpio_open_ex+0xc/0x30 [amdgpu] [ 5.353376] WARNING: CPU: 1 PID: 491 at drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:487 dal_ddc_open+0x2c/0xd0 [amdgpu]

I never get the hang during a boot. I will report that as a separate bug.

The display I am using is a IIYama Prolite XUB2792QSU using Displayport. It it a 27" 2560x1440 monitor. The distrubution is Slackware-current. ("pre 15.0")

https://bugs.freedesktop.org/show_bug.cgi?id=105725

higuita@gmx.net changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |higuita@gmx.net

--- Comment #6 from higuita@gmx.net --- running 4.17.1 on a asus rx480 i also get this

I do not see any hang or problem due to this warning/oops

https://bugs.freedesktop.org/show_bug.cgi?id=105725

--- Comment #8 from Marc Thomas marc@dragonfly.plus.com --- 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.

In Slackware-current I think pinctrl_amd was compiled in, so I had to change the Kernel config and re-compile:

-CONFIG_PINCTRL_AMD=y +CONFIG_PINCTRL_AMD=m

The blacklist was achieved by creating this file: root@deepthought:~# cat /etc/modprobe.d/gpio_amdpt.conf blacklist gpio_amdpt blacklist pinctrl_amd

NB: I found that once I'd had these kernel warnings I needed to reset the hardware (front panel reset button or power cycle) to clear them, even with the blacklist in place. A reboot didn't seem to be enough.

Finally, I do still get this warning (in 4.18-rc6 & 4.17.10), but I think the cause is something else:

root@deepthought:~# dmesg | grep WARNING [ 9.260098] WARNING: CPU: 15 PID: 1138 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:88 dm_dp_aux_transfer+0xa5/0xb0 [amdgpu] [ 9.260163] WARNING: CPU: 4 PID: 1142 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:88 dm_dp_aux_transfer+0xa5/0xb0 [amdgpu]

https://bugs.freedesktop.org/show_bug.cgi?id=105725

--- Comment #10 from Marc Thomas marc@dragonfly.plus.com --- (In reply to Alex Deucher from comment #9)

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 bug 107456.

https://bugs.freedesktop.org/show_bug.cgi?id=105725

Petr Cvek petrcvekcz@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |petrcvekcz@gmail.com

--- Comment #12 from Petr Cvek petrcvekcz@gmail.com --- Created attachment 142485 --> https://bugs.freedesktop.org/attachment.cgi?id=142485&action=edit Suggested fix with a semaphore

https://bugs.freedesktop.org/show_bug.cgi?id=105725

--- Comment #14 from hjpriester@gmail.com --- I am now running 4.19.4 and did not get the messages anymore. The messages where there from 4.5.11 to 4.18.16

https://bugs.freedesktop.org/show_bug.cgi?id=105725

Martin Peres martin.peres@free.fr changed:

What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED

--- Comment #16 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/336.