[Bug 66444] New: [IVB DP] dmesg of machine boot up with "call trace" and "*ERROR* mismatch in clock (expected 28319, found 0"

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=66444

          Priority: medium
            Bug ID: 66444
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [IVB DP] dmesg of machine boot up with "call trace"
                    and "*ERROR* mismatch in clock (expected 28319, found
                    0"
        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 81792
  --> https://bugs.freedesktop.org/attachment.cgi?id=81792&action=edit
dmesg: boot up with call trace and error

Environment:
--------------------
Kernel: (drm-intel-next-queued)b110d88135c7aa43022c8f083079ba0e15737cc8
Author: Jesse Barnes <jbarnes at virtuousgeek.org>
Date:   Wed Jun 26 01:38:19 2013 +0300

    drm/i915: flip on a no fb -> fb transition if crtc is active v3

Description:
--------------------
Test with latest -next-queued kernel, I find there's "call trace" and some
error message in dmesg during machine booting up. I trace back to some older
-next-queued kernels, and can't find a good commit.I also test it on another
IVB laptop, and this issue also exists.
Bug separated from: Bug #65287 - [IVB regression dp] *ERROR* mismatch in
adjusted_mode.flags (expected 1, found 0)

lspci:
--------------------
00:02.0 VGA compatible controller: Intel Corporation Device 0162 (rev 04)

Reproduce steps:
--------------------
1. boot up machine 
2. check the dmesg

-- 
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/20130701/54e84ab9/attachment.html>