Summary: | [KBL] [Regression] pm_rps / reset fails | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | cprigent <christophe.prigent> | ||||||
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: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | KBL | i915 features: | power/runtime PM | ||||||
Attachments: |
|
Description
cprigent
2016-08-05 13:23:55 UTC
Created attachment 125553 [details]
kblu-pm_rps__reset-dmesg
Test was Pass with: Kernel: 4.7.0-rc7 895a714 from http://cgit.freedesktop.org/drm-intel/ commit 895a714b0b596cfcbe82065f99376ad02d369125 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Mon Jul 18 14:35:39 2016 +0200 drm-intel-nightly: 2016y-07m-18d-12h-35m-15s UTC integration manifest drm: libdrm-2.4.68-15 2212a64 from git://anongit.freedesktop.org/mesa/drm mesa: mesa-11.2.2 3a9f628from git://anongit.freedesktop.org/mesa/mesa cairo: 1.15.2 db8a7f1 from git://anongit.freedesktop.org/cairo Intel-Gpu-Tools 1.15-127 ee5d5c4 from http://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools.git And without i915.enable_guc_loading=2 i915.enable_guc_submission=2 ? (In reply to yann from comment #4) > > *** This bug has been marked as a duplicate of bug 97824 *** This bug was filed before the regression behind 97824 landed. It may not be related. (In reply to Chris Wilson from comment #5) > (In reply to yann from comment #4) > > > > *** This bug has been marked as a duplicate of bug 97824 *** > > This bug was filed before the regression behind 97824 landed. It may not be > related. I agree but seeing comment #2 in bug 97824 and chatting with Christophe, we agreed to track using recent one |
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.