[Bug 69248] [Baytrail-M] Boot up with "[drm:intel_pipe_config_compare] *ERROR* mismatch in clock" and "Call Trace"
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Sep 12 19:46:19 PDT 2013
https://bugs.freedesktop.org/show_bug.cgi?id=69248
shui yangwei <yangweix.shui at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Assignee|intel-gfx-bugs at lists.freede |yangweix.shui at intel.com
|sktop.org |
--- Comment #2 from shui yangwei <yangweix.shui at intel.com> ---
Created attachment 85747
--> https://bugs.freedesktop.org/attachment.cgi?id=85747&action=edit
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
...............
...............
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list 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/20130913/d17feb17/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list