linux-kernel - X86: kexec issues with i915 in 3.14

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1397419299.1407.18.camel@vger.seibold.net>
Date:	Sun, 13 Apr 2014 22:01:39 +0200
From:	Stefani Seibold <stefani@...bold.net>
To:	linux-kernel <linux-kernel@...r.kernel.org>,
	paulo.r.zanoni@...el.com, daniel.vetter@...ll.ch,
	David.Woodhouse@...el.com, jiang.liu@...ux.intel.com,
	Greg KH <greg@...ah.com>
Subject: X86: kexec issues with i915 in 3.14

Rebooting my kernel vanilla kernel 3.14 will fail with tons of kernel
log messages:

[    0.262754] IOMMU: Setting identity map for device 0000:00:1a.0 [0x7c45f000 - 0x7c46bfff]
[    0.262780] IOMMU: Setting identity map for device 0000:00:14.0 [0x7c45f000 - 0x7c46bfff]
[    0.262798] IOMMU: Prepare 0-16MiB unity mapping for LPC
[    0.262807] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff]
[    0.262948] PCI-DMA: Intel(R) Virtualization Technology for Directed I/O
[    0.262948] dmar: DRHD: handling fault status reg 3
[    0.262951] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr ffffe000 
DMAR:[fault reason 05] PTE Write access is not set
[    0.262955] dmar: DRHD: handling fault status reg 3
[    0.262959] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr fff3c000 
DMAR:[fault reason 05] PTE Write access is not set
[    0.262965] dmar: DRHD: handling fault status reg 3
[    0.262968] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr ffe4a000 
DMAR:[fault reason 05] PTE Write access is not set
[    0.262974] dmar: DRHD: handling fault status reg 3
[    0.262976] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr fff6f000 
DMAR:[fault reason 05] PTE Write access is not set
[    0.262983] dmar: DRHD: handling fault status reg 3
[    0.262985] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr ffe8c000 
DMAR:[fault reason 05] PTE Write access is not set
[    0.262991] dmar: DRHD: handling fault status reg 3
[    0.262994] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr fffb3000 
DMAR:[fault reason 05] PTE Write access is not set
[    0.263000] dmar: DRHD: handling fault status reg 3
[    0.263002] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr ffecf000 
DMAR:[fault reason 05] PTE Write access is not set
[    0.263009] dmar: DRHD: handling fault status reg 3
[    0.263011] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr ffffd000

this message repeats more the 21000 times. After this the kernel
messages continues with

[    0.683267] fbcon: inteldrmfb (fb0) is primary device
[    0.864123] Console: switching to colour frame buffer device 320x90
[    0.880630] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    0.880632] i915 0000:00:02.0: registered panic notifier
[    0.881077] ACPI Exception: AE_NOT_FOUND, Evaluating _DOD (20131218/video-1245)
[    0.881081] ACPI: Video Device [PEGN] (multi-head: no  rom: yes  post: no)
[    0.881134] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/LNXVIDEO:00/input/input2
[    0.888055] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    0.888266] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input3
[    0.888289] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[    0.888571] mei_me 0000:00:16.0: irq 57 for MSI/MSI-X
[    0.889545] rtsx_pci 0000:3e:00.0: irq 58 for MSI/MSI-X
[    0.889559] rtsx_pci 0000:3e:00.0: rtsx_pci_acquire_irq: pcr->msi_en = 1, pci->irq = 58
[    0.890098] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182f conflicts with OpRegion 0x0000000000001800-0x000000000000187f (\PMIO) (20131218/utaddress-258)
[    0.890104] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    0.890107] ACPI Warning: SystemIO range 0x0000000000001c30-0x0000000000001c3f conflicts with OpRegion 0x0000000000001c00-0x0000000000001c3f (\GPRL) (20131218/utaddress-258)
[    0.890111] ACPI Warning: SystemIO range 0x0000000000001c30-0x0000000000001c3f conflicts with OpRegion 0x0000000000001c00-0x0000000000001fff (\GPR_) (20131218/utaddress-258)
[    0.890114] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    0.890115] ACPI Warning: SystemIO range 0x0000000000001c00-0x0000000000001c2f conflicts with OpRegion 0x0000000000001c00-0x0000000000001c3f (\GPRL) (20131218/utaddress-258)
[    0.890118] ACPI Warning: SystemIO range 0x0000000000001c00-0x0000000000001c2f conflicts with OpRegion 0x0000000000001c00-0x0000000000001fff (\GPR_) (20131218/utaddress-258)
[    0.890122] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    0.890123] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    0.890215] ahci 0000:00:1f.2: version 3.0

lspci give me for the device 00:02.0:

VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)

After this the system seams in normal condition, X is starting and i can
log on and use the machine. Any idea? 

But mostly the machine will look up and i see only garbage on the
screen.

I will attach my kernel config.


Download attachment "kernel.config.gz" of type "application/gzip" (29126 bytes)