[Bug 59408] New: [ivb] memory corruption after kexec
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jan 15 02:34:18 PST 2013
https://bugs.freedesktop.org/show_bug.cgi?id=59408
Priority: medium
Bug ID: 59408
Assignee: intel-gfx-bugs at lists.freedesktop.org
Summary: [ivb] memory corruption after kexec
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: All
Reporter: jirislaby at gmail.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Intel
Product: DRI
Created attachment 73071
--> https://bugs.freedesktop.org/attachment.cgi?id=73071&action=edit
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.
--
You are receiving this mail because:
You are the QA Contact 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/20130115/efb01832/attachment.html>
More information about the intel-gfx-bugs
mailing list