Created attachment 113454 [details] dmesg ==System Environment== -------------------------- Regression: yes Non-working platforms: HSW ==kernel== -------------------------- drm-intel-nightly/2a579576e4c01799ec67264c9169e5adeadcc3ff(2015-2-13) ==Bug detailed description== ----------------------------- ./pm_rpm --run-subtest i2c IGT-Version: 1.9-g9846e7f (x86_64) (Linux: 3.19.0_drm-intel-nightly_dbd79c_20150213+ x86_64) Runtime PM support: 1 PC8 residency support: 0 (pm_rpm:7461) igt-aux-CRITICAL: Test assertion failure function igt_get_runtime_pm_status, file igt_aux.c:588: (pm_rpm:7461) igt-aux-CRITICAL: Failed assertion: false (pm_rpm:7461) igt-aux-CRITICAL: Last errno: 5, Input/output error (pm_rpm:7461) igt-aux-CRITICAL: Unknown status unsupported Subtest i2c: FAIL (0.008s) ==Reproduce steps== ---------------------------- 1. ./pm_rpm --run-subtest i2c
I find it really weird that you get the "Unknown status unsupported" only on pm_rpm/i2c. Are you really sure you get this message only on this test? How reproducible is this? Can you please retest against the latest IGT and Kernel sources? Also, please make sure that every dmesg file you attach to every bug report always contains drm.debug=0xe, and that the Kernel buffer log size is big enough to keep everything. This is probably written on QA's BKMs somewhere.
(In reply to Paulo Zanoni from comment #1) > I find it really weird that you get the "Unknown status unsupported" only on > pm_rpm/i2c. Are you really sure you get this message only on this test? How > reproducible is this? Can you please retest against the latest IGT and > Kernel sources? > > Also, please make sure that every dmesg file you attach to every bug report > always contains drm.debug=0xe, and that the Kernel buffer log size is big > enough to keep everything. This is probably written on QA's BKMs somewhere. Pass with latest IGT and latest nightly branch, commit:855932144a48a66081a62288bea6f2bbbf48e2e7(2015-02-28). Close this bug.
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.