X session crashes with EQ overflowing

[hardhu]

On my very old laptop, that is equipped with an Ati Mobility Radeon X700, sometimes (and, sadly, I have to use this word, because I found no regularity pattern for the occurrence of this bug) randomly the desktop session locks, that is I can only move the mouse pointer, but I cannot interact anymore with the desktop session. I am forced to login trough ssh from another pc and to restart the laptop.

In Xorg.0.log I found these lines that are, in my opinion, related to the crash:

(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e]
(EE) 1: /usr/bin/X (mieqEnqueue+0x253) [0x5608e5689373]
(EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152]
(EE) 3: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026]
(EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322]
(EE) 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2]
(EE) 6: /usr/bin/X (0x5608e54f3000+0x96ac8) [0x5608e5589ac8]
(EE) 7: /usr/bin/X (0x5608e54f3000+0xbfc92) [0x5608e55b2c92]
(EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e522c9000+0x352f0) [0x7f5e522fe2f0]
(EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f5e523c60b7]
(EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f5e536ada08]
(EE) 11: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f5e536b06cb]
(EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x19c9) [0x7f5e4e3ae9c9]
(EE) 13: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x1c0c) [0x7f5e4e3aec0c]
(EE) 14: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5e4e5b9000+0x26236) [0x7f5e4e5df236]
(EE) 15: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x569b) [0x7f5e4d97869b]
(EE) 16: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x7e8f) [0x7f5e4d97ae8f]
(EE) 17: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x11953) [0x7f5e4d984953]
(EE) 18: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xe770) [0x7f5e4d981770]
(EE) 19: /usr/bin/X (0x5608e54f3000+0x13ca51) [0x5608e562fa51]
(EE) 20: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xf74f) [0x7f5e4d98274f]
(EE) 21: /usr/bin/X (0x5608e54f3000+0x1332a2) [0x5608e56262a2]
(EE) 22: /usr/bin/X (0x5608e54f3000+0x5818f) [0x5608e554b18f]
(EE) 23: /usr/bin/X (0x5608e54f3000+0x5c34b) [0x5608e554f34b]
(EE) 24: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f5e522e9a40]
(EE) 25: /usr/bin/X (_start+0x29) [0x5608e55396c9]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
(EE) [mi] EQ overflow continuing. 100 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152]
(EE) 2: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026]
(EE) 3: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322]
(EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2]
(EE) 5: /usr/bin/X (0x5608e54f3000+0x96ac8) [0x5608e5589ac8]
(EE) 6: /usr/bin/X (0x5608e54f3000+0xbfc92) [0x5608e55b2c92]
(EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e522c9000+0x352f0) [0x7f5e522fe2f0]
(EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f5e523c60b7]
(EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f5e536ada08]
(EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f5e536b06cb]
(EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x19c9) [0x7f5e4e3ae9c9]
(EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x1c0c) [0x7f5e4e3aec0c]
(EE) 13: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5e4e5b9000+0x26236) [0x7f5e4e5df236]
(EE) 14: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x569b) [0x7f5e4d97869b]
(EE) 15: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x7e8f) [0x7f5e4d97ae8f]
(EE) 16: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x11953) [0x7f5e4d984953]
(EE) 17: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xe770) [0x7f5e4d981770]
(EE) 18: /usr/bin/X (0x5608e54f3000+0x13ca51) [0x5608e562fa51]
(EE) 19: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xf74f) [0x7f5e4d98274f]
(EE) 20: /usr/bin/X (0x5608e54f3000+0x1332a2) [0x5608e56262a2]
(EE) 21: /usr/bin/X (0x5608e54f3000+0x5818f) [0x5608e554b18f]
(EE) 22: /usr/bin/X (0x5608e54f3000+0x5c34b) [0x5608e554f34b]
(EE) 23: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f5e522e9a40]
(EE) 24: /usr/bin/X (_start+0x29) [0x5608e55396c9]
(EE)
[ 335.003] [mi] Increasing EQ size to 1024 to prevent dropped events.
[ 335.005] [mi] EQ processing has resumed after 151 dropped events.
[ 335.005] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
[ 377.274] failed to map pixmap: -1
---
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: LXDE
DistUpgraded: 2016-01-08 14:07:17,902 DEBUG enabling apt cron job
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV410/M26 [Mobility Radeon X700] [1002:5653] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Aspire 5024WLMi [1025:0080]
InstallationDate: Installed on 2015-11-26 (45 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer Aspire 5020
Package: xorg 1:7.7+12ubuntu1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic root=UUID=4c854a4e-3c70-4b7b-b86d-841d4387937e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Tags: xenial ubuntu
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.3.0-5-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-01-08 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/19/2005
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.20
dmi.board.name: Aspire 5020
dmi.board.vendor: Acer
dmi.board.version: Rev.A
dmi.chassis.type: 10
dmi.chassis.vendor: N/A
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvrV1.20:bd12/19/2005:svnAcer:pnAspire5020:pvr-1:rvnAcer:rnAspire5020:rvrRev.A:cvnN/A:ct10:cvrN/A:
dmi.product.name: Aspire 5020
dmi.product.version: -1
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.65-3
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sun Jan 10 11:41:29 2016
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Video Bus KEYBOARD, id 7
 input Sleep Button KEYBOARD, id 8
 input AT Translated Set 2 keyboard KEYBOARD, id 9
 input SynPS/2 Synaptics TouchPad TOUCHPAD, id 10
xserver.errors: systemd-logind: failed to get session: PID 956 does not belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.3-2ubuntu2
xserver.video_driver: radeon

[hardhu (qzerty)]

Today the same crash occurred, and this time I found nothing relevant in /var/log/Xorg.0.log, but there is something in syslog:

Dec 30 17:34:44 eaglubuntu kernel: [ 1746.752093] radeon 0000:01:00.0: ring 0 stalled for more than 10496msec
Dec 30 17:34:44 eaglubuntu kernel: [ 1746.752110] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000aca3 last fence id 0x000000000000aca7 on ring 0)
Dec 30 17:34:44 eaglubuntu kernel: [ 1746.943410] Failed to wait GUI idle while programming pipes. Bad things might happen.
Dec 30 17:34:45 eaglubuntu kernel: [ 1746.947896] radeon 0000:01:00.0: Saved 107 dwords of commands on ring 0.
Dec 30 17:34:45 eaglubuntu kernel: [ 1746.947916] radeon 0000:01:00.0: (r300_asic_reset:425) RBBM_STATUS=0x80010140
Dec 30 17:34:45 eaglubuntu kernel: [ 1747.449111] radeon 0000:01:00.0: (r300_asic_reset:444) RBBM_STATUS=0x80010140
Dec 30 17:34:45 eaglubuntu kernel: [ 1747.946237] radeon 0000:01:00.0: (r300_asic_reset:456) RBBM_STATUS=0x00000140
Dec 30 17:34:45 eaglubuntu kernel: [ 1747.946283] radeon 0000:01:00.0: GPU reset succeed
Dec 30 17:34:45 eaglubuntu kernel: [ 1747.946290] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
Dec 30 17:34:45 eaglubuntu kernel: [ 1747.961690] radeon 0000:01:00.0: ffff880076fdec00 unpin not necessary
Dec 30 17:34:46 eaglubuntu kernel: [ 1747.969631] [drm] PCIE GART of 512M enabled (table at 0x00000000C8040000).
Dec 30 17:34:46 eaglubuntu kernel: [ 1747.969648] [drm] radeon: 2 quad pipes, 1 z pipes initialized.
Dec 30 17:34:46 eaglubuntu kernel: [ 1747.969657] radeon 0000:01:00.0: WB enabled
Dec 30 17:34:46 eaglubuntu kernel: [ 1747.969662] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000a8000000 and cpu addr 0xffff880035750000
Dec 30 17:34:46 eaglubuntu kernel: [ 1747.969681] [drm] radeon: ring at 0x00000000A8001000
Dec 30 17:34:46 eaglubuntu kernel: [ 1747.969703] [drm] ring test succeeded in 1 usecs
Dec 30 17:35:37 eaglubuntu systemd[1]: Started Session 2 of user michelasso.
Dec 30 17:35:38 eaglubuntu dbus[550]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
Dec 30 17:35:38 eaglubuntu systemd[1]: Starting Console Manager...
Dec 30 17:35:38 eaglubuntu console-kit-daemon[7064]: (process:7127): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Dec 30 17:35:38 eaglubuntu console-kit-daemon[7064]: missing action
Dec 30 17:35:38 eaglubuntu dbus[550]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Dec 30 17:35:38 eaglubuntu systemd[1]: Started Console Manager.
Dec 30 17:35:38 eaglubuntu console-kit-daemon[7064]: (process:7131): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Dec 30 17:35:38 eaglubuntu console-kit-daemon[7064]: missing action
Dec 30 17:36:13 eaglubuntu dhclient: PRC: Renewing lease on enp6s7.
Dec 30 17:36:13 eaglubuntu dhclient: XMT: Renew on enp6s7, interval 10260ms.
Dec 30 17:36:13 eaglubuntu dhclient: RCV: Reply message on enp6s7 from fe80::ea94:f6ff:fed4:4622.
Dec 30 17:36:14 eaglubuntu NetworkManager[530]: <info> valid_lft -1
Dec 30 17:36:14 eaglubuntu NetworkManager[530]: <info> preferred_lft -1
...

