69248 – [Baytrail-M] mismatch in clock for eDP

Bug 69248 - [Baytrail-M] mismatch in clock for eDP

Summary: [Baytrail-M] mismatch in clock for eDP

Status:	CLOSED FIXED

Alias:	None

Product:	DRI
Classification:	Unclassified
Component:	DRM/Intel (show other bugs)
Version:	unspecified
Hardware:	Other All

Importance:	medium major
Assignee:	Jesse Barnes
QA Contact:	Intel GFX Bugs mailing list

URL:
Whiteboard:
Keywords:

Duplicates (1):	69808 (view as bug list)
Depends on:
Blocks:

Reported:	2013-09-12 03:45 UTC by shui yangwei
Modified:	2017-10-06 14:43 UTC (History)
CC List:	1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg: boot up with error and call trace (97.88 KB, text/plain) 2013-09-12 03:45 UTC, shui yangwei	no flags	Details
dmesg: disable eDP (81.38 KB, text/plain) 2013-09-13 02:46 UTC, shui yangwei	no flags	Details
View All

Description shui yangwei 2013-09-12 03:45:23 UTC

Created attachment 85687 [details]
dmesg: boot up with error and call trace

Environment:
--------------------
Kernel: (drm-intel-next-queued)6c4a8962a4a078cacfc8eb5d4bd79f6343b8cd7a
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Tue Sep 10 14:54:42 2013 -0700
    drm/i915/vlv: re-enable hotplug detect based probing on VLV/BYT


lspci:
--------------------
00:02.0 VGA compatible controller: Intel Corporation ValleyView Gen7 (rev 0a)


Description:
--------------------
Test with latest -next-queued kernel, there's call trace and error in dmesg. I tested other IVB platform, there's not this issue. Older kernels also reproduceable. We are testing Baytrail machine recently, and it might not be a regression. I append the dmesg here, and if there's something needed, I'm glad to support you.

Error:
--------------------
[    2.710082] [drm:valleyview_enable_rps] *ERROR* GT fifo had a previous error 10
[    2.771175] [drm:intel_pipe_config_compare] *ERROR* mismatch in clock (expected 138780, found 0)


Call Trace:
--------------------
[    2.771165] [drm:i9xx_crtc_clock_get], Unknown DPLL mode 00000000 in programm
ed mode
[    2.771175] [drm:intel_pipe_config_compare] *ERROR* mismatch in clock (expect
ed 138780, found 0)
[    2.771178] ------------[ cut here ]------------
[    2.771221] WARNING: CPU: 1 PID: 1151 at drivers/gpu/drm/i915/intel_display.c
:8783 check_crtc_state+0x6d6/0x71d [i915]()
[    2.771222] pipe state doesn't match!
[    2.771229] Modules linked in: i915(+) video button drm_kms_helper drm acpi_c
pufreq mperf freq_table
[    2.771233] CPU: 1 PID: 1151 Comm: udevd Not tainted 3.11.0-rc7_drm-intel-nex
t-queued_6c4a89_20130911_+ #8370
[    2.771237]  0000000000000000 0000000000000009 ffffffff816ee0bb ffff88006feb5
2a8
[    2.771240]  ffffffff81032101 ffff88006feb52a0 ffffffffa008a8a5 0000000000000
000
[    2.771242]  ffff8800742a7000 ffff880004d58800 ffff88006feb5328 ffff8800742a7
6d0
[    2.771243] Call Trace:
[    2.771251]  [<ffffffff816ee0bb>] ? dump_stack+0x41/0x51
[    2.771256]  [<ffffffff81032101>] ? warn_slowpath_common+0x73/0x8b
.........
.........

Comment 1 Daniel Vetter 2013-09-12 08:32:08 UTC

Ok, I think we should track the "*ERROR* mismatch in clock" error here (the backtrace is just the 2nd part of that error, see the backtrace triaging BKM in the QA wiki).

Does this only happen when you have eDP enabled, or does this also happen when you have eDP disabled, but VGA output enabled?

Comment 2 shui yangwei 2013-09-13 02:46:19 UTC

Created attachment 85747 [details]
dmesg: disable eDP

