<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [Baytrail-M] Machine boot up with "Call Trace""
href="https://bugs.freedesktop.org/show_bug.cgi?id=69397">69397</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[Baytrail-M] Machine boot up with "Call Trace"
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>yangweix.shui@intel.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=85887" name="attach_85887" title="dmesg: boot up with call trace">attachment 85887</a> <a href="attachment.cgi?id=85887&action=edit" title="dmesg: boot up with call trace">[details]</a></span>
dmesg: boot up with call trace
Environment:
--------------------
Kernel: (drm-intel-next-queued)6c4a8962a4a078cacfc8eb5d4bd79f6343b8cd7a
Author: Jesse Barnes <<a href="mailto:jbarnes@virtuousgeek.org">jbarnes@virtuousgeek.org</a>>
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 in dmesg when machine
boot up. 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.
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
...............
...............</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>