[hardhu (qzerty)]

On my very old laptop, that is equipped with an Ati Mobility Radeon
X700, sometimes (and, sadly, I have to use this word, because I found no
regularity pattern for the occurrence of this bug) randomly the desktop
session locks, that is I can only move the mouse pointer, but I cannot
interact anymore with the desktop session. I am forced to login trough
ssh from another pc and to restart the laptop.

In Xorg.0.log I found these lines that are, in my opinion, related to
the crash:

(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e]
(EE) 1: /usr/bin/X (mieqEnqueue+0x253) [0x5608e5689373]
(EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152]
(EE) 3: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026]
(EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322]
(EE) 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2]
(EE) 6: /usr/bin/X (0x5608e54f3000+0x96ac8) [0x5608e5589ac8]
(EE) 7: /usr/bin/X (0x5608e54f3000+0xbfc92) [0x5608e55b2c92]
(EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e522c9000+0x352f0) [0x7f5e522fe2f0]
(EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f5e523c60b7]
(EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f5e536ada08]
(EE) 11: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f5e536b06cb]
(EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x19c9) [0x7f5e4e3ae9c9]
(EE) 13: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x1c0c) [0x7f5e4e3aec0c]
(EE) 14: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5e4e5b9000+0x26236) [0x7f5e4e5df236]
(EE) 15: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x569b) [0x7f5e4d97869b]
(EE) 16: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x7e8f) [0x7f5e4d97ae8f]
(EE) 17: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x11953) [0x7f5e4d984953]
(EE) 18: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xe770) [0x7f5e4d981770]
(EE) 19: /usr/bin/X (0x5608e54f3000+0x13ca51) [0x5608e562fa51]
(EE) 20: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xf74f) [0x7f5e4d98274f]
(EE) 21: /usr/bin/X (0x5608e54f3000+0x1332a2) [0x5608e56262a2]
(EE) 22: /usr/bin/X (0x5608e54f3000+0x5818f) [0x5608e554b18f]
(EE) 23: /usr/bin/X (0x5608e54f3000+0x5c34b) [0x5608e554f34b]
(EE) 24: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f5e522e9a40]
(EE) 25: /usr/bin/X (_start+0x29) [0x5608e55396c9]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
(EE) [mi] EQ overflow continuing. 100 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e]
(EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152]
(EE) 2: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026]
(EE) 3: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322]
(EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2]
(EE) 5: /usr/bin/X (0x5608e54f3000+0x96ac8) [...

[Michel Dänzer (michel-daenzer)]

Created attachment 120853
drm/radeon: Always use indirect access for CRTC(2)_GEN_CNTL registers

Does this kernel patch help by any chance?

[Ernst Persson (ernstp)]

Since powerplay I'm getting something with this backtrace on AMDGPU also, in bug 92996

[Michel Dänzer (michel-daenzer)]

(In reply to Ernst Sjöstrand from comment #2)
> Since powerplay I'm getting something with this backtrace on AMDGPU also, in
> bug 92996

Not related. The event queue (EQ) overflowing is a generic symptom which can be triggered by many different causes.

[hardhu (qzerty)]

(In reply to Michel Dänzer from comment #1)
> Created attachment 120853 [details] [review]
> drm/radeon: Always use indirect access for CRTC(2)_GEN_CNTL registers
>
> Does this kernel patch help by any chance?

I tried to apply this patch to ubuntu sources (I am using Lubuntu) 4.2.0, but I get the following error:
-------------------------------------------------------------------------------
michelasso@eaglubuntu:~/linux-4.2.0$ sudo patch -p1 < ../Downloads/0001-drm-radeon-Always-use-indirect-access-for-CRTC-2-_GE.patch
patching file drivers/gpu/drm/radeon/r100.c
patching file drivers/gpu/drm/radeon/radeon_bios.c
Hunk #1 succeeded at 512 (offset 1 line).
Hunk #2 succeeded at 522 (offset 1 line).
Hunk #3 succeeded at 539 (offset 1 line).
Hunk #4 succeeded at 567 (offset 1 line).
patching file drivers/gpu/drm/radeon/radeon_device.c
patching file drivers/gpu/drm/radeon/radeon_legacy_crtc.c
Hunk #2 succeeded at 324 with fuzz 1.
Hunk #3 FAILED at 339.
1 out of 8 hunks FAILED -- saving rejects to file drivers/gpu/drm/radeon/radeon_legacy_crtc.c.rej
patching file drivers/gpu/drm/radeon/radeon_legacy_encoders.c
----------------------------------------------------------------------------
However, I tried the same to build the kernel packages, and I installed them, but then my desktop is screwed as you can see in this picture:

http://s18.postimg.org/p7mi9r4ux/P_20160108_104254.jpg

[hardhu (qzerty)]

In the meanwhile, I moved to xenial (development release) Lubuntu, that uses kernel 4.3.x, I'll let you know if there are improvements.

[hardhu (qzerty)]

Yesterday, after upgrading to Xenial, I had an entire day without the problem, but today immediately after booting my notebook, the desktop freezed and I couldn't even move the mouse pointer. I could however login trough ssh, and I got the same errors in dmesg/syslog:
----------------------------------------------------------------------------
[ 2447.428051] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000082 last fence id 0x00000000000000a7 on ring 0)
[ 2447.928094] radeon 0000:01:00.0: ring 0 stalled for more than 1815000msec
[ 2447.928110] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000082 last fence id 0x00000000000000a9 on ring 0)
[ 2448.502826] Failed to wait GUI idle while programming pipes. Bad things might happen.
[ 2448.507130] radeon 0000:01:00.0: Saved 1291 dwords of commands on ring 0.
[ 2448.507152] radeon 0000:01:00.0: (r300_asic_reset:425) RBBM_STATUS=0x80010140
[ 2449.008199] radeon 0000:01:00.0: (r300_asic_reset:444) RBBM_STATUS=0x80010140
[ 2449.505214] radeon 0000:01:00.0: (r300_asic_reset:456) RBBM_STATUS=0x00000140
[ 2449.505254] radeon 0000:01:00.0: GPU reset succeed
[ 2449.505260] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[ 2449.512770] radeon 0000:01:00.0: ffff880035b62c00 unpin not necessary
[ 2449.521545] [drm] PCIE GART of 512M enabled (table at 0x00000000C8040000).
[ 2449.521562] [drm] radeon: 2 quad pipes, 1 z pipes initialized.
[ 2449.521571] radeon 0000:01:00.0: WB enabled
[ 2449.521577] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000a8000000 and cpu addr 0xffff880035213000
[ 2449.521595] [drm] radeon: ring at 0x00000000A8001000
[ 2449.521617] [drm] ring test succeeded in 1 usecs
[ 2640.100118] INFO: task Xorg:705 blocked for more than 120 seconds.
[ 2640.100132] Not tainted 4.3.0-5-generic #16-Ubuntu
[ 2640.100137] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2640.100142] Xorg D ffff88007fc169c0 0 705 692 0x00400006
[ 2640.100154] ffff88007907f9b8 0000000000000086 ffffffff81e13500 ffff88007bdd3fc0
[ 2640.100162] ffff880079080000 ffff88007907fb08 ffff88003560c000 ffff88007907faa0
[ 2640.100169] ffff88003560d490 ffff88007907f9d0 ffffffff817f7a23 7fffffffffffffff
[ 2640.100176] Call Trace:
[ 2640.100194] [<ffffffff817f7a23>] schedule+0x33/0x80
[ 2640.100204] [<ffffffff817faae9>] schedule_timeout+0x189/0x250
[ 2640.100309] [<ffffffffc01ff1a8>] ? radeon_sa_bo_new+0x78/0x480 [radeon]
[ 2640.100364] [<ffffffffc01940c2>] ? radeon_fence_process+0x12/0x30 [radeon]
[ 2640.100418] [<ffffffffc019438c>] radeon_fence_wait_seq_timeout.constprop.8+0x22c/0x300 [radeon]
[ 2640.100428] [<ffffffff810946b9>] ? __queue_delayed_work+0x89/0x190
[ 2640.100436] [<ffffffff810bf480>] ? wake_atomic_t_function+0x60/0x60
[ 2640.100490] [<ffffffffc019473f>] radeon_fence_wait+0x9f/0xe0 [radeon]
[ 2640.100555] [<ffffffffc01b8039>] r100_ib_test+0x179/0x290 [radeon]
[ 2640.100626] [<ffffffffc0253a28>] radeon_ib_ring_tests+0x58/0xc0 [radeon]
[ 2640.100675] [<ffffffffc017ae2a>] radeon_gpu_reset+0x23a/0x330 [radeon]
[ 2640.100736] [<ffffffffc01aa2ce>] radeon_gem_handle_lockup.part.3+0xe/0x20 [radeon]
[ 2640....

[penalvch (penalvch)]

hardhu, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal as it will automatically gather and attach updated debug information to this report:
apport-collect -p xorg 1529932

Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

apport information

[hardhu (qzerty)]

I ran the apport-collect command as suggested, but it is not clear to me if I have to execute it:
a) every time I turn on my notebook and boot in Lubuntu
b) only after a crash occurs.
In the meanwhile, since I think this is a bug related to radeon kernel module, I upgraded to Xenial to see if something changes with newer kernels, but with no luck so far: the problem still occurs 50% of the times I boot in Lubuntu.

