Segmentation Fault in nvidiaAddDrawableHandler

I have seen a couple segmentation faults this week with the same call stack.

  • nvidia-driver-440
  • Ubuntu 18.04, Gnome
  • Ryzen 3900X
  • 2080TI
  • Gigabyte X570 AORUS ULTRA

The forum does not let me to upload nvidia-bug-report.log.gz.

Nothing special about when it happens:

  • Browsers, dev tools and maybe some video running.
  • Xorg crashes and returns me to a log-in screen.

thanks.
Duncan

/usr/lib/gdm3/gdm-x-session[2809]: (EE)

/usr/lib/gdm3/gdm-x-session[2809]: (EE) Caught signal 7 (Bus error). Server aborting

/usr/lib/gdm3/gdm-x-session[2809]: FatalError re-entered, aborting

/usr/lib/gdm3/gdm-x-session[2809]: (EE)

/usr/lib/gdm3/gdm-x-session[2809]: (EE) Bus error at address 0x0

/usr/lib/gdm3/gdm-x-session[2809]: (EE)

/usr/lib/gdm3/gdm-x-session[2809]: (EE) 2: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x4569ec) [0x7f97cf757cd8]

/usr/lib/gdm3/gdm-x-session[2809]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f97d22988df]

/usr/lib/gdm3/gdm-x-session[2809]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x562714d387d9]

/usr/lib/gdm3/gdm-x-session[2809]: (EE) Backtrace:

/usr/lib/gdm3/gdm-x-session[2809]: (EE)

/usr/lib/gdm3/gdm-x-session[2809]: (EE)

/usr/lib/gdm3/gdm-x-session[2809]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.

/usr/lib/gdm3/gdm-x-session[2809]: for help.

/usr/lib/gdm3/gdm-x-session[2809]: #011 at http://wiki.x.org

/usr/lib/gdm3/gdm-x-session[2809]: Please consult the The X.Org Foundation support

/usr/lib/gdm3/gdm-x-session[2809]: (EE)

/usr/lib/gdm3/gdm-x-session[2809]: (EE)

/usr/lib/gdm3/gdm-x-session[2809]: (EE) Caught signal 11 (Segmentation fault). Server aborting

/usr/lib/gdm3/gdm-x-session[2809]: Fatal server error:

/usr/lib/gdm3/gdm-x-session[2809]: (EE)

/usr/lib/gdm3/gdm-x-session[2809]: (EE) Segmentation fault at address 0x8

/usr/lib/gdm3/gdm-x-session[2809]: (EE)

/usr/lib/gdm3/gdm-x-session[2809]: (EE) 2: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x456a00) [0x7f97cf757d00]

/usr/lib/gdm3/gdm-x-session[2809]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f97d22988df]

/usr/lib/gdm3/gdm-x-session[2809]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x562714d387d9]

/usr/lib/gdm3/gdm-x-session[2809]: (EE) Backtrace:

/usr/lib/gdm3/gdm-x-session[2809]: (EE)

Maybe this:
https://forums.developer.nvidia.com/t/random-xid-61-and-xorg-lock-up/79731/185
Ryzen 3rd gen + Nvidia Turing
To upload the bug-report, just remove the .gz ending.

Thanks - here is the bug report.

nvidia-bug-report.log (607.8 KB)

Maybe this: Xid 61 hang

I do see the xid 61 hang too. This has different symptoms - Xorg crash instead of pegging a cpu and no mention of Xid 61 in syslog. It would be great if they had the same cause and could be fixed in one go but nothing much to suggest that yet.

Seems something completely different, no XIDs involved, the nvidia DDX seems to just be crashing out of nowhere.
You’re currently running the 440.82 driver, did this also happen with previous drivers?

I can’t confirm past drivers - I may have had one or two xorg crashes that I didn’t diagnose.

This is the first time it has happened twice in a few days and I can confirm it’s the same segmentation fault both times.

