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 45921] [r300g, bisected] Multiple piglit regression after winsys/radeon: hook up the new DRM_RADEON_GEM_WAIT ioctl
Date: Sat, 11 Feb 2012 12:19:27 +0000	[thread overview]
Message-ID: <bug-45921-502-w8p4LXNfsf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-45921-502@http.bugs.freedesktop.org/>

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

--- Comment #3 from Marek Olšák <maraeo@gmail.com> 2012-02-11 04:19:27 PST ---
(In reply to comment #2)
> (In reply to comment #1)
> > I am sure the commit in question is not the cause. I prematurely added the code for the new ioctl and disabled it later on, because my kernel code the commit
> > was supposed to interact with wasn't accepted.
> > 
> > The problem when bisecting is that now it tries to call a non-existing ioctl if the DRM minor version is >=12, which makes some tests fail. Could you please
> > check dmesg to see if that's the case? There should be some error messages from DRM.
> 
> None of the tests produce any output in dmesg.

Okay.

> > 
> > I think that some of those piglit failures are caused by the glsl-to-tgsi translator. You can disable glsl-to-tgsi by commenting out:
> > 
> >   functions->LinkShader = st_link_shader;
> > 
> > at the end of src/mesa/state_tracker/st_cb_program.c.
> 
> From all the mentioned tests only glsl-fs-discard-02 pass when I disable glsl-to-tgsi.
> 
> BTW in which commit was the new ioctl disabled?

In this one: ef64da8f013691c66744064769db379e57ef95de

> I mean, I can understand that if I don't have kernel with support for the new ioctl it breaks the tests,
> however if the ioctl was disabled later shouldn't be current git working unless another regression happened?

Yes, it should.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2012-02-11 12:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-11 10:08 [Bug 45921] New: [r300g, bisected] Multiple piglit regression after winsys/radeon: hook up the new DRM_RADEON_GEM_WAIT ioctl bugzilla-daemon
2012-02-11  3:59 ` [Bug 45921] " bugzilla-daemon
2012-02-11 11:21 ` bugzilla-daemon
2012-02-11 12:19 ` bugzilla-daemon [this message]
2012-02-11 12:51 ` bugzilla-daemon
2012-02-11 13:59 ` bugzilla-daemon
2012-02-11 14:20 ` [Bug 45921] [r300g, bisected] Multiple piglit regressions after glsl_to_tgsi changes bugzilla-daemon
2012-04-14 15:16 ` 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-45921-502-w8p4LXNfsf@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