Created [details]
Excerpt of journalctl -b -l | grep radeon
Environment info:
OS: Arch
xf86-video-ati: 1:7.9.0-1
Kernel: 4.11.9-1
Running Gnome on Wayland (the issue happens with Xorg too).
#############
lspci | grep -i radeon:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Thames [Radeon HD 7500M/7600M Series]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Turks HDMI Aud=
io
[Radeon HD 6500/6600 / 6700M Series]
#############
hwinfo --gfxcard
21: PCI 100.0: 0300 VGA compatible controller (VGA)
[Created at pci.378]
Unique ID: VCu0.dkF2+KIVH8C
Parent ID: vSkL.zuRwVyuZRN1
SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: graphics card
Model: "Toshiba America Info Radeon HD 7670M"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0x6840 "Thames [Radeon HD 7500M/7600M Series]"
SubVendor: pci 0x1179 "Toshiba America Info Systems"
SubDevice: pci 0xfb81 "Radeon HD 7670M"
Driver: "radeon"
Driver Modules: "drm"
Memory Range: 0xb0000000-0xbfffffff (ro,non-prefetchable)
Memory Range: 0xc0000000-0xc001ffff (rw,non-prefetchable)
I/O Ports: 0x3000-0x30ff (rw)
Memory Range: 0xc0040000-0xc005ffff (ro,non-prefetchable,disabled)
IRQ: 25 (44749 events)
Module Alias: "pci:v00001002d00006840sv00001179sd0000FB81bc03sc00i00=
"
Driver Info #0:
Driver Status: radeon is active
Driver Activation Cmd: "modprobe radeon"
Config Status: cfg=3Dnew, avail=3Dyes, need=3Dno, active=3Dunknown
Attached to: #18 (PCI bridge)
Primary display adapter: #21
#############
I receive the errors as per the attached logs. I do see them sometimes at b=
oot,
about the time plymouth is about to kick in but most of the time I can
reproduce the issue by giving the GPU some work.
For example, I can trigger the issue by running:
vblank_mode=3D0 glxgears
After 10 to 15 seconds, the screen would then freeze. Then go blank as it w=
as
trying to reset itself then display the screen again before starting another
reset loop. The system is then not responsive unless via SSH, which I then =
use
to restart the display-manager service. Upon restarting it, the screen eith=
er
is full of white noise (can't see anything but noise in it) or it has a fro=
zen
image of what it was there when the lockup happened. The mouse pointer is s=
till
visible and responding.
Looking at other bugs, this could be related to
https://bugs.freedesktop.org/show_bug.c=
gi?id=3D67722 though the GPU is different.
I'm booting with radeon.dpm=3D1. Booting without that option renders the sc=
reen
unusable (h=
ttps://bugzilla.kernel.org/show_bug.cgi?id=3D82431).