I’ve been getting this exact error a couple of times a week. The latest trace seems to indicate that it was caused by chromium…

  • nvidia-driver-440.100

  • Pop!_OS 20.04 LTS

  • Gnome 3.36.3

  • Thinkpad X1 Extreme / GeForce GTX 1650

    Jul 16 13:07:25 x1 chromium.desktop[753051]: [753051:753051:0716/130725.958998:ERROR:gles2_cmd_decoder.cc(17411)] Offscreen context lost via ARB/EXT_robustness. Reset status = GL_UNKNOWN_C>
    Jul 16 13:07:25 x1 chromium.desktop[753051]: [753051:753051:0716/130725.959100:ERROR:gles2_cmd_decoder.cc(4851)] GLES2DecoderImpl: Context reset detected after MakeCurrent.
    Jul 16 13:07:25 x1 chromium.desktop[753051]: [753051:753051:0716/130725.959322:ERROR:gpu_service_impl.cc(1146)] Exiting GPU process because some drivers can’t recover from errors. GPU proc>
    Jul 16 13:07:26 x1 chromium.desktop[1237665]: [1237665:1237665:0716/130726.017553:ERROR:vaapi_wrapper.cc(480)] vaInitialize failed: unknown libva error
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE)
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) Backtrace:
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55b78e17fdec]
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f568767341f]
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) 2: /usr/lib/x86_64-linux-gnu/nvidia-440/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x456d8c) [0x7f5686e275b8]
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE)
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) Bus error at address 0x0
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE)
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: Fatal server error:
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) Caught signal 7 (Bus error). Server aborting
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE)
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE)
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: Please consult the The X.Org Foundation support
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: at http://wiki.x.org
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: for help.
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) Please also check the log file at “/var/log/Xorg.1.log” for additional information.
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE)
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE)
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) Backtrace:
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55b78e17fdec]
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f568767341f]
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) 2: /usr/lib/x86_64-linux-gnu/nvidia-440/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x456da0) [0x7f5686e275e0]
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE)
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) Segmentation fault at address 0x8
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE)
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: FatalError re-entered, aborting
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE) Caught signal 11 (Segmentation fault). Server aborting
    Jul 16 13:07:26 x1 /usr/lib/gdm3/gdm-x-session[1960]: (EE)
    Jul 16 13:07:26 x1 chromium.desktop[753010]: [753010:753010:0716/130726.160062:ERROR:chrome_browser_main_extra_parts_x11.cc(62)] X IO error received (X server probably went away)

I also see some chromium correlation. I just had another segmentation fault at precisely the moment I closed an Electron window.

A few minutes before the fault, I had this from vscode, another Electron application:

Jul 19 22:51:23 shinpan code.desktop[2403]: [2469:0719/225123.692225:ERROR:gles2_cmd_decoder.cc(18682)] [.RendererMainThread-0x3346323d7500]GL ERROR :GL_INVALID_OPERATION : DoEndSharedImageAccessCHROMIUM: shared image is not being accessed

The fault itself:

Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE)
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]:  for help.
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: #011 at http://wiki.x.org
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: Please consult the The X.Org Foundation support
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE)
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE)
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE) Caught signal 11 (Segmentation fault). Server aborting
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: Fatal server error:
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE)
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE) Segmentation fault at address 0x100000008
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE)
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE) 2: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x456da0) [0x7ff52f0715e0]
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (?+0x0) [0x7ff531bb288f]
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE) 0: /usr/lib/xorg/Xorg (?+0x0) [0x5575ef8dea50]
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE) Backtrace:
Jul 19 22:59:20 shinpan /usr/lib/gdm3/gdm-x-session[4216]: (EE)

Aug 1 17:35:07 shinpan /usr/lib/gdm3/gdm-x-session[2471]: (EE) 2: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x456d8c) [0x7fa734e415b8]
Aug 1 17:35:07 shinpan /usr/lib/gdm3/gdm-x-session[2471]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fa7379828ef]
Aug 1 17:35:07 shinpan /usr/lib/gdm3/gdm-x-session[2471]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55ee719adc29]
Aug 1 17:35:07 shinpan /usr/lib/gdm3/gdm-x-session[2471]: (EE) Backtrace:

I have the exact same error! The problem seems to only happen when I plug in a mouse after waking my computer. I’m running a Dell laptop with Quadro T1000 Mobile graphics and the 440 drivers. I’m on Ubuntu 20.04 Gnome.

Noticed that it also happens when closing chrome windows. Will try to switch to firefox and keep everyone updated.

Below are debugging traces in case it helps anyone

From syslog:
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE)
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE) Backtrace:
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x564f122ebe0c]
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f230676141f]
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE) 2: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x456da0) [0x7f2305f145e0]
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE)
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE) Segmentation fault at address 0x0
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE)
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: Fatal server error:
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE) Caught signal 11 (Segmentation fault). Server aborting
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE)
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE)
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: Please consult the The X.Org Foundation support
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: #011 at http://wiki.x.org
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: for help.
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE) Please also check the log file at “/var/log/Xorg.1.log” for additional information.
Jul 30 22:19:38 7Kettles /usr/lib/gdm3/gdm-x-session[1831]: (EE)

