Ubuntu
xorg-server package

[Karmic] Xorg crashed with SIGSEGV during gdm login

Bug #456814 reported by Simon Déziel on 2009-10-21

This bug report is a duplicate of: Bug #458697: [Karmic] Xorg crashed with SIGSEGV during gdm login with high resolutions. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xorg-server (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

When I tried to login my Gnome session the screen froze (no progress) after I entered my password (correctly).

After that the login screen came back and I logged in as normally (though my resolution was incorrect).

lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10

apt-cache policy xserver-xorg-core
xserver-xorg-core:
  Installed: 2:1.6.4-2ubuntu3
  Candidate: 2:1.6.4-2ubuntu3
  Version table:
*** 2:1.6.4-2ubuntu3 0
        500 http://ch.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

apt-cache policy xserver-xorg
xserver-xorg:
  Installed: 1:7.4+3ubuntu5
  Candidate: 1:7.4+3ubuntu5
  Version table:
*** 1:7.4+3ubuntu5 0
        500 http://ch.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
Date: Tue Oct 20 19:34:58 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xorg
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Compaq Deskpro
Package: xserver-xorg-core 2:1.6.4-2ubuntu3
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-14-generic-pae root=/dev/mapper/VG0-ROOT ro quiet splash
ProcCmdline: /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-fZjOz6/database -nolisten tcp
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
RelatedPackageVersions:
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-xorg-video-intel 2:2.9.0-1ubuntu2
xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SegvAnalysis:
Segfault happened at: 0x8122afc: movzwl 0x12(%edx),%esi
PC (0x08122afc) ok
source "0x12(%edx)" (0x00000029) not located in a known VMA region (needed readable region)!
destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
?? ()
?? ()
?? ()
?? () from /usr/lib/xorg/modules/drivers//intel_drv.so
?? ()
Title: Xorg crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic-pae i686
UserGroups:

XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 09/13/2002
dmi.bios.vendor: Compaq
dmi.bios.version: 686P2 v3.14
dmi.board.name: 0688h
dmi.board.vendor: Compaq
dmi.chassis.asset.tag: 6049FHGZN126
dmi.chassis.type: 15
dmi.chassis.vendor: Compaq
dmi.modalias: dmi:bvnCompaq:bvr686P2v3.14:bd09/13/2002:svnCompaq:pnDeskpro:pvr:rvnCompaq:rn0688h:rvr:cvnCompaq:ct15:cvr:
dmi.product.name: Deskpro
dmi.sys.vendor: Compaq
fglrx: Not loaded
system:
distro: Ubuntu
architecture: i686kernel: 2.6.31-14-generic-pae

See original description

Tags:

Revision history for this message

Simon Déziel (sdeziel) wrote on 2009-10-21:

