Segmentation fault crocus_dri.so (X server dies)

Bug #1989964 reported by Simon IJskes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mesa
New
Unknown
mesa (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The desktop session is running for 0 or more days. Suddenly the X server dies, and login screen reappears.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Sep 16 14:45:54 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:18e4]
MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=/dev/mapper/sun--vg-root ro
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2015
dmi.bios.release: 2.59
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.59
dmi.board.name: 18E4
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP EliteDesk 800 G1 TWR
dmi.product.sku: C8N27AV
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
Simon IJskes (sim-nyx) wrote :
Revision history for this message
Simon IJskes (sim-nyx) wrote :

[335842.604] (WW) glamor: Failed to allocate 128x88 FBO due to GL_OUT_OF_MEMORY.
[335842.604] (WW) glamor: Expect reduced performance.
[335844.555] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glMapBuffer(map failed)

followed by

[335844.561] (EE) glamor0: GL error: GL_INVALID_OPERATION in glUnmapBuffer(buffer is not mapped)

It looks like a failed allocation is not detected, and an illegal unmap follows.

From a distant it looks like an application is exhausting the Xserver memory, en the Xserver is not robust enough to report these problems to the application program and stay unaffected.

When it is followed by a segmentation error later it sure looks like memory corruption, due to not detecting the failure return from glMapBuffer.

Revision history for this message
Simon IJskes (sim-nyx) wrote :

is this read/followed by upstream? or should i find upstream myself to report it?

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Upstream does not follow downstream bugs, no.

That said, I don't know how to avoid this issue though. But you could file it upstream at

https://gitlab.freedesktop.org/mesa/mesa/-/issues

and see what happens. Let us know the bug# too.

Changed in mesa (Ubuntu):
status: New → Confirmed
Revision history for this message
Simon IJskes (sim-nyx) wrote :
Revision history for this message
Simon IJskes (sim-nyx) wrote :

also on libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1

Revision history for this message
Oibaf (oibaf) wrote :

Simon, Ubuntu 22.04 now has mesa 23.0.4-0ubuntu1~22.04.1, can you try it, is this still an issue for you?

Revision history for this message
Simon IJskes (sim-nyx) wrote :

@oibaf, read your request. unfort i just started rebuilding my profile from scratch. i'm in the process of re-adding all the applets, and other X stuff. will keep you posted.

Changed in mesa:
status: Unknown → New
Revision history for this message
Simon IJskes (sim-nyx) wrote :
Download full text (3.2 KiB)

The problem still exists:

 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE)
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) Backtrace:
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 0: /usr/lib/xorg/Xorg (?+0x0) [0x5614c77b0939]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7faa02b2d520]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7faa02c8baf7]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa0040eed2]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa0094570f]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa00f1cbc3]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa0046337b]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa0043568f]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa004390c9]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa0043f899]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 10: /usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7faa0236ea53]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 11: /usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7faa0235daa1]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 12: /usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7faa02368233]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 13: /usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7faa0236871e]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 14: /usr/lib/xorg/Xorg (?+0x0) [0x5614c771d890]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 15: /usr/lib/xorg/Xorg (?+0x0) [0x5614c7713b33]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 16: /usr/lib/xorg/Xorg (?+0x0) [0x5614c763a4c5]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 17: /usr/lib/xorg/Xorg (?+0x0) [0x5614c763e544]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7faa02b14d90]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7faa02b14e40]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 20: /usr/lib/xorg/Xorg (?+0x0) [0x5614c7627605]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE)
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) Segmentation fault at address 0x20
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE)
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: Fatal server error:
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) Caught signal 11 (S...

Read more...

Revision history for this message
Simon IJskes (sim-nyx) wrote :

libgl1-mesa-dri:amd64 23.0.4-0ubuntu1~22.04.1

Revision history for this message
Oibaf (oibaf) wrote :

If you can try a newer mesa snapshot you can find it in this PPA: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.