Created attachment 128278 [details]
journalctl output at the time of a deadlock on F25

> Do you get the same dmesg errors?
> I have Wayland locking up randomly,
> but dmesg stays clean and I can ssh into the machine and reboot.

Pretty much yeah. Attached is the crash I have experienced just now, and the
computer wasn't doing anything other than sitting around on the desktop and
playing music from Rhythmbox... and you can see the usual:

/usr/libexec/gdm-x-session[18145]: radeon: Failed to deallocate virtual address
for buffer:
/usr/libexec/gdm-x-session[18145]: radeon:    size      : 20480 bytes
kernel: radeon 0000:02:00.0: ring 3 stalled for more than 10083msec
kernel: radeon 0000:02:00.0: GPU lockup (current fence id 0x00000000002d46ee
last fence id 0x00000000002d4710 on ring 3)
kernel: radeon 0000:02:00.0: failed to get a new IB (-35)
kernel: [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)
kernel: radeon 0000:02:00.0: failed to get a new IB (-35)
kernel: radeon 0000:02:00.0: failed to get a new IB (-35)
kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Failed to get ib !
kernel: [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)
/usr/libexec/gdm-x-session[18145]: radeon:    va        : 0x1f836000
/usr/libexec/gdm-x-session[18145]: radeon: Failed to deallocate virtual address
for buffer:
/usr/libexec/gdm-x-session[18145]: radeon:    size      : 45056 bytes
/usr/libexec/gdm-x-session[18145]: radeon:    va        : 0x1f4b0000