Bug 88874

Summary:

[BYT/BSW]igt//pm_rps/reset doesn't exit testing

Product:

DRI

Reporter:

lu hua <huax.lu>

Component:

DRM/Intel

Assignee:

Intel GFX Bugs mailing list <intel-gfx-bugs>

Status:

CLOSED DUPLICATE

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	Flags
dmesg	none

Description lu hua 2015-01-30 05:50:14 UTC

Created attachment 112958 [details]
dmesg

==System Environment==
--------------------------
Regression: not sure, it has bug 84896

Non-working platforms: BYT/BSW

==kernel==
--------------------------
drm-intel-nightly/05081c1044aada500676224c0439442624c94646
commit 05081c1044aada500676224c0439442624c94646
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Thu Jan 29 18:04:48 2015 +0100

    drm-intel-nightly: 2015y-01m-29d-17h-04m-28s UTC integration manifest

==Bug detailed description==
-----------------------------
It takes more than 10 minutes, and doesn't exit testing. bug 84896's crash goes away.

output:
IGT-Version: 1.9-g7848d21 (x86_64) (Linux: 3.19.0-rc6_drm-intel-nightly_05081c_20150130+ x86_64)
^C(pm_rps:4225) CRITICAL: Test assertion failure function load_helper_stop, file pm_rps.c:290:
(pm_rps:4225) CRITICAL: Failed assertion: igt_wait_helper(&lh.igt_proc) == 0
(pm_rps:4225) CRITICAL: Last errno: 10, No child processes
Subtest reset: FAIL (646.744s)
pm_rps: igt_core.c:1012: fork_helper_exit_handler: Assertion `helper_process_count == 0' failed.
Aborted (core dumped)

real    10m47.581s
user    0m0.364s
sys     0m1.433s

==Reproduce steps==
---------------------------- 
1. time ./pm_rps --run-subtest reset

Comment 1 Mika Kuoppala 2015-02-03 18:23:40 UTC


*** This bug has been marked as a duplicate of bug 88933 ***

Comment 2 Elizabeth 2017-10-06 14:31:44 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.