Ubuntu
linux-restricted-modules-2.6.24 package

Xorg crashed with SIGSEGV in free()

Bug #195767 reported by docsnyderchristoph on 2008-02-26

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux-restricted-modules-2.6.24 (Ubuntu)	Expired	Medium	Unassigned

Bug Description

I am using the nvidia-glx drivers
under a ubuntu hardy heron alpha 5 release
for my Nvidia graphics card (nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300])
in a dell lattitude d620 laptop
with the driver "nv" set in the /etc/X11/Xorg.conf file for the device module. this works, but of couse without any desktop efffects.

Changing this driver option (as switching from the nvidia-glx driver to the nvidia-glx-new driver) from "nv" to "nvidia" to get the 3d desktop effects, the login window appears correctly, bu after login, the opening of a GDM session fails where the Xserver crashes and restarts after a while.

while everything worked well under ubuntu gutsy gibbon with the driver option "nvidia" and the 3d desktop effects, I get the reported error when using it for hardy heron alpha 5.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Feb 26 13:57:55 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/Xorg
NonfreeKernelModules: nvidia
Package: xserver-xorg-core 2:1.4.1~git20080131-1ubuntu4 [modified: usr/lib/xorg/modules/extensions/libglx.so]
PackageArchitecture: i386
ProcCmdline: /usr/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt9
ProcEnviron:
PATH=/sbin:/bin:/usr/sbin:/usr/bin
LANG=de_DE.UTF-8
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
free () from /lib/tls/i686/cmov/libc.so.6
Xfree ()
?? ()
?? ()
free () from /lib/tls/i686/cmov/libc.so.6
Title: Xorg crashed with SIGSEGV in free()
Uname: Linux 2.6.24-8-generic i686
UserGroups:
SegvAnalysis:
Segfault happened at: 0xb7d0a39c <free+76>: mov 0x4(%eax),%eax
PC (0xb7d0a39c) ok
source "0x4(%eax)" (0x65766c61) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA

See original description

Tags:

Revision history for this message

docsnyderchristoph (docsnyderchristoph) wrote on 2008-02-26:

Dependencies.txt Edit (2.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (719 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (7.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (603 bytes, text/plain; charset="utf-8")
Registers.txt Edit (499 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (588 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (616 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2008-02-26: Symbolic stack trace

Stacktrace.txt (retraced) Edit (7.2 KiB, text/plain)

StacktraceTop:XkbWriteXKBGeometry (file=0x83c07a0, result=0xbfe23bc0, topLevel=0, showImplicit=0,
XkbWriteXKBKeymapForNames (file=0x83c07a0, names=0xbfe26de8, dpy=0x0, xkb=0x8268160,
XkbDDXLoadKeymapByNames (keybd=0x824ef88, names=0xbfe26de8, want=127, need=63,
ProcXkbGetKbdByName (client=0x83bfb78) at ../../xkb/xkb.c:5198
ProcXkbDispatch (client=0x81d3a70) at ../../xkb/xkb.c:6178

Revision history for this message

Apport retracing service (apport) wrote on 2008-02-26: Symbolic threaded stack trace

ThreadStacktrace.txt (retraced) Edit (7.3 KiB, text/plain)

Changed in xorg-server:
importance:	Undecided → Medium

Revision history for this message

Timo Aaltonen (tjaalton) wrote on 2008-02-26:

Please attach your Xorg.0.log and xorg.conf.

Changed in xorg-server:
status:	New → Incomplete

Revision history for this message

docsnyderchristoph (docsnyderchristoph) wrote on 2008-02-27:

xorg.conf - Valid Edit (2.6 KiB, text/plain)

solution found: with the attached xorg.conf, I got a working solution!

the error appears when setting within the "InputDevice" section for the keyboard option "xorg", leaving this option out, the gnome session starts.

**********
* WORKS *
**********
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules"
Option "XkbModel" "latitude"
Option "XkbLayout" "de"
EndSection

**********
* FAILS *
**********
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "latitude"
Option "XkbLayout" "de"
EndSection

nevertheless, the erason for that are unclear to me, I just found it by accident

Revision history for this message

Pyry (pyry) wrote on 2008-02-27:

messages.txt Edit (305.4 KiB, text/plain)

I can confirm this bug happening on my Kubuntu system with Nvidia Geforce FX 5200 card. Just updated today.

I noticed that the crash happens every time the glx module is accessed. I removed all the settings requiring 3d from my startup and got the kde to start properly. But every time I try to start an application that requires glx, the crash happens (example glxgears).

Feb 27 18:46:24 mediacenter kernel: [ 1170.254137] NVRM: API mismatch: the client has the version 169.12, but
Feb 27 18:46:24 mediacenter kernel: [ 1170.254143] NVRM: this kernel module has the version 169.09. Please
Feb 27 18:46:24 mediacenter kernel: [ 1170.254145] NVRM: make sure that this kernel module and all NVIDIA driver
Feb 27 18:46:24 mediacenter kernel: [ 1170.254147] NVRM: components have the same version.

I also tried the keyboard-trick, but that did not have any effect on my machines crashing.

I believe this is related to the recent update in linux-restricted-modules and nvidia-glx.

Revision history for this message

Pyry (pyry) wrote on 2008-02-27:

xorg.conf - Valid Edit (3.6 KiB, text/plain)

Revision history for this message

Pyry (pyry) wrote on 2008-02-27:

Xorg.0.log Edit (26.1 KiB, text/plain)

Revision history for this message

Nick Booker (nmbooker) wrote on 2009-02-21:

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Bryce Harrington (bryce) on 2009-04-07

Changed in linux-restricted-modules-2.6.24 (Ubuntu):
status:	Incomplete → Confirmed

Bryce Harrington (bryce) on 2009-09-02

tags:

added: hardy

Kees Cook (kees) on 2009-09-16

description:

updated

Revision history for this message

bugbot (bugbot) wrote on 2011-04-28:

#10

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 linux-restricted-modules-2.6.24 (Ubuntu):
status:	Confirmed → New
status:	New → Incomplete

Revision history for this message

bugbot (bugbot) wrote on 2011-05-13:

#11

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 linux-restricted-modules-2.6.24 (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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

Ubuntulinux-restricted-modules-2.6.24 package

Xorg crashed with SIGSEGV in free()

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux-restricted-modules-2.6.24 package