https://bugs.freedesktop.org/show_bug.cgi?id=57531
Priority: medium Bug ID: 57531 Assignee: dri-devel@lists.freedesktop.org Summary: [GEM] RS780V allocation errors with piglit Severity: normal Classification: Unclassified OS: All Reporter: kphillisjr@gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa
Created attachment 70558 --> https://bugs.freedesktop.org/attachment.cgi?id=70558&action=edit Dmesg log - after third pass of piglit.
I was giving piglit a trial run, and noticed that there was a few errors about the radeon driver being able to allocate gem objects.
Piglit package: 1.0.0~git20121122.cf47699-0edgers~quantal1 Piglit Git revision:cf47699087f74a6fd94c59a74837fc6c3c6422a8
Mesa Package: 9.1~git20121110.c6f426c0-0ubuntu0ricotz~quantal Mesa Git Revision: c6f426c02d14fcdfdbdd03473d098d4c9b81a8b2
Libdrm package: 2.4.40+git20121109.e01d68f9-0ubuntu0ricotz~quantal libdrm revision: e01d68f9f3acfc35fe164283904b5d058c2ab378
Notes: In the kernel log, the first pass errors started at: 11166.715813, second pass started at 11742.655557 and third pass had errors start 13408.932142.
https://bugs.freedesktop.org/show_bug.cgi?id=57531
--- Comment #1 from Kenney Phillis Jr kphillisjr@gmail.com --- Created attachment 70559 --> https://bugs.freedesktop.org/attachment.cgi?id=70559&action=edit Xorg log
https://bugs.freedesktop.org/show_bug.cgi?id=57531
--- Comment #2 from Kenney Phillis Jr kphillisjr@gmail.com --- Created attachment 70560 --> https://bugs.freedesktop.org/attachment.cgi?id=70560&action=edit Piglit test results for all 3 passes
https://bugs.freedesktop.org/show_bug.cgi?id=57531
Kenney Phillis Jr kphillisjr@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |x86 (IA32) OS|All |Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=57531
--- Comment #3 from Michel Dänzer michel@daenzer.net --- Some piglit tests are about allocating as large textures as possible, which can result in such intermittent allocation failures. It might be feasible to handle this more gracefully in userspace, but otherwise it should be mostly harmless, assuming there are no other, real problems associated with it.
https://bugs.freedesktop.org/show_bug.cgi?id=57531
--- Comment #4 from Marek Olšák maraeo@gmail.com --- AFAIK, allocation failures are correctly reported to applications as the GL_OUT_OF_MEMORY errors.
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.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org