Xorg crashed with SIGSEGV in hwlIconUpload()

[W. Prins]

Ubuntu release: 8.10 Beta
Version of package: xorg 1:7.4~5ubuntu2

Tried to enable FGLRX driver again after an apparent update today (noticed fglrx package being updated by the update manager). However it still failed (X fails to start and finally boots into failsafe X), and this is the crash report as a result. This bug report is therefore related to/a dupliate of #286140.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/Xorg
NonfreeKernelModules: fglrx
Package: xserver-xorg-core 2:1.5.2-2ubuntu1 [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=/sbin:/bin:/usr/sbin:/usr/bin
 LANG=en_GB.UTF-8
ProcVersion: Linux version 2.6.27-7-generic (buildd@vernadsky) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu10) ) #1 SMP Wed Oct 22 00:29:18 UTC 2008

Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 hwlIconUpload ()
 atiddxLoadLogo ()
 atiddxLogoInit ()
 atiddxScreenInit ()
 AddScreen ()
Title: Xorg crashed with SIGSEGV in hwlIconUpload()
Uname: Linux 2.6.27-7-generic i686
UserGroups:

xkbcomp:

Stacktrace:
#0 0x08072648 in dixLookupPrivate ()
#1 0xb7a53998 in DRILock () from /usr/lib/xorg/modules/extensions//libdri.so
#2 0xb770ac91 in atiddxLeaveVT ()
   from /usr/lib/xorg/modules/drivers//fglrx_drv.so
#3 0xb7452c8f in ?? () from /usr/lib/xorg/modules//libxaa.so
#4 0x080a8af9 in AbortDDX ()
#5 0x0813c428 in AbortServer ()
#6 0x080c30c3 in xf86SigHandler ()
#7 <signal handler called>
#8 0xb774397a in hwlIconUpload ()
   from /usr/lib/xorg/modules/drivers//fglrx_drv.so
#9 0xb772d770 in atiddxLoadLogo ()
   from /usr/lib/xorg/modules/drivers//fglrx_drv.so
#10 0xb772d8ce in atiddxLogoInit ()
   from /usr/lib/xorg/modules/drivers//fglrx_drv.so
#11 0xb770781c in atiddxScreenInit ()
   from /usr/lib/xorg/modules/drivers//fglrx_drv.so
#12 0x0807137f in AddScreen ()
#13 0x080aa526 in InitOutput ()
#14 0x08071b19 in main ()

[lspci]
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge [1106:3188] (rev 01)
     Subsystem: ASUSTeK Computer Inc. Device [1043:80a3]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc R360 NJ [Radeon 9800 XT] [1002:4e4a]
     Subsystem: ASUSTeK Computer Inc. Device [1043:c000]

[W. Prins (wprins)]

More information:

xorg server build: 2:1.5.2-2ubuntu1 (<email address hidden>)
xorg-driver-fglrx: Installed: 2:8.543-0ubuntu3
Video card: Asus ATI Radeon 9800XT 256MB AGP
Motherboard: Asus K8V Deluxe

This bug originally reported in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/286140 , however as this bug report is more complete I've marked 286140 as a duplicate of this bug, making this the primary report of this bug.

[W. Prins (wprins)]

This bug is apparently hitting more people, see for example this reported experience in the wild:
http://www.groklaw.net/comment.php?mode=display&sid=20081031193540170&title=Review%3A+Ubuntu+8.10+Is+The+Real+Deal&type=article&order=&hideanonymous=0&pid=733654#c733661

[Bryce Harrington (bryce)]

While the backtrace shows fglrx, the logs and conf file attached seem to be from running the open -ati driver.

Are you still seeing this issue? If so, could you please attach a /var/log/Xorg.0.log[.old] and /etc/X11/xorg.conf from after reproducing the crash while running fglrx?

Also, you might want to try uninstalling all fglrx packages and reinstalling fglrx from scratch, just to be sure you have a clean environment.

[W. Prins (wprins)]

OK, sorry for only posting back today. I think you can close this bug as I don't get this problem anymore with the release version of Intrepid 8.10, even though I do still have an ongoing fglrx problem with a different message. (I think I reported such in a different report however, so I'll followup there, or otherwise open a new ticket.)

[W. Prins (wprins)]

Hmm, the report I was thinking of has been marked as a duplicate of this bug... I don't think the two errors are in fact the same, since the call stack is different, and the error message is different. Even so, I've got an update to this sorry saga. For some time I've been playing hide and seek with this error, sometimes thinking it's been fixed, only to boot the PC one day and *bam*, suddenly X won't start properly again and I have to jump through hoops (so it seemed) to get it working again. I've however today noticed something interesting, after having done a clean reinstallation of 8.10 again on the problem machine: The "fglrx" driver only works reliably for me, if you hot-boot (with reset button say, or shutdown) after having run Windows. If you do this, then booting into Ubuntu using fglrx works fine. If however you cold-boot directly into Ubuntu, then the error message mentioned in the duplicate bug results, as follows:

(EE) fglrx(0): Failed to allocate CMM buffer (size=16384, alignment=4096)!
(==) fglrx(0): Using hardware cursor
(EE) fglrx(0): Failed to allocate CMM buffer (size=4096, alignment=4096)!
(EE) fglrx(0): Failed to allocate CMM buffer (size=4096, alignment=4096)!

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xb7f16400]
2: /usr/lib/xorg/modules/drivers//fglrx_drv.so(atiddxLoadLogo+0x70) [0xb76b6770]
3: /usr/lib/xorg/modules/drivers//fglrx_drv.so(atiddxLogoInit+0x14e) [0xb76b68ce]
4: /usr/lib/xorg/modules/drivers//fglrx_drv.so(atiddxScreenInit+0x8ec) [0xb769081c]
5: /usr/X11R6/bin/X(AddScreen+0x19f) [0x807137f]
6: /usr/X11R6/bin/X(InitOutput+0x206) [0x80aa536]
7: /usr/X11R6/bin/X(main+0x279) [0x8071b19]
8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b1d685]
9: /usr/X11R6/bin/X [0x8071101]
Saw signal 11. Server aborting.

I attach the log and config as saved by failsafe X.

Further, for reference, lspci lists my video card as:
walterp@test-desktop:~$ sudo lspci | grep ATI
01:00.0 VGA compatible controller: ATI Technologies Inc R360 NJ [Radeon 9800 XT]
01:00.1 Display controller: ATI Technologies Inc RV350 NJ [Radeon 9800 XT] (Secondary)

[W. Prins (wprins)]

As I'm no longer getting the original problem reported in the original report, I'm marking this bug report as invalid, and have unmarked as duplicate, the other bug report I marked as duplicate of this.

[W. Prins (wprins)]

This problem as reported originally does not exist anymore. The bug report that was marked as dupliate of this, however does, and has been unmarked as duplicate for followup there.

[W. Prins (wprins)]

This problem as reported originally does not exist anymore. The bug report that was marked as duplicate of this, however does, and has been unmarked as duplicate for followup there.