From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 57531] [GEM] RS780V allocation errors with piglit
Date: Tue, 27 Nov 2012 09:41:29 +0000 [thread overview]
Message-ID: <bug-57531-502-Z3EhUey6zb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-57531-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 833 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=57531
Christian König <deathsimple@vodafone.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTABUG
--- Comment #5 from Christian König <deathsimple@vodafone.de> ---
Totally agree with that. Some piglit tests even allocate all the memory on
purpose to test that the driver can handle that gracefully, and the expectation
in the good case is that those error messages start to appear.
As long as you don't experience any crash, hang or something like this
everything should be fine.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2336 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
prev parent reply other threads:[~2012-11-27 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 22:36 [Bug 57531] New: [GEM] RS780V allocation errors with piglit bugzilla-daemon
2012-11-25 22:38 ` [Bug 57531] " bugzilla-daemon
2012-11-25 22:40 ` bugzilla-daemon
2012-11-25 22:41 ` bugzilla-daemon
2012-11-26 15:17 ` bugzilla-daemon
2012-11-26 17:04 ` bugzilla-daemon
2012-11-27 9:41 ` bugzilla-daemon [this message]
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-57531-502-Z3EhUey6zb@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