<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:lantw44@gmail.com" title="Ting-Wei Lan <lantw44@gmail.com>"> <span class="fn">Ting-Wei Lan</span></a>
</span> changed
<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [xen iommu] After upgrading to Linux 3.19, desktop no longer works in Xen 4.5.0 dom0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90037">bug 90037</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>REOPENED
</td>
</tr>
<tr>
<td style="text-align:right;">Assignee</td>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
<td>lantw44@gmail.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [xen iommu] After upgrading to Linux 3.19, desktop no longer works in Xen 4.5.0 dom0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90037#c25">Comment # 25</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [xen iommu] After upgrading to Linux 3.19, desktop no longer works in Xen 4.5.0 dom0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90037">bug 90037</a>
from <span class="vcard"><a class="email" href="mailto:lantw44@gmail.com" title="Ting-Wei Lan <lantw44@gmail.com>"> <span class="fn">Ting-Wei Lan</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=141536" name="attach_141536" title="dmesg (Xen 4.10.1 + Linux 4.19.0-rc2+) #2">attachment 141536</a> <a href="attachment.cgi?id=141536&action=edit" title="dmesg (Xen 4.10.1 + Linux 4.19.0-rc2+) #2">[details]</a></span>
dmesg (Xen 4.10.1 + Linux 4.19.0-rc2+) #2
This is the log from the test of the second time. After the first test, I
rebooted the system with 'iommu=no-igfx' set on Xen command line and hoped it
could boot normally. However, it stopped and dropped into a shell in initramfs
because the fsck on rootfs failed. I manually performed fsck and the system
seemed to boot up normally to the desktop. I assumed all filesystem troubles
caused by the previous test were now cleaned up, and I rebooted the system to
do the second test.
This time I remebered to add 'ucode=-1' to Xen command line to let it load
Intel CPU microcode update. The version of the microcode update file is
'revision 0x11, date = 2018-05-08'. The kernel printed a lot of repeated
messages in this test and the log quickly grew over 30M. I reset the system
from Xen once I saw it printed messages endlessly. Because of the large file
size, I only uploaded the first 20000 lines of the log here.</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 the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>