Xorg crashed with SIGSEGV in miPointerGetScreen() via CloseDownDevices()

Bug #357536 reported by Jan David Mol
40
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Expired
High
Unassigned

Bug Description

Saw the crash dialog box after starting X (intel driver), just after upgrading it (Jaunty).

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/Xorg
Package: xserver-xorg-core 2:1.6.0-0ubuntu11
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #40-Ubuntu SMP Fri Apr 3 17:39:41 UTC 2009
Signal: 11
SourcePackage: xorg-server
Title: Xorg crashed with SIGSEGV in <signal handler called>()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups:

Stacktrace:
#0 0x00000000004347fa in dixLookupPrivate (privates=0x198, key=0x7da700)
    at ../../dix/privates.c:79
#1 0x00000000004dafd6 in miPointerGetScreen (pDev=0x4b33930)
    at ../../mi/mipointer.c:485
#2 0x0000000000495f38 in xf86PostKeyboardEvent (device=0x4bd5010,
    key_code=235, is_down=1) at ../../../../hw/xfree86/common/xf86Xinput.c:923
 pointer = (DeviceIntPtr) 0x4b33930
#3 0x00007f398018ac35 in EvdevReadInput (pInfo=0x4ba32f0)
    at ../../src/evdev.c:256
 ev = {time = {tv_sec = 1239169974, tv_usec = 603647}, type = 1,
  code = 227, value = 1}
 value = 1
 dx = 0
 dy = 0
 abs = 0
 button = 0
 pEvdev = (EvdevPtr) 0x4bd6db0
#4 0x0000000000485be5 in xf86SigioReadInput (fd=<value optimized out>,
    closure=0x4ba32f0) at ../../../../hw/xfree86/common/xf86Events.c:311
 errno_save = 32
 sigstate = 1
#5 0x0000000000476f77 in xf86SIGIO (sig=<value optimized out>)
    at ../../../../../hw/xfree86/os-support/linux/../shared/sigio.c:114
 i = 4
 ready = {fds_bits = {131072, 0 <repeats 15 times>}}
 to = {tv_sec = 0, tv_usec = 0}
 save_errno = 32
 r = 1
#6 <signal handler called>
#7 SmartScheduleTimer (sig=14) at ../../os/utils.c:1244
#8 <signal handler called>
#9 0x00007f399320c270 in __sigprocmask (how=<value optimized out>,
    set=0x7dbae0, oset=0x0)
    at ../sysdeps/unix/sysv/linux/ia64/sigprocmask.c:43
#10 0x0000000000447079 in CloseDownDevices () at ../../dix/devices.c:913
 dev = (DeviceIntPtr) 0x0
 next = (DeviceIntPtr) 0x4bcf8a0
#11 0x0000000000433ddb in main (argc=10, argv=0x7fff9d6dca48,
    envp=<value optimized out>) at ../../dix/main.c:421
 alwaysCheckForInput = {0, 1}

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07)
     Subsystem: Dell Device [1028:024d]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
     Subsystem: Dell Device [1028:024d]

Revision history for this message
Jan David Mol (jjdmol) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:SmartScheduleTimer (sig=14) at ../../os/utils.c:1244
<signal handler called>
__sigprocmask (how=<value optimized out>,
CloseDownDevices () at ../../dix/devices.c:913
main (argc=10, argv=0x7fff9d6dca48,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Jan David Mol (jjdmol)
visibility: private → public
Revision history for this message
Jan David Mol (jjdmol) wrote : Re: Xorg crashed with SIGSEGV in <signal handler called>()

This could be a dupe of bug #328937 by the way. If so, this one provides a better traceback.

Bryce Harrington (bryce)
summary: - Xorg crashed with SIGSEGV in <signal handler called>()
+ Xorg crashed with SIGSEGV in miPointerGetScreen() via CloseDownDevices()
description: updated
Bryce Harrington (bryce)
Changed in xorg-server (Ubuntu):
importance: Medium → High
status: New → Triaged
Bryce Harrington (bryce)
description: updated
Bryce Harrington (bryce)
tags: added: jaunty
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Jan,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 357536

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 357536 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/357536

Changed in xorg-server (Ubuntu):
status: Triaged → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Bryce Harrington (bryce) 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 xorg-server (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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