Bug 90406

Summary: garbage on screen after gdm VT switch
Product: xorg Reporter: Mantas Mikulėnas <grawity>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: lee295012, marvin24, mboquien
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
example after a soft reboot
none
Xorg log from journalctl
none
EXA: Set pixmap pitch from BO none

Description Mantas Mikulėnas 2015-05-11 20:53:30 UTC 
GNOME's gdm 3.16 uses separate VTs for the login screen & user session. Somehow, when it switches the VTs, garbage is displayed on screen for a short while (instead of the expected gray gdm texture). It goes away as soon as gnome-shell begins its launch animation.

At the same time, I get this in dmesg:

[ 1294.609195] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:851 texture bo too small (layer size 4325376, offset 0, max layer 1, depth 1, bo size 4227072) (1408 768)
[ 1294.609247] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !

Specifically, the "garbage" appears to be uninitialized memory, since after soft reboot I can still see shredded parts of my previous session. (Very similar to #72979, even though that one is for nouveau and I use radeon.)

screen: LVDS at 1366x768
kernel 4.0, 4.1~rc3
gdm 3.16.1
xorg-server 1.17.1
xf86-video-ati 7.5.0
Comment 1 Mantas Mikulėnas 2015-05-11 20:57:34 UTC 
Created attachment 115703 [details]
example after a soft reboot
Comment 2 Mantas Mikulėnas 2015-05-11 21:00:08 UTC 
Also: This also happens when gdm starts openbox (a simple non-compositing WM), not only with gnome-shell. In case that's relevant.
Comment 3 Marc Dietrich 2015-05-28 14:25:12 UTC 
do you have DRI3 enabled?
Comment 4 Mantas Mikulėnas 2015-05-28 15:13:34 UTC 
Created attachment 116119 [details]
Xorg log from journalctl

Apparently no, I don't:

(II) RADEON(0): [DRI2] Setup complete
(II) RADEON(0): [DRI2]   DRI driver: r600
(II) RADEON(0): [DRI2]   VDPAU driver: r600
(II) RADEON(0): Front buffer size: 4128K
(II) RADEON(0): VRAM usage limit set to 928386K
(==) RADEON(0): DRI3 disabled
(==) RADEON(0): Backing store enabled
(II) RADEON(0): Direct rendering enabled
Comment 5 Michel Dänzer 2015-05-29 03:27:22 UTC 
Created attachment 116135 [details] [review]
EXA: Set pixmap pitch from BO

Does this xf86-video-ati patch help?
Comment 6 Mantas Mikulėnas 2015-05-29 05:42:49 UTC 
(In reply to Michel Dänzer from comment #5)
> Created attachment 116135 [details] [review] [review]
> EXA: Set pixmap pitch from BO
> 
> Does this xf86-video-ati patch help?

No, I still see the same as before.
Comment 7 Michel Dänzer 2015-05-29 10:16:35 UTC 
(In reply to Mantas Mikulėnas from comment #6)
> No, I still see the same as before.

Bummer, but I still think the problem is probably that the pitch of the pixmap created in create_pixmap_for_fbcon is getting over-aligned, most likely somewhere in EXA. Somebody "just" needs to isolate where and how to fix it.

FWIW, this should work correctly with glamor and current xf86-video-ati Git.
Comment 8 Mantas Mikulėnas 2015-05-29 10:52:13 UTC 
(In reply to Michel Dänzer from comment #7)
> (In reply to Mantas Mikulėnas from comment #6)
> > No, I still see the same as before.
> 
> Bummer, but I still think the problem is probably that the pitch of the
> pixmap created in create_pixmap_for_fbcon is getting over-aligned, most
> likely somewhere in EXA. Somebody "just" needs to isolate where and how to
> fix it.
> 
> FWIW, this should work correctly with glamor and current xf86-video-ati Git.

Hmm, yes, it works fine after setting the AccelMethod. Should I just continue using that, with r600?
Comment 9 Michel Dänzer 2015-06-01 07:17:50 UTC 
(In reply to Mantas Mikulėnas from comment #8)
> > FWIW, this should work correctly with glamor and current xf86-video-ati Git.
> 
> Hmm, yes, it works fine after setting the AccelMethod. Should I just
> continue using that, with r600?

Only you can decide which option is better overall for you.
Comment 10 M132 2015-11-07 12:23:43 UTC 
This problem affects me too, and glamor doesn't really fix it, instead of garbage, a black screen is displayed, while it should still display grey GDM background, like on Intel devices for example.
Comment 11 Michel Dänzer 2015-11-09 01:14:51 UTC 
(In reply to M132 from comment #10)
> This problem affects me too, and glamor doesn't really fix it, instead of
> garbage, a black screen is displayed, while it should still display grey GDM
> background, like on Intel devices for example.

Which commit of xf86-video-ati Git did you get that result with?
Comment 13 Michel Dänzer 2019-09-20 15:37:22 UTC 
Assuming this is fixed now.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.