Bug 70558

Summary: [BYT]igt/gem_suspend/fence-restore-tiled2untiled test failed
Product: DRI Reporter: Guo Jinxian <jinxianx.guo>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED NOTOURBUG QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs, qingshuai.tian
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg none

Description Guo Jinxian 2013-10-17 03:43:10 UTC 
System Environment:
--------------------------
Platform: BayTrail
kernel   (drm-intel-next-queued)4cdb83ec9a72f741c75e20c8e412c505fc037f5f


Bug detailed description:
-----------------------------
Test assertion failure function test_fence_restore, file gem_suspend.c:83: 
Failed assertion: ptr1[i] == i 
this case always failed since the testing began on baytrail.

Following two cases have the same failure.
igt/gem_suspend/fence-restore-tiled2untiled
igt/gem_suspend/fence-restore-untiled
**** List of PLAYBACK Hardware Devices ****
rtcwake: wakeup from "mem" using /dev/rtc0 at Tue Jan 2 05:22:39 2001 
checking the first canary object 
Test assertion failure function test_fence_restore, file gem_suspend.c:83: 
Failed assertion: ptr1[i] == i 
Subtest fence-restore-tiled2untiled: FAIL 

Reproduce steps:
----------------------------
1. ./gem_suspend --run-subtest fence-restore-tiled2untiled
Comment 1 Guo Jinxian 2013-10-17 09:55:07 UTC 
Created attachment 87787 [details]
dmesg
Comment 2 Daniel Vetter 2013-10-17 15:25:19 UTC 
Is this a regression? Jesse says that just days ago S3 worked flawlessly on byt ...
Comment 3 Guo Jinxian 2013-10-23 03:30:06 UTC 
The tests passed after we update the BIOS to new version.
The new BIOS version:
     BBAYCRB1.86C.0065.R31.1310162219
     BBAY_IA32_R_V65_31


The old BIOS version: (s3 fails on this version)
     BBAYCRB1.86C.0061.R22.1309171818
     BBAY_IA32_R_V6122_MCU312

kernel: (drm-intel-testing)d1b2b826f0969182f055d11c991f90fdc6a4924a
Comment 4 Daniel Vetter 2013-10-27 19:22:34 UTC 
Nice, another bug we can blame on the BIOS \o/
Comment 5 Daniel Vetter 2013-10-27 19:23:08 UTC 
*** Bug 70573 has been marked as a duplicate of this bug. ***
Comment 6 Guo Jinxian 2013-11-01 06:33:32 UTC 
Close it due to it's blamed on the BIOS.
Comment 7 Elizabeth 2017-10-06 14:42:40 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.