Created attachment 77844 [details] dmesg of running display with DP cause call trace Environment: -------------------------- commit e8aeaee7b012f1cdb382765d17307445385aa87c Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Sat Jul 21 16:47:09 2012 +0200 drm/i915: unbreak lastclose for failed driver init We now refuse to load on gen6+ if kms is not enabled: commit 26394d9251879231b85e6c8cf899fa43e75c68f1 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Mon Mar 26 21:33:18 2012 +0200 drm/i915: refuse to load on gen6+ without kms Which results in the drm core calling our lastclose function to clean up the mess, but that one is neatly broken for such failure cases since kms has been introduced in commit 79e539453b34e35f39299a899d263b0a1f1670bd Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Fri Nov 7 14:24:08 2008 -0800 DRM: i915: add mode setting support Reported-and-tested-by: Paulo Zanoni <przanoni@gmail.com> Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Description: --------------------- When I testdisplay with DP plugged on ILK platform, it will come up a "Call Trace". Because we usually test our testing on another ILK machine, so this bug we haven't found immediately. This bug is caused between "Linux 3.6" and "Linux 3.7". I tried to bisect, but there's too many merge commit in it. I can't find the first bad, when I bisect commit to e8aeaee7b012f1cdb382765d17307445385aa87c, there's information on terminal like below: ########################## [root@x-kernel drm-intel]# git bisect bad e8aeaee7b012f1cdb382765d17307445385aa87c The merge base a0d271cbfed1dd50278c6b06bead3d00ba0a88f9 is bad. This means the bug has been fixed between a0d271cbfed1dd50278c6b06bead3d00ba0a88f9 and [65b99c74fdd325d1ffa2e5663295888704712604 6d55d5968a8622f3ea20ec40737aea1cfba6438c 979570e02981d4a8fc20b3cc8fd651856c98ee9d a0d271cbfed1dd50278c6b06bead3d00ba0a88f9 aecdc33e111b2c447b622e287c6003726daa1426]. statement: ------------------ I have appended the dmesg in attachment. If you need more information or something else needed, please comment, I'm glad to working for this.
Is this still an issue on latest kernels? If not please attach a new drm.debug=0xe dmesg form 3.9-rc or so. The original WARN was a bit broken, but this should be fixed since commit 75c5da279e06577190abba52cabf0dc2a56edb97 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Mon Sep 10 21:58:29 2012 +0200 drm/i915: fix up the IBX transcoder B check
Created attachment 77974 [details] dmesg : 3.9-rc display call trace with DP (In reply to comment #1) > Is this still an issue on latest kernels? If not please attach a new > drm.debug=0xe dmesg form 3.9-rc or so. > > The original WARN was a bit broken, but this should be fixed since > > commit 75c5da279e06577190abba52cabf0dc2a56edb97 > Author: Daniel Vetter <daniel.vetter@ffwll.ch> > Date: Mon Sep 10 21:58:29 2012 +0200 > > drm/i915: fix up the IBX transcoder B check OK, I used latest -next-queued kernel, this issue also can be reproduced. Before I report this bug, I have tried many kernels, include 3.9-rc 3.8-rc 3.7-rc and 3.6-rc, until I go back to 3.6-rc, then I find a good commit. Now I attached the latest -next-queued 3.9-rc dmesg, and kernel info like below: ---------------------- Kernel: (drm-intel-nightly)4ab815b56a3886ac01a8e5d031dfa9733650df2d Some additional commit info: Author: Paulo Zanoni <paulo.r.zanoni@intel.com> Date: Fri Mar 22 14:16:38 2013 -0300 drm/i915: don't touch the PF regs if the power well is down
*** This bug has been marked as a duplicate of bug 54687 ***
Closing verified+duplicate as duplicate of closed+fixed.
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.