Bug 66444 - [IVB Apple MacBook pro] dmesg of machine boot up with "call trace" and "*ERROR* mismatch in clock (expected 28319, found 0"
Summary: [IVB Apple MacBook pro] dmesg of machine boot up with "call trace" and "*ERRO...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium major
Assignee: shui yangwei
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-01 09:01 UTC by shui yangwei
Modified: 2017-10-06 14:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
dmesg: boot up with call trace and error (77.02 KB, text/plain)
2013-07-01 09:01 UTC, shui yangwei 		no flags Details
dmesg: boot up with call trace and error on IVB (Apple Macbook Pro) (115.15 KB, text/plain)
2013-08-16 08:35 UTC, shui yangwei 		no flags Details
View All

Description shui yangwei 2013-07-01 09:01:39 UTC 
Created attachment 81792 [details]
dmesg: boot up with call trace and error

Environment:
--------------------
Kernel: (drm-intel-next-queued)b110d88135c7aa43022c8f083079ba0e15737cc8
Author: Jesse Barnes <jbarnes@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
Comment 1 Daniel Vetter 2013-07-01 09:04:47 UTC 
Clock mismatch, one for Jesse!
Comment 2 Daniel Vetter 2013-07-01 17:43:05 UTC 
Jesse provided a fixup which I've squashed in. This should work now in latest -nightly.
Comment 3 shui yangwei 2013-07-02 02:16:01 UTC 
(In reply to comment #2)
> Jesse provided a fixup which I've squashed in. This should work now in
> latest -nightly.

Yeah, the dirty message and "call trace" really disappeared. I verified here.
Comment 4 Sedat Dilek 2013-07-02 05:38:33 UTC 
Those patches are these ones (see [1] and [2]):

   [1/2] drm/i915: fixup messages in pipe_config_compare
   [2/2] drm/i915: get clock config when checking CRTC state too

...and fixes also a problem I reported against Linux-Next (next-20130701), see thread in [3].

- Sedat -

[1] https://patchwork.kernel.org/patch/2809031/
[2] https://patchwork.kernel.org/patch/2809021/
[3] http://marc.info/?t=137266873000004&r=1&w=2
Comment 5 shui yangwei 2013-08-16 08:35:22 UTC 
Created attachment 84129 [details]
dmesg: boot up with call trace and error on IVB (Apple Macbook Pro)

I just find this bug reproduced, and I appended the dmesg here. I test it on the Apple MacBook Pro(also IVB platform).
Comment 6 Daniel Vetter 2013-08-18 17:50:53 UTC 
Nope, the calltraces in the new dmesg are a different issue. See the BKM about filing bugs about calltraces in the kernel. Please file a new bug report for those issues.
Comment 7 Elizabeth 2017-10-06 14:45:23 UTC 
Closing old verified.

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.