Bug 73641 - [nv ppgtt]igt/gem_gtt_hog fails
Summary: [nv ppgtt]igt/gem_gtt_hog fails
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-15 03:08 UTC by lu hua
Modified: 2017-10-06 14:40 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (112.95 KB, text/plain)
2014-01-15 03:08 UTC, lu hua 		no flags Details
View All

Description lu hua 2014-01-15 03:08:10 UTC 
Created attachment 92107 [details]
dmesg

System Environment:
--------------------------
Platform: Haswell(nv)
Kernel: (drm-intel-nightly)07db3e0b8568d81226e2e17dbb1b340668cb2287

Bug detailed description:
-------------------------
It fails on haswell with NVIDIA card GT440. It's a new case.
It works well on -fixes and -queued kernel.
It fails on -nightly and ppgtt kernel

output:
IGT-Version: 1.5-g1552aa2 (x86_64) (Linux: 3.13.0-rc3_ppgtt_e91030_20140114+ x86_64)
Test assertion failure function main, file gem_gtt_hog.c:170:
Last errno: 0, Success
Failed assertion: status == 0

Reproduce steps:
----------------
1. ./gem_gtt_hog
Comment 1 Chris Wilson 2014-01-15 10:47:06 UTC 
Should be fixed by

commit 5e278c86eda1d5ade7c0fc425edc589e3c9dff59
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Jan 15 10:40:40 2014 +0000

    gem_gtt_hog: use a normal exit()
    
    Since we don't execute any subtests, using igt_exit leads to
    inconsistent behaviour. In the future, this may be converted.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=73641
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Comment 2 lu hua 2014-01-16 03:06:15 UTC 
Verified.Fixed.
Comment 3 Elizabeth 2017-10-06 14:40:28 UTC 
Closing old verified.

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.