[penalvch (penalvch)]

hardhu, to advise, you don't need to run apport-collect any further.

To clarify, which version of Ubuntu were you using when this issue was first encountered?

[hardhu (qzerty)]

First time occurred in Lubuntu 15.10 (Wily), but it occurred again in Xenial with the same characteristics.
For your reference, i reported the same bug also to xorg developers here:

https://bugs.freedesktop.org/show_bug.cgi?id=93610

[penalvch (penalvch)]

hardhu, to clarify, is the xorg crash preceded by a kernel call trace?

Also, after the xorg crash, is there a crash file in /var/crash?

[Michel Dänzer (michel-daenzer)]

(In reply to qzerty from comment #4)
> However, I tried the same to build the kernel packages, and I installed
> them, but then my desktop is screwed as you can see in this picture:

Please attach the actual patch you ended up using for the build.

[hardhu (qzerty)]

Sorry for the late reply, I haven't had a crash for five days until today, so I couldn't properly reply to your questions.
This mornig crash however has been a little different, since the monitor flashed two times going black, but then the graphical session resumed correctly, I am typing right now from Firefox.
In /var/log/Xorg.0.log I have nothing relevant, but in dmesg I have the following lines (I don't know if they are related to a kernel call trace):

[ 6243.620093] radeon 0000:01:00.0: ring 0 stalled for more than 10332msec
[ 6243.620109] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000745 last fence id 0x0000000000000746 on ring 0)
[ 6243.806159] Failed to wait GUI idle while programming pipes. Bad things might happen.
[ 6243.809265] radeon 0000:01:00.0: Saved 43 dwords of commands on ring 0.
[ 6243.809284] radeon 0000:01:00.0: (r300_asic_reset:425) RBBM_STATUS=0x80010140
[ 6244.310399] radeon 0000:01:00.0: (r300_asic_reset:444) RBBM_STATUS=0x80010140
[ 6244.807516] radeon 0000:01:00.0: (r300_asic_reset:456) RBBM_STATUS=0x00000140
[ 6244.807556] radeon 0000:01:00.0: GPU reset succeed
[ 6244.807562] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[ 6244.822004] radeon 0000:01:00.0: ffff880035b85400 unpin not necessary

So this time it seems that GPU reset succeeded fine. I don't have nothing in /var/crash related to what happened.
I am glad to provide more details to discover a possible call trace if you suggest me how to do.

[hardhu (qzerty)]

Could you explain me how to to identify what you refer to the "actual patch"? I am not so accustomed to kernel patching, I just followed this guidelines https://www.kernel.org/doc/Documentation/applying-patches.txt
with Ubuntu kernel sources 4.2.0
I will retry however using 4.3.0 sources as soon as possible.

[Michel Dänzer (michel-daenzer)]

(In reply to qzerty from comment #8)
> Could you explain me how to to identify what you refer to the "actual
> patch"?

The actual changes you ended up building the kernel with. E.g. make a copy of the kernel tree before applying the patch, then after applying the patch create a diff using

 diff -ru <copy of kernel tree> <kernel tree> >actual-changes.diff

[hardhu (qzerty)]

Created attachment 121230
File describing changes to kernel tree

[hardhu (qzerty)]

Ok, I have tried to apply the patch to Ubuntu kernel tree 4.3.0, but the error I get is the same as above. I attach the actual-changes.diff

[Martin-peres-n (martin-peres-n)]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/150.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end of standard support in April 2021:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 16.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm