Bug 37826 - piglit: fbo/fbo-maxsize assertion failure
Summary: piglit: fbo/fbo-maxsize assertion failure
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-01 10:29 UTC by Sven Arvidsson
Modified: 2012-01-10 16:15 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Sven Arvidsson 2011-06-01 10:29:59 UTC
The piglit test fbo/fbo-maxsize doesn't pass on my Evergreen:

Returncode: -6

Errors:
Failed to allocate :
   size      : 1431698944 bytes
   alignment : 512 bytes
Failed to allocate :
   size      : 1431698944 bytes
   alignment : 512 bytes
fbo-maxsize: /home/sa/Programming/gfx/piglit/tests/fbo/fbo-maxsize.c:115: create_fbo: Assertion `glGetError() == 0' failed.

dmesg:
Jun  1 19:10:43 zoe kernel: [ 1384.924077] radeon 0000:01:00.0: object_init failed for (1431699456, 0x00000006)
Jun  1 19:10:43 zoe kernel: [ 1384.924081] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (1431699456, 4, 4096, -12)
Jun  1 19:10:43 zoe kernel: [ 1384.926286] radeon 0000:01:00.0: object_init failed for (1431699456, 0x00000006)
Jun  1 19:10:43 zoe kernel: [ 1384.926289] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (1431699456, 4, 4096, -12)

This doesn't seem to be a new problem, it fails with 7.10 too, but the kernel message is different: "[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!".

System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: REDWOOD
-- Model: XFX Radeon HD 5670 1GB
-- Display connector: DVI
-- xf86-video-ati: 6.14.2
-- xserver: 1.10.1
-- mesa: git-c5903ed
-- drm: 2.4.25
-- kernel: 2.6.39
Comment 1 Sven Arvidsson 2012-01-10 16:15:47 UTC
This test is passing now.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.