From Xorg Log:
[ 73910.326] (II) event8 - Logitech Wireless Mouse: is tagged by udev as: Mouse
[ 73910.326] (II) event8 - Logitech Wireless Mouse: device is a pointer
[ 73910.326] (II) event8 - Logitech Wireless Mouse: device removed
[ 73910.383] () Option “config_info” “udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:046D:C534.0007/0003:046D:4054.0008/input/input37/event8”
[ 73910.383] (II) XINPUT: Adding extended input device “Logitech Wireless Mouse” (type: MOUSE, id 12)
[ 73910.385] (
) Option “AccelerationScheme” “none”
[ 73910.386] () Logitech Wireless Mouse: (accel) selected scheme none/0
[ 73910.386] (
) Logitech Wireless Mouse: (accel) acceleration factor: 2.000
[ 73910.387] (**) Logitech Wireless Mouse: (accel) acceleration threshold: 4
[ 73910.391] (II) event8 - Logitech Wireless Mouse: is tagged by udev as: Mouse
[ 73910.391] (II) event8 - Logitech Wireless Mouse: device is a pointer
[ 73948.513] (EE)
[ 73948.513] (EE) Backtrace:
[ 73948.514] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5621c0591e0c]
[ 73948.514] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f6bff72d41f]
[ 73948.515] (EE) 2: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x456d8c) [0x7f6bfeedf5b8]
[ 73948.515] (EE)
[ 73948.515] (EE) Segmentation fault at address 0xac
[ 73948.515] (EE)

-Koby

I have the exact same error!

  • nvidia-driver-440.100
  • Pop!_OS 20.04 LTS
  • Gnome 3.36.3
  • Thinkpad X1 Extreme / GeForce GTX 1050 Ti


