[fglrx] atieventsd crashed with SIGSEGV in XextAddDisplay

Bug #201650 reported by charIie
12
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I updated and restarted. Error occurred without doing anything separate from normal startup.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Mar 12 19:22:35 2008
Disassembly: 0xb7ef45c0:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/sbin/atieventsd
NonfreeKernelModules: fglrx
Package: xorg-driver-fglrx 1:7.1.0-8-3+2.6.24.11-12.31
PackageArchitecture: i386
ProcCmdline: /usr/sbin/atieventsd
ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: linux-restricted-modules-2.6.24
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:

Title: atieventsd crashed with SIGSEGV
Uname: Linux 2.6.24-12-generic i686
UserGroups:

Revision history for this message
charIie (bcp5023) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_XAllocIDs () from /usr/lib/libX11.so.6
XQueryBestCursor () from /usr/lib/libX11.so.6
XESetWireToError () from /usr/lib/libX11.so.6
XextAddDisplay (extinfo=0x8076630, dpy=0x8078b58, ext_name=0x806b3c6 "ATIFGLEXTENSION", hooks=0x8074500,
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Charles Marslett (charles-marslett) wrote : Re: atieventsd crashed with SIGSEGV

Very comparable failure on my machine - SCIM seems to be not very functional. It's initialization and "code page" changing code seems to trigger this off.

Revision history for this message
Bryce Harrington (bryce) wrote : Re: atieventsd crashed with SIGSEGV in XextAddDisplay

Charles or charlie, could either of you describe in more detail how this bug gets triggered? You mention something about it relating to SCIM?

There are two other recent bug reports about crashes in atieventsd. While their backtraces differ, I wonder if they might be related: bug 193559 and bug 194249.

Changed in linux-restricted-modules-2.6.24:
status: New → Incomplete
Revision history for this message
charIie (bcp5023) wrote :

For me it occurred after I restarted once an update was complete. Other than that I don't have much knowledge of what caused it.

Revision history for this message
Charles Marslett (charles-marslett) wrote : Re: [Bug 201650] Re: atieventsd crashed with SIGSEGV in XextAddDisplay

Bryce Harrington wrote:
> Charles or charlie, could either of you describe in more detail how this
> bug gets triggered? You mention something about it relating to SCIM?
>
> There are two other recent bug reports about crashes in atieventsd.
> While their backtraces differ, I wonder if they might be related: bug
> 193559 and bug 194249.
>
> ** Summary changed:
>
> - atieventsd crashed with SIGSEGV
> + atieventsd crashed with SIGSEGV in XextAddDisplay
>
> ** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
> Status: New => Incomplete
There were a number of updates installed (probably 25 or more) that were
installed. I have been updating 8.04 periodically (sometimes daily,
sometimes more like weekly, and this was after several days of not
updating).

There were only two obvious things I noticed: the large number of
updates, and the fact that I got an error message and a hang when
shutting down that referred to the SCIM initialization. I do not know
if this was the initial install of SCIM or if previous installs and
updates just did not generate any errors so I had not noticed it.

I was able to get past the problem by reinstalling 8.04 from the CD, and
then I used the Synaptic Package Manager to update all packages,
unchecked all the updates that referred to SCIM, and rebooted (as
requested). I then updated the SCIM packages and all worked well.

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for fglrx bugs, which now includes a process for upstreaming bugs to AMD.

  http://bugs.launchpad.net/ubuntu/+source/fglrx-installer

To transition your bug into the new fglrx-package, we need your help. Please do the following:

 a. Verify the bug occurs in Intrepid.
     (Intrepid ISOs: http://cdimage.ubuntu.com)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Click 'Also affects distribution'
 d. Set 'Source Package Name' to 'fglrx-installer'
 e. Click Continue

Thank you. This will assist us in reviewing and upstreaming your fglrx bug, as appropriate.

[We'll expire the fglrx bugs in l-r-m-* in a month or so.]

Revision history for this message
Charles Marslett (charles-marslett) wrote :

I've let the system not install any updates for a couple of weeks, then blasted them all at once (the only thing that seems to trigger this) and neither an update of 86 or so files nor the version update to Intrepid (1600 or so files) resulted in any such failures, so it may be fixed.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Great.

Changed in linux-restricted-modules-2.6.24:
status: Incomplete → 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.