Xorg crashed with SIGSEGV in xf86CursorSetCursor()

Bug #363665 reported by Bastien Scher
10
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-180 (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I tried to play Crayon Physics Deluxe Demo with PlayOnLinux, but my screen freezed. So I used tty to kill the game, and when I returned to Xorg I saw my desktop for 1/2 second before X crashes and restarts.

This sometimes happens, even without PlayOnLinux. And to go to ttys with Ctrl+Alt+Fx, I always have to try twice : I go to the tty, then it returns to Xorg, I go back to tty and it works.
Also, I have to use Framebuffer to use ttys.

These bugs have begun to happen since Intrepid.

P.S : Sorry if i made mistakes, English isn't my native language.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/Xorg
NonfreeKernelModules: nvidia
Package: xserver-xorg-core 2:1.6.0-0ubuntu14 [modified: usr/lib/xorg/modules/extensions/libglx.so]
ProcAttrCurrent: unconfined
ProcCmdline: /usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_GB:en
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@rothera) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:38:53 UTC 2009
Signal: 11
SourcePackage: xorg-server
Stacktrace:
 #0 0x080f9f84 in ?? ()
 #1 0x080fa366 in ?? ()
 #2 0xb68bea37 in ?? () from /usr/lib/xorg/modules/drivers//nvidia_drv.so
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/xorg/modules/drivers//nvidia_drv.so
ThreadStacktrace:
 .
 Thread 1 (process 3618):
 #0 0x080f9f84 in ?? ()
 #1 0x080fa366 in ?? ()
 #2 0xb68bea37 in ?? () from /usr/lib/xorg/modules/drivers//nvidia_drv.so
Title: Xorg crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic i686
UserGroups:

Xrandr:

[lspci]
00:00.0 RAM memory [0500]: nVidia Corporation MCP78S [GeForce 8200] Memory Controller [10de:0754] (rev a2)
     Subsystem: Hewlett-Packard Company Device [103c:360a]
02:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8200M G [10de:0845] (rev a2)
     Subsystem: Hewlett-Packard Company Device [103c:360a]

Revision history for this message
Bastien Scher (bastien0705) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:xf86CursorSetCursor (pDev=0x8e0c720, pScreen=0x8caf720,
xf86CursorEnableDisableFBAccess (index=0, enable=1)
?? () from /usr/lib/xorg/modules/drivers//nvidia_drv.so

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Bryce Harrington (bryce)
tags: added: crash
Changed in xorg-server (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
description: updated
Bryce Harrington (bryce)
summary: - Xorg crashed with SIGSEGV
+ Xorg crashed with SIGSEGV in xf86CursorSetCursor()
Revision history for this message
PaulH (huffton) wrote :

I can reliably reproduce this bug playing railroad tycoon II in wine. It always happens when it wants to play a video at the start of a scenario. Note that while I do use Nvidia drivers like the original reporter, I also reproduced this bug using the nv driver, so can reproduce using an open source stack. I am running Jaunty (9.04). I did not get the problem on 8.04. (I did not install 8.10 due to the legacy nvidia driver issue). I have tested Fedora 10, and it works fine.

I am willing to put some effort into debugging this, but need some guidance. What should I try?

Revision history for this message
PaulH (huffton) wrote :

Here is the stack trace using the nv driver from the Xorg.0.log.old:
===
Backtrace:
0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x813518b]
1: /usr/X11R6/bin/X(xf86SigHandler+0x55) [0x80c7be5]
2: [0xb7ee9400]
3: /usr/X11R6/bin/X [0x80fa366]
4: /usr/lib/xorg/modules/drivers//nv_drv.so [0xb77ec5ac]
5: /usr/X11R6/bin/X [0x80e1b5b]
6: /usr/X11R6/bin/X [0x80e1d0a]
7: /usr/X11R6/bin/X(RRCrtcSet+0x13c) [0x816439c]
8: /usr/X11R6/bin/X(ProcRRSetScreenConfig+0x4e3) [0x8169e93]
9: /usr/X11R6/bin/X [0x8161fc5]
10: /usr/X11R6/bin/X(Dispatch+0x33f) [0x808d57f]
11: /usr/X11R6/bin/X(main+0x3bd) [0x80722ed]
12: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7ab6775]
13: /usr/X11R6/bin/X [0x80717a1]
Saw signal 11. Server aborting.
===

Bryce Harrington (bryce)
tags: added: jaunty
Bryce Harrington (bryce)
affects: xorg-server (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu)
Revision history for this message
PaulH (huffton) wrote :

Bryce

I note this has been moved from xorg-server to nvidia-graphics-drivers-180.

Did you notice that I have reproduced the issue using the nv driver (See my previous 2 updates)? It would seem unlikely to me that the same bug is present in both drivers, so I am not sure that this is a driver issue.

Please let me know if there is anything I can do to help debug this.

Cheers

PaulH

Revision history for this message
Alen (cshadow) wrote :

Have the same problem on ubuntu Karmic. It happens often when switching users, like I described here:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/502237

Program received signal SIGSEGV, Segmentation fault.
0x080f95fc in xf86CursorSetCursor (pDev=0xa33d258, pScreen=0xa1c7458, pCurs=0xa90a190, x=1, y=0)
    at ../../../../hw/xfree86/ramdac/xf86Cursor.c:324
324 ../../../../hw/xfree86/ramdac/xf86Cursor.c: No such file or directory.
 in ../../../../hw/xfree86/ramdac/xf86Cursor.c
(gdb) bt f
#0 0x080f95fc in xf86CursorSetCursor (pDev=0xa33d258, pScreen=0xa1c7458, pCurs=0xa90a190, x=1,
    y=0) at ../../../../hw/xfree86/ramdac/xf86Cursor.c:324
        ScreenPriv = 0xa1d5e18
        infoPtr = 0xa1c81a8
#1 0x080f99f0 in xf86CursorEnableDisableFBAccess (index=1, enable=1)
    at ../../../../hw/xfree86/ramdac/xf86Cursor.c:230
        pDev = 0xa33d258
        pScreen = 0xa1c7458
        ScreenPriv = <value optimized out>
#2 0xb5f985f7 in ?? () from /usr/lib/xorg/modules/drivers//nvidia_drv.so
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Revision history for this message
bugbot (bugbot) wrote :

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Confirmed → New
status: New → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → Expired
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.