[Bug 66952] New: [IVB Regression: Apple MacBook Pro] eDP + two any pipes will cause call trace in dmesg
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jul 16 01:46:41 PDT 2013
https://bugs.freedesktop.org/show_bug.cgi?id=66952
Priority: medium
Bug ID: 66952
Assignee: intel-gfx-bugs at lists.freedesktop.org
Summary: [IVB Regression: Apple MacBook Pro] eDP + two any
pipes will cause call trace in dmesg
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Severity: major
Classification: Unclassified
OS: All
Reporter: yangweix.shui at intel.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Intel
Product: DRI
Created attachment 82471
--> https://bugs.freedesktop.org/attachment.cgi?id=82471&action=edit
dmesg: eDP + two any cause call trace
Environment:
--------------------
Kernel: (drm-intel-next-queued)50b44a449ff1a19712ebc36ffccf9ac0a68033bf
Author: Daniel Vetter <daniel.vetter at ffwll.ch>
Date: Wed Jun 5 13:34:33 2013 +0200
drm/i915: clear DPLL reg when disabling i9xx dplls
Good commit: 328d8e829b9a05814af4722c1091d62c5533c4f8
lspci:
--------------------
00:02.0 VGA compatible controller: Intel Corporation Device 0162 (rev 09)
Description:
--------------------
With eDP and two any pipes plugged in, there's "call trace" in dmesg when
machine resumed from booting. If I plugged each pipe only, there's not this
issue. Our Apple MacBook Pro support: HDMI , mini-DP-to-HDMI, mini-DP-to-VGA,
mini-DP-to-DVI and mini-DP-to-DP.
Bisect is on the way, we will update the bug ASAP. This machine is not support
kexec currently, we need take much more time by manual. If you have any idea
about this regression, please comment. THX.
Reproduce step:
--------------------
1. plugged two any pipes in
2. reboot
3. check the dmesg when machine boot up
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130716/c0f17047/attachment.html>
More information about the intel-gfx-bugs
mailing list