From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 53111] [bisected] lockups since added support for virtual address space on cayman v11
Date: Sun, 16 Dec 2012 21:31:50 +0000 [thread overview]
Message-ID: <bug-53111-502-EDYUeK9R4Q@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-53111-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1403 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=53111
--- Comment #27 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(In reply to comment #21)
> (In reply to comment #20)
> > (In reply to comment #19)
> > > So about this locking piglit test (depthstencil-render-miplevels 146
> > > s=z24_s8_d=z32f_s8), I've been able to track it down to:
> > > line 218: piglit_report_result(PIGLIT_SKIP);
> >
> > How did you determine that? It's weird, I wouldn't expect a skipped test to
> > produce any actual GPU rendering.
>
> I used gdb and step into the code until it locked. It gets out at level 0,
> after going through:
>
> /**
> * Attach the proper miplevel of each texture to the framebuffer
> */
> void
> set_up_framebuffer_for_miplevel(int level)...
>
> Before this call, there is a framebuffer initialization:
> GLuint fbo;
> glGenFramebuffers(1, &fbo);
> glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo);
> glBindFramebuffer(GL_READ_FRAMEBUFFER, fbo);
>
> for (int level = 0; level <= max_miplevel; ++level) {
> set_up_framebuffer_for_miplevel(level);
It seems that with latest mesa, drm, xf86 and kernel 3.7.0-rc7-71633-g3b6b59b
from drm-next, it doesn't fail on this test anymore. It does lock however on a
different one. I'll debug it and see where it locks.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2531 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-12-16 21:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 4:00 [Bug 53111] New: [bisected] lockups since added support for virtual address space on cayman v11 bugzilla-daemon
2012-08-04 4:13 ` [Bug 53111] " bugzilla-daemon
2012-08-04 4:32 ` bugzilla-daemon
2012-08-06 13:27 ` bugzilla-daemon
2012-08-06 14:42 ` bugzilla-daemon
2012-08-07 1:21 ` bugzilla-daemon
2012-08-09 3:07 ` bugzilla-daemon
2012-08-09 7:05 ` bugzilla-daemon
2012-08-17 3:49 ` bugzilla-daemon
2012-08-17 7:28 ` bugzilla-daemon
2012-08-18 5:08 ` bugzilla-daemon
2012-08-18 5:09 ` bugzilla-daemon
2012-08-19 22:22 ` bugzilla-daemon
2012-08-19 23:03 ` bugzilla-daemon
2012-08-19 23:04 ` bugzilla-daemon
2012-08-20 14:59 ` bugzilla-daemon
2012-08-20 15:05 ` bugzilla-daemon
2012-08-22 3:02 ` bugzilla-daemon
2012-08-22 5:32 ` bugzilla-daemon
2012-08-23 4:12 ` bugzilla-daemon
2012-08-23 6:45 ` bugzilla-daemon
2012-08-23 13:13 ` bugzilla-daemon
2012-08-30 21:34 ` bugzilla-daemon
2012-08-30 21:42 ` bugzilla-daemon
2012-08-30 22:38 ` bugzilla-daemon
2012-09-06 17:19 ` bugzilla-daemon
2012-10-03 2:47 ` bugzilla-daemon
2012-12-16 21:31 ` bugzilla-daemon [this message]
2013-02-01 4:35 ` bugzilla-daemon
2013-02-01 4:36 ` 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-53111-502-EDYUeK9R4Q@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;
as well as URLs for NNTP newsgroup(s).