From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42050] New: Maximizing glxgears -> texture_desc_init: The buffer is not large enough
Date: Thu, 20 Oct 2011 13:06:31 +0000 [thread overview]
Message-ID: <bug-42050-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=42050
Bug #: 42050
Summary: Maximizing glxgears -> texture_desc_init: The buffer
is not large enough
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: curaga@operamail.com
Mobility X1600 / 128mb
r300g git (2.1 Mesa 7.12-devel (git-6235846) / Gallium 0.4 on ATI RV530)
Linux 3.0.3
When I maximize glxgears, I get the following errors:
r300: texture_desc_init: The buffer is not large enough. Got: 4972544, Need:
4976640, Info:
r300: texture_desc_init: Macro: NO, Micro: YES, Pitch: 1440, Dim: 1438x863x1,
LastLevel: 0, Size: 4976640, Format: x8z24_unorm
r300: ERROR: Cannot set texture properties.
When maximized, it also stutters about every second, which may or may not be
related. This may also be a kernel bug, if so, please reassign.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-10-20 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 13:06 bugzilla-daemon [this message]
2011-10-20 21:40 ` [Bug 42050] Maximizing glxgears -> texture_desc_init: The buffer is not large enough bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-42050-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox