continuous [driAllocateTexture:636] even when idle

Bug #305586 reported by Uwe Geuder
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: gnome-control-center

1) $ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

2) $ apt-cache policy gnome-control-center
gnome-control-center:
  Installed: 1:2.24.0.1-0ubuntu7.1
  Candidate: 1:2.24.0.1-0ubuntu7.1
  Version table:
 *** 1:2.24.0.1-0ubuntu7.1 0
        500 http://fi.archive.ubuntu.com intrepid-updates/main Packages
        100 /var/lib/dpkg/status
     1:2.24.0.1-0ubuntu7 0
        500 http://fi.archive.ubuntu.com intrepid/main Packages

3) What I expected to happen: No resource problems and/or continuous error messages to log on an idle system with default settings

4) What happend: The message

"[driAllocateTexture:636] unable to allocate texture"

is written to /var/log/gdm/\:0.log about once a second even when the system is idle and no graphics intensive application is running.

Without being an expert in this area, I understand this means that the resources of graphics card have been exhausted.

I believe this can be seen by the end user e.g. by drastically reduced scrolling performance e.g. in a normal gnome terminal (but I have not investigated this claim very carefully). Anyway I think writing an error to a log file about once a
second in a clean system is not acceptable.

Further details

Hardware: Laptop IBM T40

Graphics card:

(--) PCI:*(0@1:0:0) ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] rev 2, Mem @ 0xe0000000/0, 0xc0100000/0, I/O @ 0x00003000/0, BIOS @ 0x????????/131072

Software: a plain intrepid installation with all recommended updates and only 3 minor additional packages installed

Work around: Go to System --> Preferences --> Appearance // Visual Effects and change the default setting "Normal" to "None"

Without understanding much of that topic I made the following guesses:

- The "Normal" visual effects of 2008 are just too heavy for an approximately 5 year old laptop. (I understand business laptops like this one are not optimized for graphics performance anyway)

- Because the graphic card runs out of resources the error occurs continuously

If my guesses are correct the only solution is that Ubuntu must recognize during installation (or at each boot), whether the graphics card is powerful enough to handle "Normal" visual effects. If not, they should be disabled by default, because the average user

- will not read the log files,
- will not understand what the error message [driAllocateTexture:636] means (nor do I)
- and will not be able to draw the conclusion that visual effect should be disabled

I further guessed that gnome-control-center might possibly be responsible for the default settings, because it allows the user to change the visual effects. If this guess was wrong, the bug needs to be redirected to another package, whoever is
responsible for choosing the default value)

(Of course if my guesses above that the visual effects will just not reasonably work on "such an old" laptop graphics card were wrong, it might be possible to correct the implementation of the visual effects. Then again, the bug should be redirected to whoever causes the error message)

description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Pedro Villavicencio (pedro) wrote :

not a gnome-control-center issue.

Revision history for this message
Patrick Kilgore (patrick-kilgore) wrote :

Can you attach (or just check) to see if this error is being written to /var/log/Xorg.0.log ?
I'm about 90% sure this is x's problem.

Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

Please find attached both the Xorg and the gdm/\:0 logs. They are copied more or less immediately after booting with "normal" visual effects. Only one xterm was started during that time.

Changed in xorg:
status: Incomplete → New
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

Hi ubuntulp-ugeuder,

Please attach the output of `lspci -vvnn` too.

Changed in xserver-xorg-video-ati:
status: New → Incomplete
Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

Oops, sorry, I completely forgot about this log file. I hope I'll remember to do it soon. (Right now I'm not close to the machine in question and it's not online)

Bryce Harrington (bryce)
Changed in xserver-xorg-video-ati:
status: Incomplete → New
Revision history for this message
Bryce Harrington (bryce) wrote :

Actually, the lspci output probably doesn't matter for this bug.

I notice this error message comes from mesa rather than -ati. Refiling.

./mesa-7.2+git20081209.a0d5c3cf/src/mesa/drivers/dri/common/texmem.c: fprintf( stderr, "[%s:%d] unable to allocate texture\n",

Changed in xserver-xorg-video-ati:
status: New → Incomplete
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 mesa:
status: Incomplete → Invalid
Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

> since it is has been some time with no response from the original reporter.

I'm the original reporter.

> However, if the issue still exists

Yes, it does, (intrepid system with all updates, tested 2 minutes ago)

apt-cache policy libgl1-mesa-dri
libgl1-mesa-dri:
  Installed: 7.2-1ubuntu2
  Candidate: 7.2-1ubuntu2
  Version table:
 *** 7.2-1ubuntu2 0
        500 http://fi.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

> feel free to reopen with the requested information.

Sorry, I'm not aware that any additional information has been requested from me. Could you please rephrase what you need.

Changed in mesa:
status: Invalid → New
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi ubuntulp-ugeuder,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISO CD images are available from http://cdimage.ubuntu.com/releases/)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-verification
Changed in mesa (Ubuntu):
status: New → Incomplete
Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

Hi Bryce,

Tanks for your message. I'm about to leave to holidays and unfortunately I won't be able to investigate the issue right now. I should be be able to look into again in mid-August at the latest.

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

It's mid-August now, please retest on latest development version of Karmic to make sure the issue still happens there with the latest code. ISO images are available via http://www.ubuntu.com/testing/. If you can reproduce it in the LiveCD environment, you shouldn't need to modify your installed system. Also please attach a fresh Xorg.0.log and dmesg from this testing.

Changed in mesa (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Bryce Harrington (bryce)
tags: added: intrepid
Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

Sorry about the delay, too many things ongoing...

Tried with Karmic Alpha 5 LiveCD. There are no continuous log writings with normal desktop effects.

(Is logging active in LiveCD enviroment???)

Double checked with my current Intrepid installation: continuous log writings do still occur as originally reported.

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

[This is an automatic notification.]

Hi Uwe,

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 305586

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 305586 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/305586

Changed in mesa (Ubuntu):
status: Incomplete → New
status: New → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

Hi Bryce,

With Lucid I have switched to Kubuntu on that machine. I'm not sure whether it is possible to retest the original problem in Kubuntu, because the visual effects are probably quite differently implemtned. I cannot promise that I have time to install Ubuntu until June, but I'll try to keep it in mind. As mentioned in comment #12 I'm not sure whether log writings would appear in LiveCD environment (after all there is no disk to write the log to) So I guess installing Ubuntu Lucid is the only way to be sure.

Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

Retested on the original machine with Ubuntu Lucid 10.04 LTS. No log writings in /var/log/gdm/\:0.log anymore.

Changed in mesa (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

Fixed in Lucid 10.04 LTS (or possibly even earlier)

tags: added: verification-done
removed: needs-retested-on-lucid-by-june needs-verification
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.