[ 28571.334] (II) event5 - SynPS/2 Synaptics TouchPad: SYN_DROPPED event - some input events have been lost.
[ 28654.552] () Option “fd” “51”
[ 28654.552] (II) event2 - Power Button: device removed
[ 28654.553] (
) Option “fd” “91”
[ 28654.553] (II) event4 - Video Bus: device removed
[ 28654.553] () Option “fd” “93”
[ 28654.553] (II) event0 - Sleep Button: device removed
[ 28654.554] (
) Option “fd” “53”
[ 28654.554] (II) event10 - Integrated IR Camera: Integrate: device removed
[ 28654.554] () Option “fd” “96”
[ 28654.554] (II) event9 - Integrated Camera: Integrated C: device removed
[ 28654.554] (
) Option “fd” “46”
[ 28654.554] (II) event3 - AT Translated Set 2 keyboard: device removed
[ 28654.555] () Option “fd” “92”
[ 28654.555] (II) event5 - SynPS/2 Synaptics TouchPad: device removed
[ 28654.555] (
) Option “fd” “94”
[ 28654.555] (II) event8 - TPPS/2 Elan TrackPoint: device removed
[ 28654.555] () Option “fd” “90”
[ 28654.555] (II) event13 - ThinkPad Extra Buttons: device removed
[ 28654.556] (
) Option “fd” “97”
[ 28654.556] (II) event17 - WH-XB900N (AVRCP): device removed
[ 28657.914] (II) systemd-logind: got pause for 13:71
[ 28657.914] (II) systemd-logind: got pause for 13:73
[ 28657.914] (II) systemd-logind: got pause for 13:67
[ 28657.914] (II) systemd-logind: got pause for 13:81
[ 28657.914] (II) systemd-logind: got pause for 13:66
[ 28657.914] (II) systemd-logind: got pause for 13:70
[ 28657.914] (II) systemd-logind: got pause for 13:74
[ 28657.914] (II) systemd-logind: got pause for 13:77
[ 28657.914] (II) systemd-logind: got pause for 13:68
[ 28657.914] (II) systemd-logind: got pause for 13:69
[ 28657.914] (II) systemd-logind: got pause for 13:64
[ 28657.914] (II) systemd-logind: got pause for 13:72
[ 28664.771] (II) systemd-logind: got resume for 13:71
[ 28664.771] (–) NVIDIA(GPU-0): DFP-0: disconnected
[ 28664.771] (–) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[ 28664.771] (–) NVIDIA(GPU-0): DFP-0: 1440.0 MHz maximum pixel clock
[ 28664.771] (–) NVIDIA(GPU-0):
[ 28664.771] (–) NVIDIA(GPU-0): DFP-1: disconnected
[ 28664.772] (–) NVIDIA(GPU-0): DFP-1: Internal DisplayPort
[ 28664.772] (–) NVIDIA(GPU-0): DFP-1: 1440.0 MHz maximum pixel clock
[ 28664.772] (–) NVIDIA(GPU-0):
[ 28664.772] (–) NVIDIA(GPU-0): DFP-2: disconnected
[ 28664.772] (–) NVIDIA(GPU-0): DFP-2: Internal TMDS
[ 28664.772] (–) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 28664.772] (–) NVIDIA(GPU-0):
[ 28664.773] (–) NVIDIA(GPU-0): AU Optronics Corporation (DFP-3): connected
[ 28664.773] (–) NVIDIA(GPU-0): AU Optronics Corporation (DFP-3): Internal DisplayPort
[ 28664.773] (–) NVIDIA(GPU-0): AU Optronics Corporation (DFP-3): 1440.0 MHz maximum pixel clock
[ 28664.773] (–) NVIDIA(GPU-0):
[ 28664.838] (II) NVIDIA(0): Setting mode “DFP-3:nvidia-auto-select”
[ 28668.134] (II) config/udev: removing device WH-XB900N (AVRCP)
[ 28668.135] (II) UnloadModule: “libinput”
[ 28668.135] (II) systemd-logind: releasing fd for 13:81
[ 28668.135] (EE) systemd-logind: failed to release device: Device not taken
[ 28668.680] (II) libinput: TPPS/2 Elan TrackPoint: SetProperty on 340 called but device is disabled.
This driver cannot change properties on a disabled device
[ 28668.680] (II) libinput: TPPS/2 Elan TrackPoint: SetProperty on 328 called but device is disabled.
This driver cannot change properties on a disabled device
[ 28668.681] (II) libinput: TPPS/2 Elan TrackPoint: SetProperty on 342 called but device is disabled.
This driver cannot change properties on a disabled device
[ 28672.804] (II) systemd-logind: got resume for 13:73
[ 28672.805] (II) event9 - Integrated Camera: Integrated C: is tagged by udev as: Keyboard
[ 28672.805] (II) event9 - Integrated Camera: Integrated C: device is a keyboard
[ 28672.806] (II) systemd-logind: got resume for 13:67
[ 28672.807] (II) event3 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[ 28672.807] (II) event3 - AT Translated Set 2 keyboard: device is a keyboard
[ 28672.808] (II) systemd-logind: got resume for 13:66
[ 28672.808] (II) event2 - Power Button: is tagged by udev as: Keyboard
[ 28672.808] (II) event2 - Power Button: device is a keyboard
[ 28672.809] (II) systemd-logind: got resume for 13:70
[ 28672.810] (II) systemd-logind: got resume for 13:74
[ 28672.814] (II) event10 - Integrated IR Camera: Integrate: is tagged by udev as: Keyboard
[ 28672.814] (II) event10 - Integrated IR Camera: Integrate: device is a keyboard
[ 28672.815] (II) systemd-logind: got resume for 13:77
[ 28672.818] (II) event13 - ThinkPad Extra Buttons: is tagged by udev as: Keyboard Switch
[ 28672.818] (II) event13 - ThinkPad Extra Buttons: device is a keyboard
[ 28672.819] (II) systemd-logind: got resume for 13:68
[ 28672.822] (II) event4 - Video Bus: is tagged by udev as: Keyboard
[ 28672.822] (II) event4 - Video Bus: device is a keyboard
[ 28672.823] (II) systemd-logind: got resume for 13:69
[ 28672.825] (II) event5 - SynPS/2 Synaptics TouchPad: is tagged by udev as: Touchpad
[ 28672.826] (II) event5 - SynPS/2 Synaptics TouchPad: device is a touchpad
[ 28672.827] (II) systemd-logind: got resume for 13:64
[ 28672.828] (II) event0 - Sleep Button: is tagged by udev as: Keyboard
[ 28672.828] (II) event0 - Sleep Button: device is a keyboard
[ 28672.829] (II) systemd-logind: got resume for 13:72
[ 28672.830] (II) event8 - TPPS/2 Elan TrackPoint: is tagged by udev as: Mouse Pointingstick
[ 28672.830] (II) event8 - TPPS/2 Elan TrackPoint: device is a pointer
[ 28725.819] (EE)
[ 28725.819] (EE) Backtrace:
[ 28725.821] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55e5e36e1e0c]
[ 28725.822] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f99e8d0641f]
[ 28725.823] (EE) 2: /usr/lib/x86_64-linux-gnu/nvidia-440/xorg/nvidia_drv.so (?+0x0) [0x7f99e805e82c]
[ 28725.823] (EE)
[ 28725.823] (EE) Segmentation fault at address 0xab
[ 28725.823] (EE)
Fatal server error:
[ 28725.823] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 28725.823] (EE)
[ 28725.823] (EE)

