dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41231] New: GL_INVALID_ENUM when using glxinfo -l
Date: Mon, 26 Sep 2011 07:10:24 -0700 (PDT)	[thread overview]
Message-ID: <bug-41231-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=41231

           Summary: GL_INVALID_ENUM when using glxinfo -l
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: minor
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: stefano.teso@gmail.com


Hi,

using git 455a19b1b3d7ca0a40c65d89e45209dbd8ac7b35, and running:

$ glxinfo -l > /dev/null

makes mesa sad:

Mesa: User error: GL_INVALID_ENUM in
glGetIntegerv(pname=GL_MAX_COLOR_MATRIX_STACK_DEPTH)
Mesa: User error: GL_INVALID_ENUM in glGetConvolutionParameteriv

This doesn't happen with stock mesa 7.11, nor when using
LIBGL_ALWAYS_SOFTWARE=1. The driver is r600g, the device is:

01:00.0 VGA compatible controller: ATI Technologies Inc Robson CE [AMD Radeon
HD 6300 Series]

I'm using debian unstable FWIW.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-09-26 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26 14:10 bugzilla-daemon [this message]
2011-09-29  9:58 ` [Bug 41231] GL_INVALID_ENUM when using glxinfo -l bugzilla-daemon
2011-09-29 13:58 ` bugzilla-daemon
2012-08-08 21:14 ` 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-41231-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