From: Stefani Seibold <stefani@seibold.net>
To: linux-kernel <linux-kernel@vger.kernel.org>,
paulo.r.zanoni@intel.com, daniel.vetter@ffwll.ch,
David.Woodhouse@intel.com, jiang.liu@linux.intel.com,
Greg KH <greg@kroah.com>
Subject: X86: kexec issues with i915 in 3.14
Date: Sun, 13 Apr 2014 22:01:39 +0200 [thread overview]
Message-ID: <1397419299.1407.18.camel@vger.seibold.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 4784 bytes --]
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.
[-- Attachment #2: kernel.config.gz --]
[-- Type: application/gzip, Size: 29126 bytes --]
next reply other threads:[~2014-04-13 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 20:01 Stefani Seibold [this message]
2014-04-14 0:28 ` Woodhouse, David
2014-04-14 19:49 ` Stefani Seibold
2014-04-15 8:54 ` Jiang Liu
2014-04-15 18:51 ` Stefani Seibold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1397419299.1407.18.camel@vger.seibold.net \
--to=stefani@seibold.net \
--cc=David.Woodhouse@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=greg@kroah.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulo.r.zanoni@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®