Bug 1015891

Hi Andrea

Can you please attach your hwinfo --gfxcard

Thanks
Patrik

Hi Patrik, sure, here it is:

11: PCI 600.0: 0300 VGA compatible controller (VGA)             
  [Created at pci.378]
  Unique ID: vTuk.8amuH9y3gw7
  Parent ID: _Znp.D5WGnMXZEsB
  SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:06:00.0
  SysFS BusID: 0000:06:00.0
  Hardware Class: graphics card
  Model: "ATI Barts PRO [Radeon HD 6850]"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0x6739 "Barts PRO [Radeon HD 6850]"
  SubVendor: pci 0x174b "PC Partner Limited / Sapphire Technology"
  SubDevice: pci 0xe174 
  Driver: "radeon"
  Driver Modules: "drm"
  Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
  Memory Range: 0xfe9e0000-0xfe9fffff (rw,non-prefetchable)
  I/O Ports: 0xe000-0xefff (rw)
  Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
  IRQ: 42 (3095608 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00001002d00006739sv0000174Bsd0000E174bc03sc00i00"
  Driver Info #0:
    Driver Status: radeon is active
    Driver Activation Cmd: "modprobe radeon"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #19 (PCI bridge)

Primary display adapter: #11



If you need anything else, just ask.

Andrea.

Hi, sorry for the delay.

I was able to reproduce this a while ago (on 7850) but when retesting today everything is working fine. Andrea, do you still see the issue?

Hi Patrik, yes alas it is still there.

Usually now it happens almost always only on the left monitor (the one with ID 0) but not every time, there is a 20%-30% chance it happens when I resume from wakeup. So it is sort of random.

To make it happen you have probably to wakeup several times and after a long time (at least one hour). 

If you want/need I can take a picture next time it happens, today it happened once or twice out of 4-5 wakeups, but if you already managed to reproduce it is only a matter of trying until you get it.

I tried to change some settings in the xorg.conf device section, like AccelMethod to EXA and removing some aggressive hardware usage, but no change. 

Do you need some more info, like the X Server version? It is 1.19.3 at the moment. 

Best regards,
  Andrea

Hi Andrea,

Unfortunately Patrik has been unable to work on this for a while, and the bug got lost.

Could you please update us on whether the issue still occurs with the latest Tumbleweed?

Unfortunately, it sounds really hard to reproduce and we may have to send this upstream.
Do you know whether there was a time, or an entire distribution, with which this didn't happen?

Hi Max, right now I have Thumbleweed 20170704 and the bug is still there.
Actually today has happened again, doesn't happen always but very often, exactly as my description on December 2016. Nothing has changed.

As I wrote in the bug report, this started after I switched to Thumbleweed from Leap. The Thumbleweed version at the time was approximately the one in early December 2016, and the bug was not there in Leap 42.1 or 42.2, not sure which one I had at the time, probably 42.2. 

The hardware and X server version 1.19.3 is the same as before.

If you need anything, feel free to ask.

(In reply to Andrea Controzzi from comment #6)
> Hi Max, right now I have Thumbleweed 20170704 and the bug is still there.

Okay, that is *very* old by Tumbleweed standards. We need to know whether it still happens on the most recent TW release, so please use zypper or a GUI tool to update your running system to the most recent TW packages, and then do a full reboot. Please also make sure that the kernel is updated and that you boot into it - it is currently at 4.15. If anything strange happens, or some packages are not updated, please let us know.

As an aside, as a general hint, valid for every software:
It is crucial to keep your system and applications up to date, because software receives security fixes all the time. In Tumbleweed, this happens to be the same as updating to the latest release.


For reference: I've tried to reproduce your issue with the following card, and couldn't reproduce it:

  Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611]

Granted, it's 2 generations newer, so it may never have been a problem with this hardware.


Please update your system and let us know whether the problem still occurs! :)

Hi Max, yes I know I should update it more frequently, I usually do, but in these months I've been so busy with work and personal matters that I could not risk to have to spend all the extra time to fix any new problems I could get from a Thumbleweed update. I was even considering to revert back to Leap to be on the safe side, since right now I lack time to follow a rolling release.

Anyway I took courage and made the update, right now it is 20180215 and so far no big trouble came out (beside a scary problem with KDE, which got solved after a further update). So far the corruption has not happened, but I know from experience that it is random, so it is early.

I'll keep testing, since it is my PC for everyday use it will be pretty intensive, and if I don't get it in a few days I'll mark it as resolved.

Best regards,
  Andrea.

Cool, thank you!

After upgrading to the last tumbleweed version it seems to have disappeared.
I tested many times, after short and long hibernate, and the display corruption never appeared again. 
Unless it suddenly comes back, I call this resolved.

Thank you for testing this and reporting back!