About once in a week the X server is crashing at a system with a GeForce GT 520 due to segmentation fault. In /var/log/Xorg.0.log I find: [1281400.737] (EE) [1281400.737] (EE) Backtrace: [1281400.806] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x34) [0x5954f4] [1281400.806] (EE) 1: /usr/bin/Xorg (0x400000+0x1992f9) [0x5992f9] [1281400.806] (EE) 2: /lib64/libpthread.so.0 (0x7f307c787000+0x10460) [0x7f307c797460] [1281400.819] (EE) 3: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (0x7f307a275000+0x10cf8) [0x7f307a285cf8] [1281400.819] (EE) 4: /usr/lib64/xorg/modules/libshadowfb.so (0x7f30795ad000+0x3f5a) [0x7f30795b0f5a] [1281400.819] (EE) 5: /usr/bin/Xorg (0x400000+0x36f43) [0x436f43] [1281400.819] (EE) 6: /usr/bin/Xorg (0x400000+0x3aee1) [0x43aee1] [1281400.819] (EE) 7: /usr/bin/Xorg (0x400000+0x29b14) [0x429b14] [1281400.819] (EE) 8: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7f307b41f4bd] [1281400.819] (EE) 9: /usr/bin/Xorg (0x400000+0x29e5d) [0x429e5d] [1281400.819] (EE) [1281400.834] (EE) Segmentation fault at address 0x7f30795b50d4 [1281400.834] Fatal server error: [1281400.835] Caught signal 11 (Segmentation fault). Server aborting [1281400.835] [1281400.835] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [1281400.835] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [1281400.835] (EE) [1281400.848] (II) evdev: Power Button: Close [1281400.856] (II) UnloadModule: "evdev" [1281400.872] (II) evdev: Power Button: Close [1281400.872] (II) UnloadModule: "evdev" [1281400.888] (II) evdev: Microsoft Wired Keyboard 600: Close [1281400.888] (II) UnloadModule: "evdev" [1281400.904] (II) evdev: Microsoft Wired Keyboard 600: Close [1281400.904] (II) UnloadModule: "evdev" [1281400.922] (II) evdev: Microsoft Wired Keyboard 600: Close [1281400.922] (II) UnloadModule: "evdev" [1281400.938] (II) evdev: HID 046a:0023: Close [1281400.938] (II) UnloadModule: "evdev" [1281400.954] (II) evdev: HID 046a:0023: Close [1281400.954] (II) UnloadModule: "evdev" [1281400.970] (II) evdev: Logitech USB-PS/2 Optical Mouse: Close [1281400.970] (II) UnloadModule: "evdev" [1281400.971] (II) NOUVEAU(0): NVLeaveVT is called. [1281401.009] Server terminated with error (1). Closing log file. root@leopard:/usr/src(18)# lspci -v -s 01:00.0 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 83c1 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at fa000000 (32-bit, non-prefetchable) [size=16M] Memory at f0000000 (64-bit, prefetchable) [size=128M] Memory at f8000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at fb000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 <?> Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: nouveau
> 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1) (prog-if 00 [VGA controller]) > /usr/lib64/xorg/modules/libshadowfb.so It is my understanding that there are still unsolved issues with GF119 and that is also why acceleration is disabled (nouveau uses shadowfb instead of EXA). Probably reporting this upstream at https://bugs.freedesktop.org/ is a good idea. If you can get a stack trace through gdb this would be even better (see http://www.x.org/wiki/Development/Documentation/ServerDebugging ) but if the crash happens only once a week this might not be feasible.
Hi Chí-Thanh Christopher, I just started a debugging session with Xorg as described in http://www.x.org/wiki/Development/Documentation/ServerDebugging . I hope, a xserver crash will happen in the next days.
I also created a bug report at https://bugs.freedesktop.org/show_bug.cgi?id=55832
xf86-video-nouveau-1.0.3 was added to the tree containing the fix mentioned in the upstream bug. Please test.
Please reopen if you still see this issue after upgrading to 1.0.3.