(In reply to comment #1)
> Ok, I think we should track the "*ERROR* mismatch in clock" error here (the
> backtrace is just the 2nd part of that error, see the backtrace triaging BKM
> in the QA wiki).
> 
> Does this only happen when you have eDP enabled, or does this also happen
> when you have eDP disabled, but VGA output enabled?

If eDP disabled, no matter whether VGA enabled or not ,there's also call_trace and error, but "[drm:intel_pipe_config_compare] *ERROR* mismatch in clock" disappeared. 



Error:
--------------------
[    4.713728] [drm:valleyview_enable_rps] *ERROR* GT fifo had a previous error 10

Call Trace:
--------------------
[    2.672633] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing gene
ric driver
[    2.672973] Console: switching to colour dummy device 80x25
[    2.691967] i915 0000:00:02.0: setting latency timer to 64
[    2.760073] [drm:intel_detect_pch], No PCH found?
[    2.760338] INFO: trying to register non-static key.
[    2.760351] the code is fine but needs lockdep annotation.
[    2.760358] turning off the locking correctness validator.
[    2.760369] CPU: 0 PID: 1191 Comm: systemd-udevd Not tainted 3.11.0-rc7_drm-i
ntel-next-queued_e14c68_20130912+ #1
[    2.760381] Hardware name: Intel Corp. VALLEYVIEW B2 PLATFORM/NOTEBOOK, BIOS
BBAYCRB1.X64.0055.R31.1308081542 BBAY_X64_R_V0055_31 08/08/2013
[    2.760394]  0000000000000000 ffff88003f9f16a8 ffffffff817d020f 0000000000000
006
[    2.760409]  ffffffff82859810 ffff88003f9f1778 ffffffff81089328 0000000000000006
[    2.760422]  0000000700046e00 ffffffff828a7470 0000000000000000 ffffffff00000000
[    2.760436] Call Trace:
[    2.760449]  [<ffffffff817d020f>] dump_stack+0x46/0x58
[    2.760465]  [<ffffffff81089328>] __lock_acquire+0x8b4/0x183b
[    2.760477]  [<ffffffff8108b004>] ? trace_hardirqs_on_caller+0x142/0x19e
[    2.760490]  [<ffffffff8108b06d>] ? trace_hardirqs_on+0xd/0xf
[    2.760501]  [<ffffffff8104fb0d>] ? __flush_work+0x3a/0x1cc
[    2.760513]  [<ffffffff8107b4ea>] ? vprintk_emit+0x453/0x47f
[    2.760524]  [<ffffffff8108a7b3>] lock_acquire+0xcc/0x106
[    2.760534]  [<ffffffff8104fd30>] ? flush_work+0x5/0x5a
[    2.760545]  [<ffffffff8108ae96>] ? mark_held_locks+0xce/0xfa
[    2.760556]  [<ffffffff8104fd61>] flush_work+0x36/0x5a
...............
...............

Comment 3 Daniel Vetter 2013-09-13 08:05:57 UTC

(In reply to comment #2)
> If eDP disabled, no matter whether VGA enabled or not ,there's also
> call_trace and error, but "[drm:intel_pipe_config_compare] *ERROR* mismatch
> in clock" disappeared. 

Thanks, I've updated the summary.

> Error:
> --------------------
> [    4.713728] [drm:valleyview_enable_rps] *ERROR* GT fifo had a previous
> error 10

That's a different bug, can you please file a new report for it?

> Call Trace:
> --------------------
> [    2.672633] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing
> gene
> ric driver
> [    2.672973] Console: switching to colour dummy device 80x25
> [    2.691967] i915 0000:00:02.0: setting latency timer to 64
> [    2.760073] [drm:intel_detect_pch], No PCH found?
> [    2.760338] INFO: trying to register non-static key.
> [    2.760351] the code is fine but needs lockdep annotation.
> [    2.760358] turning off the locking correctness validator.
> [    2.760369] CPU: 0 PID: 1191 Comm: systemd-udevd Not tainted
> 3.11.0-rc7_drm-i
> ntel-next-queued_e14c68_20130912+ #1
> [    2.760381] Hardware name: Intel Corp. VALLEYVIEW B2 PLATFORM/NOTEBOOK,
> BIOS
> BBAYCRB1.X64.0055.R31.1308081542 BBAY_X64_R_V0055_31 08/08/2013
> [    2.760394]  0000000000000000 ffff88003f9f16a8 ffffffff817d020f
> 0000000000000
> 006
> [    2.760409]  ffffffff82859810 ffff88003f9f1778 ffffffff81089328
> 0000000000000006
> [    2.760422]  0000000700046e00 ffffffff828a7470 0000000000000000
> ffffffff00000000
> [    2.760436] Call Trace:
> [    2.760449]  [<ffffffff817d020f>] dump_stack+0x46/0x58
> [    2.760465]  [<ffffffff81089328>] __lock_acquire+0x8b4/0x183b
> [    2.760477]  [<ffffffff8108b004>] ? trace_hardirqs_on_caller+0x142/0x19e
> [    2.760490]  [<ffffffff8108b06d>] ? trace_hardirqs_on+0xd/0xf
> [    2.760501]  [<ffffffff8104fb0d>] ? __flush_work+0x3a/0x1cc
> [    2.760513]  [<ffffffff8107b4ea>] ? vprintk_emit+0x453/0x47f
> [    2.760524]  [<ffffffff8108a7b3>] lock_acquire+0xcc/0x106
> [    2.760534]  [<ffffffff8104fd30>] ? flush_work+0x5/0x5a
> [    2.760545]  [<ffffffff8108ae96>] ? mark_held_locks+0xce/0xfa
> [    2.760556]  [<ffffffff8104fd61>] flush_work+0x36/0x5a
> ...............
> ...............

That's again a different bug. Please file a new bug report for it.

Comment 4 shui yangwei 2013-09-16 02:06:09 UTC

(In reply to comment #3)
> (In reply to comment #2)
> > If eDP disabled, no matter whether VGA enabled or not ,there's also
> > call_trace and error, but "[drm:intel_pipe_config_compare] *ERROR* mismatch
> > in clock" disappeared. 
> 
> Thanks, I've updated the summary.
> 
> > Error:
> > --------------------
> > [    4.713728] [drm:valleyview_enable_rps] *ERROR* GT fifo had a previous
> > error 10
> 
> That's a different bug, can you please file a new report for it?
> 

Bug 69396 - [Baytrail-M] [drm:valleyview_enable_rps] *ERROR* GT fifo had a previous error 10

> > Call Trace:
> > --------------------
> > [    2.672633] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing
> > gene
> > ric driver
> > [    2.672973] Console: switching to colour dummy device 80x25
> > [    2.691967] i915 0000:00:02.0: setting latency timer to 64
> > [    2.760073] [drm:intel_detect_pch], No PCH found?
> > [    2.760338] INFO: trying to register non-static key.
> > [    2.760351] the code is fine but needs lockdep annotation.
> > [    2.760358] turning off the locking correctness validator.
> > [    2.760369] CPU: 0 PID: 1191 Comm: systemd-udevd Not tainted
> > 3.11.0-rc7_drm-i
> > ntel-next-queued_e14c68_20130912+ #1
> > [    2.760381] Hardware name: Intel Corp. VALLEYVIEW B2 PLATFORM/NOTEBOOK,
> > BIOS
> > BBAYCRB1.X64.0055.R31.1308081542 BBAY_X64_R_V0055_31 08/08/2013
> > [    2.760394]  0000000000000000 ffff88003f9f16a8 ffffffff817d020f
> > 0000000000000
> > 006
> > [    2.760409]  ffffffff82859810 ffff88003f9f1778 ffffffff81089328
> > 0000000000000006
> > [    2.760422]  0000000700046e00 ffffffff828a7470 0000000000000000
> > ffffffff00000000
> > [    2.760436] Call Trace:
> > [    2.760449]  [<ffffffff817d020f>] dump_stack+0x46/0x58
> > [    2.760465]  [<ffffffff81089328>] __lock_acquire+0x8b4/0x183b
> > [    2.760477]  [<ffffffff8108b004>] ? trace_hardirqs_on_caller+0x142/0x19e
> > [    2.760490]  [<ffffffff8108b06d>] ? trace_hardirqs_on+0xd/0xf
> > [    2.760501]  [<ffffffff8104fb0d>] ? __flush_work+0x3a/0x1cc
> > [    2.760513]  [<ffffffff8107b4ea>] ? vprintk_emit+0x453/0x47f
> > [    2.760524]  [<ffffffff8108a7b3>] lock_acquire+0xcc/0x106
> > [    2.760534]  [<ffffffff8104fd30>] ? flush_work+0x5/0x5a
> > [    2.760545]  [<ffffffff8108ae96>] ? mark_held_locks+0xce/0xfa
> > [    2.760556]  [<ffffffff8104fd61>] flush_work+0x36/0x5a
> > ...............
> > ...............
> 
> That's again a different bug. Please file a new bug report for it.

Bug 69397 - [Baytrail-M] Machine boot up with "Call Trace"



OK, I reported two bugs to track each issue.

Comment 5 Daniel Vetter 2013-09-25 15:54:30 UTC

*** Bug 69808 has been marked as a duplicate of this bug. ***

Comment 6 Jesse Barnes 2013-09-25 21:46:21 UTC

Fixed by:
58fc1e077db44f7ed13943426bb38c8e2740b7cc and
75b6ef3a51672c2cb25a100860df22e3688c00a6

Comment 7 Jesse Barnes 2013-09-25 21:46:22 UTC

Fixed by:
58fc1e077db44f7ed13943426bb38c8e2740b7cc and
75b6ef3a51672c2cb25a100860df22e3688c00a6

Comment 8 shui yangwei 2013-09-26 01:52:19 UTC

OK, when eDP enabled, "[drm:intel_pipe_config_compare] *ERROR* mismatch in clock" is disappeared. Verified here.

Comment 9 Elizabeth 2017-10-06 14:43:13 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.