Crash during booting in dixAllocatePrivate()

Bug #359880 reported by stz_comp
6
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

This crash was probably caused by the fact, that I have modified xorg.conf. However, several boots before this crash were OK. Another bug, the matter to modify the xorg.conf, is that by using two monitors, the "fglrx" driver joins both screens also for maximized windows and fullscreen mode contrary to basic opensource driver.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/Xorg
NonfreeKernelModules: fglrx
Package: xserver-xorg-core 2:1.6.0-0ubuntu14 [modified: usr/lib/xorg/modules/extensions/libdri.so 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:
 PATH=(custom, no user)
 LANG=cs_CZ.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 memset () from /lib/libc.so.6
 dixAllocatePrivate ()
 dixLookupPrivate ()
 ?? ()
 SigAbortDDX ()
Title: Xorg crashed with SIGSEGV in memset()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: admin fuse plugdev

[lspci]
00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS780 Host Bridge [1022:9600]
     Subsystem: ASUSTeK Computer Inc. Device [1043:82f1]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility Radeon HD 3450 [1002:95c5]
     Subsystem: ASUSTeK Computer Inc. Device [1043:01f4]

Revision history for this message
stz_comp (stz-comp) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:memset () at ../sysdeps/x86_64/memset.S:674
dixAllocatePrivate (privates=0x27afdb0,
dixLookupPrivate (privates=0xfffffff8f44870d0,
xf86XVLeaveVT (index=<value optimized out>, flags=0)
SigAbortDDX (signo=0)

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
Bryce Harrington (bryce)
tags: added: crash
Changed in xorg-server (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
description: updated
Bryce Harrington (bryce)
visibility: private → public
Timo Aaltonen (tjaalton)
affects: xorg-server (Ubuntu) → fglrx-installer (Ubuntu)
Bryce Harrington (bryce)
summary: - Crash during booting
+ Crash during booting in dixAllocatePrivate()
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package fglrx-installer - 2:8.632-0ubuntu1~bwh~1

---------------
fglrx-installer (2:8.632-0ubuntu1~bwh~1) karmic; urgency=low

  * New upstream release.
    - X segmentation fault no longer occurs after applying reflections or
      rotations on some systems that support Xrandr 1.2 or higher
    - Catalyst Control Center hot plugging a secondary display no longer
      causes screen corruption in clone mode
      (LP: #388601)
    - Monitor are now disabled after removing the secondary display when
      system is in standby
    - Some systems now report CrossFire adapters available during driver
      re-install
    - On some multi-monitor configurations disabling one display no longer
      causes both displays to become disabled
    - X Server does not intermittently fail to start on some multi adapter
      configurations
      (LP: #367045, #360790, #370051)
    - Executing xrandr --prop no longer causes Ubuntu 9.04 X Server to stop
      responding
    - Segmentation fault no longer occurs with X server Xinerama is
      enabled
      (LP: #364497, #355841, #359880)
  * xorg-driver-fglrx.preinst: Switch obsolete
    --print-installation-architecture to --print-architecture.
    (LP: #403316)

 -- Bryce Harrington <email address hidden> Wed, 05 Aug 2009 01:38:39 -0700

Changed in fglrx-installer (Ubuntu):
status: Confirmed → Fix Released
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.