| Bug ID | 99330 |
|---|---|
| Summary | Severe flickering with Fiji on Wayland |
| Product | Mesa |
| Version | unspecified |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | vedran@miletic.net |
| QA Contact | dri-devel@lists.freedesktop.org |
I am using 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] [1002:7300] (rev ca) (prog-if= 00 [VGA controller]) on Fedora 25 running GNOME 3 with Mesa git and LLVM git on two 4K monitors. When using Wayland, there is a noticeable flickering in the upper part of t= he screen when switching between desktops. Nothing relevant is shown in dmesg. Also, when using Xorg, everything works fine. Would a screenshot be useful? Any other info I can provide?
Which exact version is that of gnome-shell and mutter?
(In reply to Ernst Sj=C3=B6strand from comment #1) > Which exact version is that of gnome-shell and m= utter? gnome-shell-3.22.2-2.fc25.x86_64 mutter-3.22.2-3.fc25.x86_64
I happen to have 2 4K monitors and a Fury as well actually.
I actually couldn't run Wayland at all for some time, perhaps it was fixed =
by:
mutter (3.22.2-3) unstable; urgency=3Dmedium
[ Jeremy Bicha ]
* Add git_flush_all_swap_notifies_on_idle.patch:
- Add patch from 3.22 branch that fixes freezes with multiple monitors
on Wayland
landing in my Ubuntu repos.
Anyway, today I can run gnome shell in Wayland and I don't have any flicker=
ing.
Do you have the very latest firmware from
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmwar=
e.git ?
Guess the devs always like dmesg and xorg... wait nevermind that last part.=
:-)
Maybe journalctl /usr/bin/gnome-shell ?
Wait, actually after some DPMS and [ 4378.466823] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery tried 5 times [ 4378.466834] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock recovery failed journalctl /usr/bin/gnome-shell now show a bunch of stuff like: jan 09 22:06:51 mammut gnome-shell[1675]: Failed to flip: Invalid argument jan 09 22:06:52 mammut org.gnome.Shell.desktop[1675]: Window manager warnin= g: Failed to read EDID of output DP-3: Filen eller katalogen finns inte jan 09 22:06:52 mammut gnome-shell[1448]: Failed to apply DRM plane transfo= rm 0: Access denied=20 jan 09 22:06:52 mammut gnome-shell[1448]: Failed to apply DRM plane transfo= rm 0: Access denied jan 09 22:06:52 mammut gnome-shell[1675]: Failed to apply DRM plane transfo= rm 0: Invalid argument jan 09 22:06:52 mammut gnome-shell[1675]: Failed to apply DRM plane transfo= rm 0: Invalid argument jan 09 22:06:53 mammut org.gnome.Shell.desktop[1675]: Window manager warnin= g: Failed to read EDID of output DP-3: Filen eller katalogen finns inte jan 09 22:06:53 mammut org.gnome.Shell.desktop[1675]: Window manager warnin= g: Failed to read EDID of output DP-3: Filen eller katalogen finns inte jan 09 22:06:53 mammut org.gnome.Shell.desktop[1675]: Window manager warnin= g: Failed to read EDID of output DP-3: Filen eller katalogen finns inte jan 09 22:06:53 mammut org.gnome.Shell.desktop[1675]: Window manager warnin= g: Failed to read EDID of output DP-3: Filen eller katalogen finns inte jan 09 22:06:53 mammut org.gnome.Shell.desktop[1675]: Window manager warnin= g: Failed to read EDID of output DP-3: Filen eller katalogen finns inte jan 09 22:06:53 mammut org.gnome.Shell.desktop[1675]: Window manager warnin= g: Failed to read EDID of output DP-3: Filen eller katalogen finns inte jan 09 22:06:53 mammut org.gnome.Shell.desktop[1675]: Window manager warnin= g: Failed to read EDID of output DP-3: Filen eller katalogen finns inte jan 09 22:06:53 mammut gnome-shell[1448]: Failed to apply DRM plane transfo= rm 0: Access denied jan 09 22:06:53 mammut gnome-shell[1675]: Failed to apply DRM plane transfo= rm 0: Invalid argument Still, this could just as well be a gnome-shell bug? Does it work with an older mesa/llvm version for you?
(In reply to Ernst Sj=C3=B6strand from comment #3) > I happen to have 2 4K monitors and a Fury as wel= l actually. >=20 > I actually couldn't run Wayland at all for some time, perhaps it was f= ixed > by: > mutter (3.22.2-3) unstable; urgency=3Dmedium >=20 > [ Jeremy Bicha ] > * Add git_flush_all_swap_notifies_on_idle.patch: > - Add patch from 3.22 branch that fixes freezes with multiple moni= tors > on Wayland > landing in my Ubuntu repos. > That's also in Fedora as far as I can tell: = https://koji.fedoraproject.org/koji/buildinfo?buildID=3D823521 (In reply to Ernst Sj=C3=B6strand from comment #4) > Does it work with an older mesa/llvm version for= you? Mesa 13 and LLVM 3.8 in stock Fedora doesn't help.
Got it, thanks Ernst: Jan 10 17:44:30 localhost.localdomain gnome-shell[22110]: Failed to flip: Invalid argument I also got the following in dmesg, but it's likely unrelated as I get it wi= th Xorg as well: [Tue Jan 10 17:44:29 2017] [drm:amdgpu_crtc_page_flip [amdgpu]] *ERROR* fai= led to get vblank before flip
Please attach the dmesg output, preferably captured after the = problem occurred. (In reply to Vedran Mileti=C4=87 from comment #6) > Jan 10 17:44:30 localhost.localdomain gnome-shel= l[22110]: Failed to flip: > Invalid argument >=20 > I also got the following in dmesg, but it's likely unrelated as I get = it > with Xorg as well: >=20 > [Tue Jan 10 17:44:29 2017] [drm:amdgpu_crtc_page_flip [amdgpu]] *ERROR* > failed to get vblank before flip It might be related. There might be similar messages about the page flip io= ctl failing in the Xorg log file, Xorg might just be more resilient against it.=
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | NOTOURBUG |
Somehow can't reproduce it right now. The only related package= I see in my today's updates is GTK3 3.22.6-2.fc25 [1] which fixes [2]. Could be that. W= ill report if it happens again. [1] https://koji.fedoraproject.org/koji/buildinfo?buildID=3D832589 [2] https:/= /bugzilla.gnome.org/show_bug.cgi?id=3D769835