And again:

Aug 13 14:57:05 shinpan /usr/lib/gdm3/gdm-x-session[2409]: (EE) Segmentation fault at address 0x8
Aug 13 14:57:05 shinpan /usr/lib/gdm3/gdm-x-session[2409]: (EE)
Aug 13 14:57:05 shinpan /usr/lib/gdm3/gdm-x-session[2409]: (EE) 2: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x456da0) [0x7f00a11ad5e0]
Aug 13 14:57:05 shinpan /usr/lib/gdm3/gdm-x-session[2409]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f00a3cee8ef]
Aug 13 14:57:05 shinpan /usr/lib/gdm3/gdm-x-session[2409]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x561757d3bc29]
Aug 13 14:57:05 shinpan /usr/lib/gdm3/gdm-x-session[2409]: (EE) Backtrace:
Aug 13 14:57:05 shinpan /usr/lib/gdm3/gdm-x-session[2409]: (EE)

1 Like

@ahuillet what can we do to get this issue some attention please?

1 Like

Hi Dawdaw,
We will try to reproduce issue locally and will start debugging from there.
Do you have reliable repro steps to recreate issue ?

Sadly it’s pretty random but I’ve noticed it often seems coincident with an interaction Electron based applications (which use Chromium for rendering) e.g. closing VS Code.

I’ll try scripting some application churn and see if that provokes it.

That will really help a lot but I would try few things on my own which other users tried to recreate issue.

It’s often happens to me when i just close apps: Slack, Chrome, etc.

1 Like

I ran this for about an hour but it didn’t trigger the issue. I’ll run it for longer when I get a chance:

while true
do
    code .

    sleep 2s

    xdotool key ctrl+w

    sleep 1s

    xdotool key ctrl+w
done

Hello.
I can indeed confirm this is also happening for me with apps using electron. (eg. Discord chat client)
App freezes for a bit and whole X crashes. (can relogin and will work).

[357429.212] (EE) Backtrace:
[357429.212] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5584761e52c9]
[357429.213] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fc6ef18c77f]
[357429.213] (EE) 2: /usr/lib/xorg/modules/drivers/nvidia_drv.so (nvidiaAddDrawableHandler+0x456a00) [0x7fc6ee34fd00]
[357429.213] (EE)
[357429.213] (EE) Segmentation fault at address 0x8
[357429.213] (EE)
Fatal server error:
[357429.213] (EE) Caught signal 11 (Segmentation fault). Server aborting

System: Clevo P370SM3 with two GTX 780M’s

1 Like

Please try with latest driver release and share results…

I have been having the same problem.

@amrits I just tried driver release 450.80.02 and still observe frequent crashes with the same stack trace. Here are my steps to reproduce. From the other descriptions, it seems like these could be simpler but these steps seem to reproduce the bug repeatedly.

  1. Use multiple display devices. I have a Quadro P2000 driving three displays. I can reproduce the driver bug using a bare bones Xorg configuration containing only a device section that specifies the nvidia driver as the driver to use. Only one “X screen” is created.
  2. Launch a multi-window OpenGL accelerated application.
  3. Make a window on each display expand to full-screen.
  4. Interact with each window for a while and try to close the application.
  5. Repeat 2-4.

I believe the most important point is that multiple GLX contexts exist and I think it matters that their associated drawables are on different displays. In my case, I see the bug almost every time after I extend the windows to full-screen. I have seen this bug across machines CentOS 7, Ubuntu 20.04 with Xorg 1.19.5 and Xorg 1.20.8 and many different driver versions (390.87 - 450.80.02).

FWIW this bug has been reported multiple other times (in case there is valuable information there):