<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 --- - [ivb] memory corruption after kexec"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59408">59408</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[ivb] memory corruption after kexec
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jirislaby@gmail.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=73071" name="attach_73071" title="lspci -vvnnxxxs 2.0">attachment 73071</a> <a href="attachment.cgi?id=73071&action=edit" title="lspci -vvnnxxxs 2.0">[details]</a></span>
lspci -vvnnxxxs 2.0
Using KMS, when I kexec from kernel 3.7.2 (to the same one), memory gets
corrupted. I see 0x0720 (white space on a black background) all over the
structures. I do not start X at all. This is a pure fb console.
My IOMMU also complains in the kexec'ed kernel:
dmar: DRHD: handling fault status reg 3
dmar: DMAR:[DMA Read] Request device [00:02.0] fault addr fffff000
DMAR:[fault reason 06] PTE Read access is not set
This happens until i915 is loaded in the new kernel:
dmar: DRHD: handling fault status reg 3
dmar: DMAR:[DMA Read] Request device [00:02.0] fault addr ff34c000
DMAR:[fault reason 06] PTE Read access is not set
[drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5
fbcon: inteldrmfb (fb0) is primary device
<here it stops to access invalid memory>
There is no pci_driver->shutdown method and there apparently should be one that
stops the card in some manner. I tried to add the .shutdown hook which did the
same as .remove, but it had no effect. It was a shot in the dark though.</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>
</ul>
</body>
</html>