| Summary: | [SNB+]igt/drv_getparams fails | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | lu hua <huax.lu> | ||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Severity: | normal | ||||||
| Priority: | medium | CC: | intel-gfx-bugs | ||||
| Version: | unspecified | ||||||
| Hardware: | All | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: | 
            
  | 
      ||||||
| 
 
        
          Description
        
        
          lu hua
        
        
        
        
          2015-03-19 03:19:34 UTC
        
       
    This is actually expected behavior. Older kernels don't support this param, so will return -EINVAL. Newer kernels will return the new, expected error code of ENODEV on older devices, and a valid value for newer ones. Not sure how we want to handle this... it shouldn't be a problem going forward, so we could just wontfix it. Author: Jeff McGee <jeff.mcgee@intel.com> Date: Tue Mar 24 11:30:57 2015 -0700 tests/drv_getparams: Skip instead of fail on EINVAL Nope this isn't WONTFIX, igt generally should detect older kernels (within limits) and skip correctly. Fixed. It skips on the latest igt and -fixes kernel. IGT-Version: 1.10-g1cfcca6 (x86_64) (Linux: 4.0.0-rc5_drm-intel-fixes_771246_20150326+ x86_64) Test requirement not met in function subslice_total, file drv_getparams.c:80: Test requirement: !(ret == -EINVAL) Interface not supported by kernel Last errno: 22, Invalid argument Subtest subslice-total: SKIP (0.000s) Test requirement not met in function eu_total, file drv_getparams.c:117: Test requirement: !(ret == -EINVAL) Interface not supported by kernel Last errno: 22, Invalid argument Subtest eu-total: SKIP (0.000s) 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.