| Bug ID | 110862 |
|---|---|
| Summary | Dual-monitors invalid state after turning on |
| Product | DRI |
| Version | XOrg git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | denisgolovan@yandex.ru |
Hi
I experience annoying bug when I turn on my dual-monitor PC after some time=
is
turned off state.
Basically it results in following:
+-----------+
| OK |
| |
+-----------+------------------+
| | |
| | |
| GARBAGE | GARBAGE |
| | |
| +------------------+
| |
| |
+-----------+
X Windows render a small part of screen ("OK" area), everything e=
lse is
garbage, quite often flicking. Changing VT does not help.
Tested under Linux x64 5.1.6 + xorg-server-1.20.5 + amdgpu driver from git.
Hardware: XFX RX580 8GB
Please attach the corresponding Xorg log file and output of xr= andr and dmesg.
Probably best if you attach all of those from a bad and good b= oot each.
Created attachment 14=
4506 [details]
xorg.log after bug occured
Created attachment 14450=
7 [details]
dmesg after bug occured
Created attachment 144508 [details]
xrandr
Created atta=
chment 144509 [details]
xorg log after successful X restart
Created attach=
ment 144511 [details]
dmesg after successfull X restart
| What | Removed | Added |
|---|---|---|
| Attachment #144506 mime type | text/x-log | text/plain |
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | NOTOURBUG |
The xrandr output is probably different in the bad case as wel= l, isn't it? >>From the bad case Xorg log file: [421376.800] (II) AMDGPU(0): Allocate new frame buffer 2160x738 This means Xorg calls into the driver to resize the desktop to 2160x738 (wh= ich explains why that area is OK, whereas the remaining area has undefined contents). This is most likely in turn due to a client (probably some compo= nent of the desktop environment you're using) requesting so via the RandR extens= ion. So it's either a bug in that or in the X server, not in the driver.