<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 --- - System hangs at X startup on Dell Venue 8 Pro (valleyview / baytrail tablet)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73133">73133</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>chris@chris-wilson.co.uk
</td>
</tr>
<tr>
<th>Summary</th>
<td>System hangs at X startup on Dell Venue 8 Pro (valleyview / baytrail tablet)
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>blocker
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>awilliam@redhat.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86 (IA32)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>Driver/intel
</td>
</tr>
<tr>
<th>Product</th>
<td>xorg
</td>
</tr></table>
<p>
<div>
<pre>After <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [BYT] Modesetting on Dell Venue 8 Pro (Bay Trail) produces garbled output (3.11, 3.12) or blank screen (3.13)"
href="show_bug.cgi?id=71977">https://bugs.freedesktop.org/show_bug.cgi?id=71977</a> , this is the next
problem I'm hitting with graphics on the Dell Venue 8 Pro, a vlv /
baytrail-based tablet. It's pretty simple: if I try and start X with
modesetting enabled, the system hangs completely.
I've checked, and there's nothing useful in any log (X log or journal), even if
I boot with drm.debug=15 . If I boot to runlevel 3 and run 'startx', all I see
is the regular X startup process begins and when it loads the GLX extension,
the system flat hangs. It's always right after GLX extension loads, for
whatever that's worth. When I say 'hangs', I mean I can't get a response to
anything - ctrl-c, ctrl-alt-f2, magic keys, nothing does anything. I can't
check if the system responds to pings as the wireless adapter doesn't work.
I'm sure you'd want more info to debug this, but I'm not sure how I can get any
more! Ideas are welcome.
X starts up fine on the system with modesetting disabled, though of course
that's a very different path and uses a fallback X driver.
Note that I'm doing a 32-bit UEFI boot, which is somewhat unusual and may
relate somehow. All these vlv / baytrail systems have 32-bit UEFI firmwares
(and somewhere, mjg59 is weeping into his gin), so I've hacked up Fedora
somewhat to be capable of 32-bit UEFI boot.
My current test images are built from Fedora Rawhide, which has a very recent X
stack and kernel:
xorg-x11-server-common-1.14.99.904-1.fc21.x86_64
xorg-x11-drv-intel-2.21.15-12.fc21
libdrm-2.4.50-1.fc21.x86_64
mesa-dri-drivers-10.0.1-1.20131220.fc21.x86_64
kernel-3.13.0-0.rc5.git0.1.fc21.x86_64</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>