Bug 185825 – ati-drivers-8.37.6-r1 FGLTexMgrAllocMem failed

• Product: Gentoo Linux
• Status: RESOLVED UPSTREAM

[Description Iain Buchanan 2007-07-19 01:07:04 UTC]

I've only seen this with xscreensaver, but another person another distro says in Quake IV also[1].

for some x-screensavers (eg mirrorblob, starwars) this message always flashes in yellow, over the screensaver:

fglX11AllocateManagedSurface: __FGLTexMgrAllocMem failed!!

sometimes 4 in a row, sometimes 20 in a row.  The result is a "stutter" or otherwise bad performance in 3d.

gentoo-user discussions led me to check /dev/shm:
$ ls -al /dev/shm/
total 16
drwxrwxrwt  2 root root       60 2007-07-18 08:33 .
drwxr-xr-x 15 root root    14180 2007-07-19 08:32 ..
-rw-rw-rw-  1 iain users 1048576 2007-07-18 08:33 ATISHM00

and from /etc/fstab:
tmpfs   /dev/shm   tmpfs   defaults   0 0

I tried purging /dev/shm, unmounted and remounted, but no change.

Hardware is Inspiron 9100, P4 3.0GHz, with ATI radeon 9600:
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]


[1] http://ubuntuforums.org/showthread.php?p=1691647

[Comment 1 Iain Buchanan 2007-07-19 01:08:23 UTC]

Created attachment 125300 [details]
output from emerge --info

[Comment 2 Jakub Moc (RETIRED) 2007-07-19 06:00:43 UTC]

Bugs reproducible on Ubuntu are apparently not Gentoo specific, you need to complain to ATI.

(In reply to comment #0)
> I tried purging /dev/shm, unmounted and remounted, but no change.

This is a *very* bad idea.

[Comment 3 Iain Buchanan 2007-09-12 00:36:10 UTC]

OK, the "bug" exists with all these versions:

8.36.5
8.37.6
8.39.4
8.40.4

but not with 8.34.8.  I recompiled and rebooted in-between each one, then ran the mirrorblob screensaver to test.

I am re-opening this so that 8.34.8 doesn't get removed from portage, and so that other versions can be marked unstable if seen fit.  If this isn't the right way to do it, just let me know :)

[Comment 4 Jakub Moc (RETIRED) 2007-09-12 00:40:48 UTC]

Yeah, thanks but there's still nothing we could fix here. To get it fixed in latest versions, you still need to complain upstream and not here. 

Sorry.