BootDmesg.txt Edit (30.9 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (525 bytes, text/plain; charset="utf-8")
GdmLog.txt Edit (22.1 KiB, text/plain; charset="utf-8")
GdmLogOld.txt Edit (36.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (5.2 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (736 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (411 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1021 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (12.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (699 bytes, text/plain; charset="utf-8")
Registers.txt Edit (477 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (640 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (666 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (65.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (141.2 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (28.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (42.9 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (938 bytes, text/plain; charset="utf-8")
glxinfo.txt Edit (5.4 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (265 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (6.0 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (56.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-10-21: Stacktrace.txt (retraced)

Stacktrace.txt (retraced) Edit (768 bytes, text/plain)

StacktraceTop:?? ()
?? ()
?? ()
I810BlockHandler (i=0, blockData=0x0, pTimeout=0xbffe109c,
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2009-10-21: ThreadStacktrace.txt (retraced)

ThreadStacktrace.txt (retraced) Edit (795 bytes, text/plain)

Changed in xorg-server (Ubuntu):
status:	New → Invalid

Revision history for this message

Apport retracing service (apport) wrote on 2009-10-21: Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

xserver-xorg: installed version 1:7.4+3ubuntu5, latest version: 1:7.4+3ubuntu7
tzdata: installed version 2009n-2, latest version: 2009o-1
libselinux1: installed version 2.0.85-2ubuntu1, latest version: 2.0.85-2ubuntu2
xserver-xorg-input-all: installed version 1:7.4+3ubuntu5, latest version: 1:7.4+3ubuntu7
xserver-xorg-video-all: installed version 1:7.4+3ubuntu5, latest version: 1:7.4+3ubuntu7
x11-common: installed version 1:7.4+3ubuntu5, latest version: 1:7.4+3ubuntu7
base-files: installed version 5.0.0ubuntu6, latest version: 5.0.0ubuntu7

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags:

removed: need-i386-retrace

Simon Déziel (sdeziel) on 2009-10-21

visibility:	private → public
summary:	- Xorg crashed with SIGSEGV + Xorg crashed with SIGSEGV during login on Karmic
summary:	- Xorg crashed with SIGSEGV during login on Karmic + [Karmic] Xorg crashed with SIGSEGV during gdm login

Revision history for this message

Simon Déziel (sdeziel) wrote on 2009-10-21:

I don't know if it's related but I have a cheap KVM that makes the screen detection fail *only when I'm not toggled* at the computer when the screen detection occurs.

When I booted my computer my KVM was toggled to my other computer. That has make Xorg use the wrong resolution (800x600). When I toggled back to my Karmic computer I saw the resolution problem and I hit Alt-SysRq-K to restart Xorg. Xorg restarted properly *and* the resolution OK (as it normally is 1600x1200 or so).

After that I logged myself and while my session was loading, it froze (no progression) for a few seconds and GDM login screen came back after. I was then able to login properly even if the screen resolution was again at 800x600.

Simon Déziel (sdeziel) on 2009-10-21

description:

updated

Revision history for this message

Simon Déziel (sdeziel) wrote on 2009-10-21:

I'm still have the issue using

apt-cache policy xserver-xorg
xserver-xorg:
  Installed: 1:7.4+3ubuntu7
  Candidate: 1:7.4+3ubuntu7
  Version table:
*** 1:7.4+3ubuntu7 0
        500 http://ch.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

It's now worst because I'm now unable to login with GDM. When I enter my password my session starts to load but the screen goes black with small green vertical lines and I switch temporarily to the console (Alt-F1) and see those errors :

[ 57.477288] mtrr: base(0x44000000) is not aligned on a size(0x3aa000) boundary
[ 57.631701] [drm] Using v1.4 init.
[ 60.812018] [drm:drm_reclaim_locked_buffers] *ERROR* reclaim_buffers_locked() deadlock. Please rework this
[ 60.812027] driver to use reclaim_buffers_idlelocked() instead.
[ 60.812032] I will go on reclaiming the buffers anyway.
[ 94.560032] [drm:i810_wait_ring] *ERROR* space: 65520 wanted 65528
[ 94.560101] [drm:i810_wait_ring] *ERROR* lockup

Revision history for this message

Simon Déziel (sdeziel) wrote on 2009-10-21:

When I took a look at /var/log/kern.log, I found this :

Oct 20 19:23:31 srv kernel: [ 19.211607] [drm] Initialized drm 1.1.0 20060810
Oct 20 19:23:31 srv kernel: [ 19.244320] alloc irq_desc for 16 on node -1
Oct 20 19:23:31 srv kernel: [ 19.244334] alloc kstat_irqs on node -1
Oct 20 19:23:31 srv kernel: [ 19.244357] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Oct 20 19:23:31 srv kernel: [ 19.244372] pci 0000:00:02.0: setting latency timer to 64
Oct 20 19:23:31 srv kernel: [ 19.245106] [drm] Initialized i810 1.4.0 20030605 for 0000:00:02.0 on minor 0
Oct 20 19:23:31 srv kernel: [ 19.258611] mtrr: base(0x44000000) is not aligned on a size(0x12c000) boundary
Oct 20 19:23:32 srv kernel: [ 19.509338] [drm] Using v1.4 init.
Oct 20 19:23:35 srv kernel: [ 22.784019] [drm:drm_reclaim_locked_buffers] *ERROR* reclaim_buffers_locked() deadlock. Please rework this
Oct 20 19:23:35 srv kernel: [ 22.784029] driver to use reclaim_buffers_idlelocked() instead.
Oct 20 19:23:35 srv kernel: [ 22.784034] I will go on reclaiming the buffers anyway.

This is the error message related to my comment #5.

Revision history for this message

Simon Déziel (sdeziel) wrote on 2009-10-21:

When the screen resolution is wrong (low : 800x600) at login screen I can login but I still have those errors :

Oct 20 22:48:37 srv kernel: [ 18.679978] [drm] Initialized drm 1.1.0 20060810
Oct 20 22:48:37 srv kernel: [ 18.705632] alloc irq_desc for 16 on node -1
Oct 20 22:48:37 srv kernel: [ 18.705646] alloc kstat_irqs on node -1
Oct 20 22:48:37 srv kernel: [ 18.705672] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Oct 20 22:48:37 srv kernel: [ 18.705687] pci 0000:00:02.0: setting latency timer to 64
Oct 20 22:48:37 srv kernel: [ 18.706503] [drm] Initialized i810 1.4.0 20030605 for 0000:00:02.0 on minor 0
Oct 20 22:48:37 srv kernel: [ 18.715087] mtrr: base(0x44000000) is not aligned on a size(0x12c000) boundary
Oct 20 22:48:37 srv kernel: [ 18.755769] ppdev: user-space parallel port driver
Oct 20 22:48:37 srv kernel: [ 18.957959] [drm] Using v1.4 init.
Oct 20 22:48:40 srv kernel: [ 22.276025] [drm:drm_reclaim_locked_buffers] *ERROR* reclaim_buffers_locked() deadlock. Please rework this
Oct 20 22:48:40 srv kernel: [ 22.276038] driver to use reclaim_buffers_idlelocked() instead.
Oct 20 22:48:40 srv kernel: [ 22.276043] I will go on reclaiming the buffers anyway.
Oct 20 22:48:43 srv kernel: [ 25.068070] eth0: no IPv6 routers present
Oct 20 22:52:13 srv kernel: [ 234.784021] [drm:drm_reclaim_locked_buffers] *ERROR* reclaim_buffers_locked() deadlock. Please rework this
Oct 20 22:52:13 srv kernel: [ 234.784035] driver to use reclaim_buffers_idlelocked() instead.
Oct 20 22:52:13 srv kernel: [ 234.784039] I will go on reclaiming the buffers anyway.
Oct 20 22:52:13 srv kernel: [ 234.842895] [drm] DMA Cleanup
Oct 20 22:52:13 srv kernel: [ 234.924240] mtrr: no MTRR for 44000000,3000000 found
Oct 20 22:52:14 srv kernel: [ 236.095500] mtrr: base(0x44000000) is not aligned on a size(0x3aa000) boundary
Oct 20 22:52:14 srv kernel: [ 236.251441] [drm] Using v1.4 init.
Oct 20 22:52:18 srv kernel: [ 239.432019] [drm:drm_reclaim_locked_buffers] *ERROR* reclaim_buffers_locked() deadlock. Please rework this
Oct 20 22:52:18 srv kernel: [ 239.432031] driver to use reclaim_buffers_idlelocked() instead.
Oct 20 22:52:18 srv kernel: [ 239.432036] I will go on reclaiming the buffers anyway.

That differs from when I *can't* login and get [drm:i810_wait_ring] *ERROR*.

When the screen resolution is wrong (low : 800x600) at login screen I can login but I still have those errors :

Oct 20 22:48:37 srv kernel: [   18.679978] [drm] Initialized drm 1.1.0 20060810
Oct 20 22:48:37 srv kernel: [   18.705632]   alloc irq_desc for 16 on node -1
Oct 20 22:48:37 srv kernel: [   18.705646]   alloc kstat_irqs on node -1
Oct 20 22:48:37 srv kernel: [   18.705672] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Oct 20 22:48:37 srv kernel: [   18.705687] pci 0000:00:02.0: setting latency timer to 64
Oct 20 22:48:37 srv kernel: [   18.706503] [drm] Initialized i810 1.4.0 20030605 for 0000:00:02.0 on minor 0
Oct 20 22:48:37 srv kernel: [   18.715087] mtrr: base(0x44000000) is not aligned on a size(0x12c000) boundary
Oct 20 22:48:37 srv kernel: [   18.755769] ppdev: user-space parallel port driver
Oct 20 22:48:37 srv kernel: [   18.957959] [drm] Using v1.4 init.
Oct 20 22:48:40 srv kernel: [   22.276025] [drm:drm_reclaim_locked_buffers] *ERROR* reclaim_buffers_locked() deadlock. Please rework this
Oct 20 22:48:40 srv kernel: [   22.276038]      driver to use reclaim_buffers_idlelocked() instead.
Oct 20 22:48:40 srv kernel: [   22.276043]      I will go on reclaiming the buffers anyway.
Oct 20 22:48:43 srv kernel: [   25.068070] eth0: no IPv6 routers present
Oct 20 22:52:13 srv kernel: [  234.784021] [drm:drm_reclaim_locked_buffers] *ERROR* reclaim_buffers_locked() deadlock. Please rework this
Oct 20 22:52:13 srv kernel: [  234.784035]      driver to use reclaim_buffers_idlelocked() instead.
Oct 20 22:52:13 srv kernel: [  234.784039]      I will go on reclaiming the buffers anyway.
Oct 20 22:52:13 srv kernel: [  234.842895] [drm] DMA Cleanup
Oct 20 22:52:13 srv kernel: [  234.924240] mtrr: no MTRR for 44000000,3000000 found
Oct 20 22:52:14 srv kernel: [  236.095500] mtrr: base(0x44000000) is not aligned on a size(0x3aa000) boundary
Oct 20 22:52:14 srv kernel: [  236.251441] [drm] Using v1.4 init.
Oct 20 22:52:18 srv kernel: [  239.432019] [drm:drm_reclaim_locked_buffers] *ERROR* reclaim_buffers_locked() deadlock. Please rework this
Oct 20 22:52:18 srv kernel: [  239.432031]      driver to use reclaim_buffers_idlelocked() instead.
Oct 20 22:52:18 srv kernel: [  239.432036]      I will go on reclaiming the buffers anyway.

That differs from when I *can't* login and get [drm:i810_wait_ring] *ERROR*.

Revision history for this message

Simon Déziel (sdeziel) wrote on 2009-10-21:

The problem also happens when I use the linux-image-generic (not PAE).

Revision history for this message

Simon Déziel (sdeziel) wrote on 2009-10-22:

#10

Today during login I had a kernel panic. I'm still unable to log in and I have the same errors.

Changed in xorg-server (Ubuntu):
status:	Invalid → New

Bryce Harrington (bryce) on 2009-10-22

tags:	added: crash
Changed in xorg-server (Ubuntu):
status:	New → Confirmed

Revision history for this message

Simon Déziel (sdeziel) wrote on 2009-10-23:

#11

Just to make it clear, I no longer use my KVM because it is buggy. So the bug #458697 was reproduced with 2 different monitors connected directly to the computer.