[PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Takao Indoh]

These patches reset PCIe devices at boot time to address DMA problem on
kdump with iommu. When "reset_devices" is specified, a hot reset is
triggered on each PCIe root port and downstream port to reset its
downstream endpoint.

Background:
A kdump problem about DMA has been discussed for a long time. That is,
when a kernel is switched to the kdump kernel, DMA derived from first
kernel affects second kernel. Especially this problem surfaces when
iommu is used for PCI passthrough on KVM guest. In the case of the
machine I use, when intel_iommu=on is specified, DMAR error is detected
in kdump kernel and PCI SERR is also detected. Finally kdump fails
because some devices does not work correctly.

The root cause is that ongoing DMA from first kernel causes DMAR fault
because page table of DMAR is initialized while kdump kernel is booting
up. Therefore to solve this problem DMA needs to be stopped before DMAR
is initialized at kdump kernel boot time. By these patches, PCIe devices
are reset by hot reset and its DMA is stopped when reset_devices is
specified. One problem of this solution is that the monitor blacks out
when VGA controller is reset. So this patch does not reset the port
whose child endpoint is VGA device.

What I tried:
- Clearing bus master bit and INTx disable bit at boot time
    This did not solve this problem. I still got DMAR error on devices.
- Resetting devices in fixup_final(v1 patch)
    DMAR error disappeared, but sometimes PCI SERR was detected. This
    is well explained here.
    https://lkml.org/lkml/2012/9/9/245
    This PCI SERR seems to be related to interrupt remapping.
- Clearing bus master in setup_arch() and resetting devices in
  fixup_final
    Neither DMAR error nor PCI SERR occurred. But on certain machine
    kdump kernel hung up when resetting devices. It seems to be a
    problem specific to the platform.
- Resetting devices in setup_arch() (v2 and later patch)
    This solution solves all problems I found so far.

Changelog:
v7:
Update Yinghai's dummy-pci patch with macros in linux/pci.h, and fix
some bugs

v6:
Rewrite using Yinghai's dummy-pci patch
https://lkml.org/lkml/2012/11/13/118

v5:
Do bus reset after all devices are scanned and its config registers are
saved. This fixes a bug that config register is accessed without delay
after reset.
https://lkml.org/lkml/2012/10/17/47

v4:
Reduce waiting time after resetting devices. A previous patch does reset
like this:
  for (each device) {
    save config registers
    reset
    wait for 500 ms
    restore config registers
  }

If there are N devices to be reset, it takes N*500 ms. On the other
hand, the v4 patch does:
  for (each device) {
    save config registers
    reset
  }
  wait 500 ms
  for (each device) {
    restore config registers
  }
Though it needs more memory space to save config registers, the waiting
time is always 500ms.
https://lkml.org/lkml/2012/10/15/49

v3:
Move alloc_bootmem and free_bootmem to early_reset_pcie_devices so that
they are called only once.
https://lkml.org/lkml/2012/10/10/57

v2:
Reset devices in setup_arch() because reset need to be done before
interrupt remapping is initialized.
https://lkml.org/lkml/2012/10/2/54

v1:
Add fixup_final quirk to reset PCIe devices
https://lkml.org/lkml/2012/8/3/160

Takao Indoh (5):
  x86, pci: add dummy pci device for early stage
  PCI: Define the maximum number of PCI function
  Make reset_devices available at early stage
  x86, pci: Reset PCIe devices at boot time
  x86, pci: Enable PCI INTx when MSI is disabled

 arch/x86/include/asm/pci-direct.h |    3 +
 arch/x86/kernel/setup.c           |    3 +
 arch/x86/pci/common.c             |    4 +-
 arch/x86/pci/early.c              |  315 +++++++++++++++++++++++++++++++++++++
 include/linux/pci.h               |    2 +
 init/main.c                       |    4 +-
 6 files changed, 328 insertions(+), 3 deletions(-)

[PATCH v7 1/5] x86, pci: add dummy pci device for early stage

[Takao Indoh]

So we can pass pci_dev *dev to reuse some generic pci functions.

The original patch was written by Yinghai Lu.

Signed-off-by: Takao Indoh <indou.takao@jp.fujitsu.com>
---
 arch/x86/include/asm/pci-direct.h |    2 +
 arch/x86/pci/early.c              |   74 +++++++++++++++++++++++++++++++++++++
 2 files changed, 76 insertions(+), 0 deletions(-)

diff --git a/arch/x86/include/asm/pci-direct.h b/arch/x86/include/asm/pci-direct.h
index b1e7a45..b6360d3 100644
--- a/arch/x86/include/asm/pci-direct.h
+++ b/arch/x86/include/asm/pci-direct.h
@@ -18,4 +18,6 @@ extern int early_pci_allowed(void);
 extern unsigned int pci_early_dump_regs;
 extern void early_dump_pci_device(u8 bus, u8 slot, u8 func);
 extern void early_dump_pci_devices(void);
+
+struct pci_dev *get_early_pci_dev(int num, int slot, int func);
 #endif /* _ASM_X86_PCI_DIRECT_H */
diff --git a/arch/x86/pci/early.c b/arch/x86/pci/early.c
index d1067d5..024def7 100644
--- a/arch/x86/pci/early.c
+++ b/arch/x86/pci/early.c
@@ -109,3 +109,77 @@ void early_dump_pci_devices(void)
 		}
 	}
 }
+
+static __init int
+early_pci_read(struct pci_bus *bus, unsigned int devfn, int where,
+			int size, u32 *value)
+{
+	int num, slot, func;
+
+	num = bus->number;
+	slot = PCI_SLOT(devfn);
+	func = PCI_FUNC(devfn);
+	switch (size) {
+	case 1:
+		*value = read_pci_config_byte(num, slot, func, where);
+		break;
+	case 2:
+		*value = read_pci_config_16(num, slot, func, where);
+		break;
+	case 4:
+		*value = read_pci_config(num, slot, func, where);
+		break;
+	}
+
+	return 0;
+}
+
+static __init int
+early_pci_write(struct pci_bus *bus, unsigned int devfn, int where,
+			int size, u32 value)
+{
+	int num, slot, func;
+
+	num = bus->number;
+	slot = PCI_SLOT(devfn);
+	func = PCI_FUNC(devfn);
+	switch (size) {
+	case 1:
+		write_pci_config_byte(num, slot, func, where, (u8)value);
+		break;
+	case 2:
+		write_pci_config_16(num, slot, func, where, (u16)value);
+		break;
+	case 4:
+		write_pci_config(num, slot, func, where, (u32)value);
+		break;
+	}
+
+	return 0;
+}
+
+static __initdata struct pci_ops pci_early_ops = {
+	.read  = early_pci_read,
+	.write = early_pci_write,
+};
+static __initdata struct pci_bus pci_early_bus = {
+	.ops = &pci_early_ops,
+};
+static __initdata char pci_early_init_name[8];
+static __initdata struct pci_dev pci_early_dev;
+
+__init struct pci_dev *get_early_pci_dev(int num, int slot, int func)
+{
+	struct pci_dev *pdev;
+
+	pdev = &pci_early_dev;
+	memset(pdev, 0, sizeof(*pdev));
+
+	pdev->bus = &pci_early_bus,
+	pdev->dev.init_name = pci_early_init_name;
+	pdev->bus->number = num;
+	pdev->devfn = PCI_DEVFN(slot, func);
+	sprintf((char *)pdev->dev.init_name, "%02x:%02x.%01x", num, slot, func);
+
+	return pdev;
+}
-- 
1.7.1

[PATCH v7 2/5] PCI: Define the maximum number of PCI function

[Takao Indoh]

Define the maximum number of PCI function so that PCI functions can be
enumerated without using "8".

Signed-off-by: Takao Indoh <indou.takao@jp.fujitsu.com>
---
 include/linux/pci.h |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/include/linux/pci.h b/include/linux/pci.h
index ee21795..eca3231 100644
--- a/include/linux/pci.h
+++ b/include/linux/pci.h
@@ -35,6 +35,8 @@
 /* Include the ID list */
 #include <linux/pci_ids.h>
 
+#define PCI_MAX_FUNCTIONS 8
+
 /* pci_slot represents a physical slot */
 struct pci_slot {
 	struct pci_bus *bus;		/* The bus this slot is on */
-- 
1.7.1

[PATCH v7 3/5] Make reset_devices available at early stage

[Takao Indoh]

Change reset_devices from __setup to early_param so this parameter is
available at early stage.

Signed-off-by: Takao Indoh <indou.takao@jp.fujitsu.com>
---
 init/main.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/init/main.c b/init/main.c
index e33e09d..f2b24cb 100644
--- a/init/main.c
+++ b/init/main.c
@@ -144,10 +144,10 @@ EXPORT_SYMBOL(reset_devices);
 static int __init set_reset_devices(char *str)
 {
 	reset_devices = 1;
-	return 1;
+	return 0;
 }
 
-__setup("reset_devices", set_reset_devices);
+early_param("reset_devices", set_reset_devices);
 
 static const char * argv_init[MAX_INIT_ARGS+2] = { "init", NULL, };
 const char * envp_init[MAX_INIT_ENVS+2] = { "HOME=/", "TERM=linux", NULL, };
-- 
1.7.1

[PATCH v7 4/5] x86, pci: Reset PCIe devices at boot time

[Takao Indoh]

This patch resets PCIe devices at boot time when "reset_devices" is
specified.

Kdump with intel_iommu=on fails becasue ongoing DMA from first kernel
causes DMAR fault when page table of DMAR is initialized while kdump
kernel is booting up. To solve this problem, this patch resets PCIe
devices during boot to stop its DMA.

Signed-off-by: Takao Indoh <indou.takao@jp.fujitsu.com>
---
 arch/x86/include/asm/pci-direct.h |    1 +
 arch/x86/kernel/setup.c           |    3 +
 arch/x86/pci/early.c              |  241 +++++++++++++++++++++++++++++++++++++
 3 files changed, 245 insertions(+), 0 deletions(-)

diff --git a/arch/x86/include/asm/pci-direct.h b/arch/x86/include/asm/pci-direct.h
index b6360d3..5620070 100644
--- a/arch/x86/include/asm/pci-direct.h
+++ b/arch/x86/include/asm/pci-direct.h
@@ -18,6 +18,7 @@ extern int early_pci_allowed(void);
 extern unsigned int pci_early_dump_regs;
 extern void early_dump_pci_device(u8 bus, u8 slot, u8 func);
 extern void early_dump_pci_devices(void);
+extern void early_reset_pcie_devices(void);
 
 struct pci_dev *get_early_pci_dev(int num, int slot, int func);
 #endif /* _ASM_X86_PCI_DIRECT_H */
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index ca45696..2e7928e 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -1001,6 +1001,9 @@ void __init setup_arch(char **cmdline_p)
 	generic_apic_probe();
 
 	early_quirks();
+#ifdef CONFIG_PCI
+	early_reset_pcie_devices();
+#endif
 
 	/*
 	 * Read APIC and some other early information from ACPI tables.
diff --git a/arch/x86/pci/early.c b/arch/x86/pci/early.c
index 024def7..ff737f3 100644
--- a/arch/x86/pci/early.c
+++ b/arch/x86/pci/early.c
@@ -1,5 +1,6 @@
 #include <linux/kernel.h>
 #include <linux/pci.h>
+#include <linux/bootmem.h>
 #include <asm/pci-direct.h>
 #include <asm/io.h>
 #include <asm/pci_x86.h>
@@ -183,3 +184,243 @@ __init struct pci_dev *get_early_pci_dev(int num, int slot, int func)
 
 	return pdev;
 }
+
+struct pcie_dev {
+	int cap;	/* position of PCI Express capability */
+	int flags;	/* PCI_EXP_FLAGS */
+
+	/* saved configration register */
+	u32 pci_cfg[16];
+	u16 pcie_cfg[7];
+};
+
+struct pcie_port {
+	struct list_head dev;
+	u8 bus;
+	u8 slot;
+	u8 func;
+	u8 secondary;
+	struct pcie_dev child[PCI_MAX_FUNCTIONS];
+};
+
+static __initdata LIST_HEAD(device_list);
+
+static void __init early_udelay(int loops)
+{
+	while (loops--) {
+		/* Approximately 1 us */
+		native_io_delay();
+	}
+}
+
+static void __init do_reset(u8 bus, u8 slot, u8 func)
+{
+	struct pci_dev *dev;
+	u16 ctrl;
+
+	dev = get_early_pci_dev(bus, slot, func);
+
+	printk(KERN_INFO "pci 0000:%02x:%02x.%d reset\n", bus, slot, func);
+
+	/* Assert Secondary Bus Reset */
+	pci_read_config_word(dev, PCI_BRIDGE_CONTROL, &ctrl);
+	ctrl |= PCI_BRIDGE_CTL_BUS_RESET;
+	pci_write_config_word(dev, PCI_BRIDGE_CONTROL, ctrl);
+
+	/*
+	 * PCIe spec requires software to ensure a minimum reset duration
+	 * (Trst == 1ms). We have here 5ms safety margin because early_udelay
+	 * is not precise.
+	 */
+	early_udelay(5000);
+
+	/* De-assert Secondary Bus Reset */
+	ctrl &= ~PCI_BRIDGE_CTL_BUS_RESET;
+	pci_write_config_word(dev, PCI_BRIDGE_CONTROL, ctrl);
+}
+
+static void __init save_state(u8 bus, u8 slot, u8 func, struct pcie_dev *pdev)
+{
+	struct pci_dev *dev;
+	int i;
+
+	dev = get_early_pci_dev(bus, slot, func);
+	dev->is_pcie = 1;
+	dev->pcie_cap = pdev->cap;
+	dev->pcie_flags_reg = pdev->flags;
+
+	printk(KERN_INFO "pci 0000:%02x:%02x.%d save state\n", bus, slot, func);
+
+	for (i = 0; i < 16; i++)
+		pci_read_config_dword(dev, i * 4, pdev->pci_cfg + i);
+	i = 0;
+	pcie_capability_read_word(dev, PCI_EXP_DEVCTL, &pdev->pcie_cfg[i++]);
+	pcie_capability_read_word(dev, PCI_EXP_LNKCTL, &pdev->pcie_cfg[i++]);
+	pcie_capability_read_word(dev, PCI_EXP_SLTCTL, &pdev->pcie_cfg[i++]);
+	pcie_capability_read_word(dev, PCI_EXP_RTCTL, &pdev->pcie_cfg[i++]);
+	pcie_capability_read_word(dev, PCI_EXP_DEVCTL2, &pdev->pcie_cfg[i++]);
+	pcie_capability_read_word(dev, PCI_EXP_LNKCTL2, &pdev->pcie_cfg[i++]);
+	pcie_capability_read_word(dev, PCI_EXP_SLTCTL2, &pdev->pcie_cfg[i++]);
+}
+
+static void __init restore_state(u8 bus, u8 slot, u8 func,
+				 struct pcie_dev *pdev)
+{
+	struct pci_dev *dev;
+	int i = 0;
+
+	dev = get_early_pci_dev(bus, slot, func);
+	dev->is_pcie = 1;
+	dev->pcie_cap = pdev->cap;
+	dev->pcie_flags_reg = pdev->flags;
+
+	printk(KERN_INFO "pci 0000:%02x:%02x.%d restore state\n",
+	       bus, slot, func);
+
+	pcie_capability_write_word(dev, PCI_EXP_DEVCTL, pdev->pcie_cfg[i++]);
+	pcie_capability_write_word(dev, PCI_EXP_LNKCTL, pdev->pcie_cfg[i++]);
+	pcie_capability_write_word(dev, PCI_EXP_SLTCTL, pdev->pcie_cfg[i++]);
+	pcie_capability_write_word(dev, PCI_EXP_RTCTL, pdev->pcie_cfg[i++]);
+	pcie_capability_write_word(dev, PCI_EXP_DEVCTL2, pdev->pcie_cfg[i++]);
+	pcie_capability_write_word(dev, PCI_EXP_LNKCTL2, pdev->pcie_cfg[i++]);
+	pcie_capability_write_word(dev, PCI_EXP_SLTCTL2, pdev->pcie_cfg[i++]);
+
+	for (i = 15; i >= 0; i--)
+		pci_write_config_dword(dev, i * 4, pdev->pci_cfg[i]);
+}
+
+static void __init find_pcie_device(unsigned bus, unsigned slot, unsigned func)
+{
+	struct pci_dev *dev;
+	int f, pcie_type, count;
+	u8 secondary, type;
+	u16 vendor;
+	u32 class;
+	struct pcie_port *port;
+	int pcie_cap[PCI_MAX_FUNCTIONS];
+	int pcie_flags[PCI_MAX_FUNCTIONS];
+
+	dev = get_early_pci_dev(bus, slot, func);
+	set_pcie_port_type(dev);
+	if (!pci_is_pcie(dev))
+		return;
+
+	pcie_type = pci_pcie_type(dev);
+	if ((pcie_type != PCI_EXP_TYPE_ROOT_PORT) &&
+	    (pcie_type != PCI_EXP_TYPE_DOWNSTREAM))
+		return;
+
+	pci_read_config_byte(dev, PCI_HEADER_TYPE, &type);
+	if ((type & 0x7f) != PCI_HEADER_TYPE_BRIDGE)
+		return;
+	pci_read_config_byte(dev, PCI_SECONDARY_BUS, &secondary);
+
+	memset(pcie_cap, 0, sizeof(pcie_cap));
+	memset(pcie_flags, 0, sizeof(pcie_flags));
+	for (count = 0, f = 0; f < PCI_MAX_FUNCTIONS; f++) {
+		dev = get_early_pci_dev(secondary, 0, f);
+		pci_read_config_word(dev, PCI_VENDOR_ID, &vendor);
+		if (vendor == 0xffff)
+			continue;
+
+		set_pcie_port_type(dev);
+		if (!pci_is_pcie(dev))
+			continue;
+
+		pcie_type = pci_pcie_type(dev);
+		if ((pcie_type == PCI_EXP_TYPE_UPSTREAM) ||
+		    (pcie_type == PCI_EXP_TYPE_PCI_BRIDGE))
+			/* Don't reset switch, bridge */
+			return;
+
+		pci_read_config_dword(dev, PCI_CLASS_REVISION, &class);
+		if ((class >> 24) == PCI_BASE_CLASS_DISPLAY)
+			/* Don't reset VGA device */
+			return;
+
+		count++;
+		pcie_cap[f] = dev->pcie_cap;
+		pcie_flags[f] = dev->pcie_flags_reg;
+	}
+
+	if (!count)
+		return;
+
+	port = (struct pcie_port *)alloc_bootmem(sizeof(struct pcie_port));
+	if (port == NULL) {
+		printk(KERN_ERR "pci 0000:%02x:%02x.%d alloc_bootmem failed\n",
+		       bus, slot, func);
+		return;
+	}
+	memset(port, 0, sizeof(*port));
+	port->bus = bus;
+	port->slot = slot;
+	port->func = func;
+	port->secondary = secondary;
+	for (f = 0; f < PCI_MAX_FUNCTIONS; f++)
+		if (pcie_cap[f]) {
+			port->child[f].cap = pcie_cap[f];
+			port->child[f].flags = pcie_flags[f];
+			save_state(secondary, 0, f, &port->child[f]);
+		}
+	list_add_tail(&port->dev, &device_list);
+}
+
+void __init early_reset_pcie_devices(void)
+{
+	unsigned bus, slot, func;
+	struct pcie_port *port, *tmp;
+	struct pci_dev *dev;
+
+	if (!early_pci_allowed() || !reset_devices)
+		return;
+
+	/*
+	 * Find PCIe port(root port and downstream port) and save config
+	 * registers of its downstream devices
+	 */
+	for (bus = 0; bus < 256; bus++) {
+		for (slot = 0; slot < 32; slot++) {
+			for (func = 0; func < PCI_MAX_FUNCTIONS; func++) {
+				u16 vendor;
+				u8 type;
+
+				dev = get_early_pci_dev(bus, slot, func);
+				pci_read_config_word(dev, PCI_VENDOR_ID,
+						     &vendor);
+				if (vendor == 0xffff)
+					continue;
+
+				pci_read_config_byte(dev, PCI_HEADER_TYPE,
+						     &type);
+				find_pcie_device(bus, slot, func);
+
+				if ((func == 0) && !(type & 0x80))
+					break;
+			}
+		}
+	}
+
+	if (list_empty(&device_list))
+		return;
+
+	/* Do bus reset */
+	list_for_each_entry(port, &device_list, dev)
+		do_reset(port->bus, port->slot, port->func);
+
+	/*
+	 * According to PCIe spec, software must wait a minimum of 100 ms
+	 * before sending a configuration request. We have 500ms safety margin
+	 * here.
+	 */
+	early_udelay(500000);
+
+	/* Restore config registers and free memory */
+	list_for_each_entry_safe(port, tmp, &device_list, dev) {
+		for (func = 0; func < PCI_MAX_FUNCTIONS; func++)
+			if (port->child[func].cap)
+				restore_state(port->secondary, 0, func,
+					      &port->child[func]);
+		free_bootmem(__pa(port), sizeof(*port));
+	}
+}
-- 
1.7.1

[PATCH v7 5/5] x86, pci: Enable PCI INTx when MSI is disabled

[Takao Indoh]

This patch enables INTx if MSI is disabled in pcibios_enable_device().
In normal case interrupt disable bit in command register is 0b on boot
time, but in case of kdump, this bit may be 1b. It causes problems of
some drivers. At leaset I confirmed mptsas driver does not work in such
a case. This patch fix this problem.

Signed-off-by: Takao Indoh <indou.takao@jp.fujitsu.com>
---
 arch/x86/pci/common.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/arch/x86/pci/common.c b/arch/x86/pci/common.c
index 720e973..2bb7ecc 100644
--- a/arch/x86/pci/common.c
+++ b/arch/x86/pci/common.c
@@ -615,8 +615,10 @@ int pcibios_enable_device(struct pci_dev *dev, int mask)
 	if ((err = pci_enable_resources(dev, mask)) < 0)
 		return err;
 
-	if (!pci_dev_msi_enabled(dev))
+	if (!pci_dev_msi_enabled(dev)) {
+		pci_intx(dev, true);
 		return pcibios_enable_irq(dev);
+	}
 	return 0;
 }
 
-- 
1.7.1

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[MUNEDA Takahiro]

On Tue, 27 Nov 2012 09:42:20 +0900 (JST),
Takao Indoh <indou.takao@jp.fujitsu.com> wrote:

> These patches reset PCIe devices at boot time to address DMA problem on
> kdump with iommu. When "reset_devices" is specified, a hot reset is
> triggered on each PCIe root port and downstream port to reset its
> downstream endpoint.
> 
> Background:
> A kdump problem about DMA has been discussed for a long time. That is,
> when a kernel is switched to the kdump kernel, DMA derived from first
> kernel affects second kernel. Especially this problem surfaces when
> iommu is used for PCI passthrough on KVM guest. In the case of the
> machine I use, when intel_iommu=on is specified, DMAR error is detected
> in kdump kernel and PCI SERR is also detected. Finally kdump fails
> because some devices does not work correctly.
> 
> The root cause is that ongoing DMA from first kernel causes DMAR fault
> because page table of DMAR is initialized while kdump kernel is booting
> up. Therefore to solve this problem DMA needs to be stopped before DMAR
> is initialized at kdump kernel boot time. By these patches, PCIe devices
> are reset by hot reset and its DMA is stopped when reset_devices is
> specified. One problem of this solution is that the monitor blacks out
> when VGA controller is reset. So this patch does not reset the port
> whose child endpoint is VGA device.
> 
> What I tried:
> - Clearing bus master bit and INTx disable bit at boot time
>      This did not solve this problem. I still got DMAR error on devices.
> - Resetting devices in fixup_final(v1 patch)
>      DMAR error disappeared, but sometimes PCI SERR was detected. This
>      is well explained here.
>      https://lkml.org/lkml/2012/9/9/245
>      This PCI SERR seems to be related to interrupt remapping.
> - Clearing bus master in setup_arch() and resetting devices in
>    fixup_final
>      Neither DMAR error nor PCI SERR occurred. But on certain machine
>      kdump kernel hung up when resetting devices. It seems to be a
>      problem specific to the platform.
> - Resetting devices in setup_arch() (v2 and later patch)
>      This solution solves all problems I found so far.

Thank you for updating a patchset.
I have a server which raises PCI Error while system is rebooting when
I set intel_iommu=on.  With v7 on top of 3.7-rc7, I don't see any PCI
Errors or other hardware related errors. So,

Tested-by: MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>

Thanks,
Takahiro

> 
> Changelog:
> v7:
> Update Yinghai's dummy-pci patch with macros in linux/pci.h, and fix
> some bugs
> 
> v6:
> Rewrite using Yinghai's dummy-pci patch
> https://lkml.org/lkml/2012/11/13/118
> 
> v5:
> Do bus reset after all devices are scanned and its config registers are
> saved. This fixes a bug that config register is accessed without delay
> after reset.
> https://lkml.org/lkml/2012/10/17/47
> 
> v4:
> Reduce waiting time after resetting devices. A previous patch does reset
> like this:
>    for (each device) {
>      save config registers
>      reset
>      wait for 500 ms
>      restore config registers
>    }
> 
> If there are N devices to be reset, it takes N*500 ms. On the other
> hand, the v4 patch does:
>    for (each device) {
>      save config registers
>      reset
>    }
>    wait 500 ms
>    for (each device) {
>      restore config registers
>    }
> Though it needs more memory space to save config registers, the waiting
> time is always 500ms.
> https://lkml.org/lkml/2012/10/15/49
> 
> v3:
> Move alloc_bootmem and free_bootmem to early_reset_pcie_devices so that
> they are called only once.
> https://lkml.org/lkml/2012/10/10/57
> 
> v2:
> Reset devices in setup_arch() because reset need to be done before
> interrupt remapping is initialized.
> https://lkml.org/lkml/2012/10/2/54
> 
> v1:
> Add fixup_final quirk to reset PCIe devices
> https://lkml.org/lkml/2012/8/3/160
> 
> Takao Indoh (5):
>    x86, pci: add dummy pci device for early stage
>    PCI: Define the maximum number of PCI function
>    Make reset_devices available at early stage
>    x86, pci: Reset PCIe devices at boot time
>    x86, pci: Enable PCI INTx when MSI is disabled
> 
>   arch/x86/include/asm/pci-direct.h |    3 +
>   arch/x86/kernel/setup.c           |    3 +
>   arch/x86/pci/common.c             |    4 +-
>   arch/x86/pci/early.c              |  315 +++++++++++++++++++++++++++++++++++++
>   include/linux/pci.h               |    2 +
>   init/main.c                       |    4 +-
>   6 files changed, 328 insertions(+), 3 deletions(-)
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Takao Indoh]

Hi,

(2012/12/21 18:59), oliver yang wrote:
>
> Hi Takao,
>
> Because I want to config the kdump in our lab, I have some questions
> about the backgroud of your patch.
>
> 1. Will you patch only work while IOMMU is enabled?

No. It always works when "reset_devices" is specified as boot parameter.


>
> 2. Looks like kdump doesn't disable DMA and interrupts in the systems,
> how can Linux make sure second kernel's memory is not corrupted by
> devices initialized by first kernel?

See purgatory/purgatory.c in kexec_tools. Before jumping into second
kernel, a part of memory is checked using sha256 digest.

Thanks,
Takao Indoh


>
>
> 2012/11/27 Takao Indoh <indou.takao@jp.fujitsu.com <mailto:indou.takao@jp.fujitsu.com>>
>
>     These patches reset PCIe devices at boot time to address DMA problem on
>     kdump with iommu. When "reset_devices" is specified, a hot reset is
>     triggered on each PCIe root port and downstream port to reset its
>     downstream endpoint.
>
>     Background:
>     A kdump problem about DMA has been discussed for a long time. That is,
>     when a kernel is switched to the kdump kernel, DMA derived from first
>     kernel affects second kernel. Especially this problem surfaces when
>     iommu is used for PCI passthrough on KVM guest. In the case of the
>     machine I use, when intel_iommu=on is specified, DMAR error is detected
>     in kdump kernel and PCI SERR is also detected. Finally kdump fails
>     because some devices does not work correctly.
>
>     The root cause is that ongoing DMA from first kernel causes DMAR fault
>     because page table of DMAR is initialized while kdump kernel is booting
>     up. Therefore to solve this problem DMA needs to be stopped before DMAR
>     is initialized at kdump kernel boot time. By these patches, PCIe devices
>     are reset by hot reset and its DMA is stopped when reset_devices is
>     specified. One problem of this solution is that the monitor blacks out
>     when VGA controller is reset. So this patch does not reset the port
>     whose child endpoint is VGA device.
>
>     What I tried:
>     - Clearing bus master bit and INTx disable bit at boot time
>          This did not solve this problem. I still got DMAR error on devices.
>     - Resetting devices in fixup_final(v1 patch)
>          DMAR error disappeared, but sometimes PCI SERR was detected. This
>          is well explained here.
>     https://lkml.org/lkml/2012/9/9/245
>          This PCI SERR seems to be related to interrupt remapping.
>     - Clearing bus master in setup_arch() and resetting devices in
>        fixup_final
>          Neither DMAR error nor PCI SERR occurred. But on certain machine
>          kdump kernel hung up when resetting devices. It seems to be a
>          problem specific to the platform.
>     - Resetting devices in setup_arch() (v2 and later patch)
>          This solution solves all problems I found so far.
>
>     Changelog:
>     v7:
>     Update Yinghai's dummy-pci patch with macros in linux/pci.h, and fix
>     some bugs
>
>     v6:
>     Rewrite using Yinghai's dummy-pci patch
>     https://lkml.org/lkml/2012/11/13/118
>
>     v5:
>     Do bus reset after all devices are scanned and its config registers are
>     saved. This fixes a bug that config register is accessed without delay
>     after reset.
>     https://lkml.org/lkml/2012/10/17/47
>
>     v4:
>     Reduce waiting time after resetting devices. A previous patch does reset
>     like this:
>        for (each device) {
>          save config registers
>          reset
>          wait for 500 ms
>          restore config registers
>        }
>
>     If there are N devices to be reset, it takes N*500 ms. On the other
>     hand, the v4 patch does:
>        for (each device) {
>          save config registers
>          reset
>        }
>        wait 500 ms
>        for (each device) {
>          restore config registers
>        }
>     Though it needs more memory space to save config registers, the waiting
>     time is always 500ms.
>     https://lkml.org/lkml/2012/10/15/49
>
>     v3:
>     Move alloc_bootmem and free_bootmem to early_reset_pcie_devices so that
>     they are called only once.
>     https://lkml.org/lkml/2012/10/10/57
>
>     v2:
>     Reset devices in setup_arch() because reset need to be done before
>     interrupt remapping is initialized.
>     https://lkml.org/lkml/2012/10/2/54
>
>     v1:
>     Add fixup_final quirk to reset PCIe devices
>     https://lkml.org/lkml/2012/8/3/160
>
>     Takao Indoh (5):
>        x86, pci: add dummy pci device for early stage
>        PCI: Define the maximum number of PCI function
>        Make reset_devices available at early stage
>        x86, pci: Reset PCIe devices at boot time
>        x86, pci: Enable PCI INTx when MSI is disabled
>
>       arch/x86/include/asm/pci-direct.h |    3 +
>       arch/x86/kernel/setup.c           |    3 +
>       arch/x86/pci/common.c             |    4 +-
>       arch/x86/pci/early.c              |  315 +++++++++++++++++++++++++++++++++++++
>       include/linux/pci.h               |    2 +
>       init/main.c                       |    4 +-
>       6 files changed, 328 insertions(+), 3 deletions(-)
>
>
>     --
>     To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>     the body of a message to majordomo@vger.kernel.org <mailto:majordomo@vger.kernel.org>
>     More majordomo info at http://vger.kernel.org/majordomo-info.html
>     Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
> --
> ------------------
> Oliver Yang

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Yinghai Lu]

On Fri, Nov 30, 2012 at 7:49 AM, MUNEDA Takahiro
<muneda.takahiro@jp.fujitsu.com> wrote:
> On Tue, 27 Nov 2012 09:42:20 +0900 (JST),
> Takao Indoh <indou.takao@jp.fujitsu.com> wrote:
>
>> These patches reset PCIe devices at boot time to address DMA problem on
>> kdump with iommu. When "reset_devices" is specified, a hot reset is
>> triggered on each PCIe root port and downstream port to reset its
>> downstream endpoint.

ThomasR, Can you check if this one help your test case about interrupt ?

Yinghai

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Thomas Renninger]

[-- Attachment #1: Type: text/plain, Size: 52833 bytes --]

On Friday, December 21, 2012 08:19:05 AM Yinghai Lu wrote:
> On Fri, Nov 30, 2012 at 7:49 AM, MUNEDA Takahiro
> 
> <muneda.takahiro@jp.fujitsu.com> wrote:
> > On Tue, 27 Nov 2012 09:42:20 +0900 (JST),
> > 
> > Takao Indoh <indou.takao@jp.fujitsu.com> wrote:
> >> These patches reset PCIe devices at boot time to address DMA problem on
> >> kdump with iommu. When "reset_devices" is specified, a hot reset is
> >> triggered on each PCIe root port and downstream port to reset its
> >> downstream endpoint.
> 
> ThomasR, Can you check if this one help your test case about interrupt ?

Sorry for the long delay...

First: I cannot reproduce this myself. I get one error like:
DRHD: handling fault status reg 2
INTR-REMAP: Request device [[01:00.0] fault index 33
INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear
when a dump is written and the dump completes successfully.

The other report with a specific 10G network card is that they seem
to get an irq storm and see about 80 per second of above messages
in the kdump kernel until things are dead.

I tried the provided patches first on 2.6.32, then I verfied with 3.8-rc2
and in both cases the disk is not detected anymore in
reset_devices (kexec'ed/kdump) case (but things work fine without these
patches).

Find the relevant serial output here:
(starting when the sysrq c(rash) got triggered until
the disk is not found anymore.)
lspci -nn attached:

RIP  [<ffffffff813b05b1>] sysrq_handle_crash+0x11/0x20
 RSP <ffff885f64ee1e38>
CR2: 0000000000000000
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.8.0-rc2-default+ (trenn@ett) (gcc version 4.5.1 20101208 [gcc-4_5-branch revision 13
Command line: root=/dev/disk/by-label/ROOT-BE2 resume=/dev/disk/by-id/scsi-36d4ae52076eef40017f5c96K
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000100-0x000000000009bfff] usable
BIOS-e820: [mem 0x0000000000100000-0x00000000bd2effff] usable
BIOS-e820: [mem 0x00000000bd2f0000-0x00000000bd31bfff] reserved
BIOS-e820: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
BIOS-e820: [mem 0x00000000bd35b000-0x00000000bfffffff] reserved
BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
BIOS-e820: [mem 0x00000000fe000000-0x00000000ffffffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x000000603fffffff] usable
debug: ignoring loglevel setting.
e820: last_pfn = 0x6040000 max_arch_pfn = 0x400000000
NX (Execute Disable) protection: active
e820: user-defined physical RAM map:
user: [mem 0x0000000000000000-0x000000000009ffff] usable
user: [mem 0x00000000070a0000-0x000000001effafff] usable
user: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
SMBIOS 2.7 present.
DMI: Dell Inc. PowerEdge R720/0M1GCR, BIOS 0.3.35 12/15/2011
e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
e820: remove [mem 0x000a0000-0x000fffff] usable
No AGP bridge found
e820: last_pfn = 0x1effb max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-BFFFF uncachable
  C0000-CBFFF write-protect
  CC000-D7FFF write-back
  D8000-EBFFF uncachable
  EC000-FFFFF write-protect
MTRR variable ranges enabled:
  0 base 000000000000 mask 3FC000000000 write-back
  1 base 004000000000 mask 3FE000000000 write-back
  2 base 006000000000 mask 3FFFC0000000 write-back
  3 base 0000C0000000 mask 3FFFC0000000 uncachable
  4 disabled
  5 disabled
  6 disabled
  7 disabled
  8 disabled
  9 disabled
x86 PAT enabled: cpu 0, old 0x7010600070106, new 0x7010600070106
e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
found SMP MP-table at [mem 0x000fe710-0x000fe71f] mapped at [ffff8800000fe710]
initial memory mapped: [mem 0x00000000-0x1fffffff]
Base memory trampoline at [ffff880000096000] 96000 size 24576
Using GB pages for direct mapping
init_memory_mapping: [mem 0x00000000-0x1effafff]
 [mem 0x00000000-0x1edfffff] page 2M
 [mem 0x1ee00000-0x1effafff] page 4k
kernel direct mapping tables up to 0x1effafff @ [mem 0x1eff8000-0x1effafff]
log_buf_len: 4194304
early log buf free: 258384(98%)
RAMDISK: [mem 0x1ea3f000-0x1efeefff]
ACPI: RSDP 00000000000f10d0 00024 (v02 DELL  )
ACPI: XSDT 00000000000f11d4 0009C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: FACP 00000000bd34111c 000F4 (v03 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: DSDT 00000000bd31c000 05FCD (v01 DELL   PE_SC3   00000001 INTL 20110211)
ACPI: FACS 00000000bd343000 00040
ACPI: APIC 00000000bd340478 0016A (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SPCR 00000000bd3405e4 00050 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: HPET 00000000bd340638 00038 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: DMAR 00000000bd340674 00158 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: MCFG 00000000bd340950 0003C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: WD__ 00000000bd340990 00134 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SLIC 00000000bd340ac8 00176 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: ERST 00000000bd322170 00270 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: HEST 00000000bd3223e0 0055C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: BERT 00000000bd321fd0 00030 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: EINJ 00000000bd322000 00170 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SRAT 00000000bd340cf0 003C0 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: TCPA 00000000bd3410b4 00064 (v02 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SSDT 00000000bd344000 0AA14 (v01 INTEL  PPM RCM  80000001 INTL 20061109)
ACPI: Local APIC address 0xfee00000
SRAT: PXM 1 -> APIC 0x00 -> Node 0
SRAT: PXM 2 -> APIC 0x20 -> Node 1
SRAT: PXM 1 -> APIC 0x02 -> Node 0
SRAT: PXM 2 -> APIC 0x22 -> Node 1
SRAT: PXM 1 -> APIC 0x04 -> Node 0
SRAT: PXM 2 -> APIC 0x24 -> Node 1
SRAT: PXM 1 -> APIC 0x06 -> Node 0
SRAT: PXM 2 -> APIC 0x26 -> Node 1
SRAT: PXM 1 -> APIC 0x08 -> Node 0
SRAT: PXM 2 -> APIC 0x28 -> Node 1
SRAT: PXM 1 -> APIC 0x0a -> Node 0
SRAT: PXM 2 -> APIC 0x2a -> Node 1
SRAT: PXM 1 -> APIC 0x0c -> Node 0
SRAT: PXM 2 -> APIC 0x2c -> Node 1
SRAT: PXM 1 -> APIC 0x0e -> Node 0
SRAT: PXM 2 -> APIC 0x2e -> Node 1
SRAT: PXM 1 -> APIC 0x01 -> Node 0
SRAT: PXM 2 -> APIC 0x21 -> Node 1
SRAT: PXM 1 -> APIC 0x03 -> Node 0
SRAT: PXM 2 -> APIC 0x23 -> Node 1
SRAT: PXM 1 -> APIC 0x05 -> Node 0
SRAT: PXM 2 -> APIC 0x25 -> Node 1
SRAT: PXM 1 -> APIC 0x07 -> Node 0
SRAT: PXM 2 -> APIC 0x27 -> Node 1
SRAT: PXM 1 -> APIC 0x09 -> Node 0
SRAT: PXM 2 -> APIC 0x29 -> Node 1
SRAT: PXM 1 -> APIC 0x0b -> Node 0
SRAT: PXM 2 -> APIC 0x2b -> Node 1
SRAT: PXM 1 -> APIC 0x0d -> Node 0
SRAT: PXM 2 -> APIC 0x2d -> Node 1
SRAT: PXM 1 -> APIC 0x0f -> Node 0
SRAT: PXM 2 -> APIC 0x2f -> Node 1
SRAT: Node 0 PXM 1 [mem 0x00000000-0x303fffffff]
SRAT: Node 1 PXM 2 [mem 0x3040000000-0x603fffffff]
Initmem setup node 0 [mem 0x00000000-0x1effafff]
  NODE_DATA [mem 0x1e62b000-0x1e63efff]
 [ffffea0000000000-ffffea00007fffff] PMD -> [ffff88001d600000-ffff88001ddfffff] on node 0
Zone ranges:
  DMA      [mem 0x00010000-0x00ffffff]
  DMA32    [mem 0x01000000-0xffffffff]
  Normal   empty
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x00010000-0x0009ffff]
  node   0: [mem 0x070a0000-0x1effafff]
On node 0 totalpages: 98283
  DMA zone: 3 pages used for memmap
  DMA zone: 10 pages reserved
  DMA zone: 131 pages, LIFO batch:0
  DMA32 zone: 1534 pages used for memmap
  DMA32 zone: 96605 pages, LIFO batch:31
pci 0000:01:00.0 save state
pci 0000:01:00.1 save state
pci 0000:01:00.2 save state
pci 0000:01:00.3 save state
pci 0000:02:00.0 save state
pci 0000:05:00.0 save state
pci 0000:48:00.0 save state
pci 0000:48:00.1 save state
pci 0000:44:00.0 save state
pci 0000:45:00.0 save state
pci 0000:46:00.0 save state
pci 0000:47:00.0 save state
pci 0000:00:01.0 reset
pci 0000:00:02.2 reset
pci 0000:00:03.2 reset
pci 0000:40:02.0 reset
pci 0000:42:05.0 reset
pci 0000:42:06.0 reset
pci 0000:42:08.0 reset
pci 0000:42:09.0 reset
pci 0000:01:00.0 restore state
pci 0000:01:00.1 restore state
pci 0000:01:00.2 restore state
pci 0000:01:00.3 restore state
pci 0000:02:00.0 restore state
pci 0000:05:00.0 restore state
pci 0000:48:00.0 restore state
pci 0000:48:00.1 restore state
pci 0000:44:00.0 restore state
pci 0000:45:00.0 restore state
pci 0000:46:00.0 restore state
pci 0000:47:00.0 restore state
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x20] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x22] enabled)
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x24] enabled)
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x08] lapic_id[0x26] enabled)
ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] enabled)
ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x28] enabled)
ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] enabled)
ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2a] enabled)
ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] enabled)
ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2c] enabled)
ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] enabled)
ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2e] enabled)
ACPI: LAPIC (acpi_id[0x11] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x12] lapic_id[0x21] enabled)
ACPI: LAPIC (acpi_id[0x13] lapic_id[0x03] enabled)
ACPI: LAPIC (acpi_id[0x14] lapic_id[0x23] enabled)
ACPI: LAPIC (acpi_id[0x15] lapic_id[0x05] enabled)
ACPI: LAPIC (acpi_id[0x16] lapic_id[0x25] enabled)
ACPI: LAPIC (acpi_id[0x17] lapic_id[0x07] enabled)
ACPI: LAPIC (acpi_id[0x18] lapic_id[0x27] enabled)
ACPI: LAPIC (acpi_id[0x19] lapic_id[0x09] enabled)
ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x29] enabled)
ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x0b] enabled)
ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x2b] enabled)
ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x0d] enabled)
ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x2d] enabled)
ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x0f] enabled)
ACPI: LAPIC (acpi_id[0x20] lapic_id[0x2f] enabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x01] address[0xfec3f000] gsi_base[32])
IOAPIC[1]: apic_id 1, version 32, address 0xfec3f000, GSI 32-55
ACPI: IOAPIC (id[0x02] address[0xfec7f000] gsi_base[64])
IOAPIC[2]: apic_id 2, version 32, address 0xfec7f000, GSI 64-87
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a701 base: 0xfed00000
smpboot: Allowing 32 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 104
PM: Registered nosave memory: 00000000000a0000 - 00000000070a0000
e820: [mem 0x1effb000-0xbd31bfff] available for PCI devices
Booting paravirtualized kernel on bare hardware
setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:32 nr_node_ids:2
PERCPU: Embedded 27 pages/cpu @ffff88001e000000 s81728 r8192 d20672 u131072
pcpu-alloc: s81728 r8192 d20672 u131072 alloc=1*2097152
pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
pcpu-alloc: [0] 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 96736
Policy zone: DMA32
Kernel command line: root=/dev/disk/by-label/ROOT-BE2 resume=/dev/disk/by-id/scsi-36d4ae52076eef400K
Disabling memory control group subsystem
Misrouted IRQ fixup and polling support enabled
This may significantly impact system performance
PID hash table entries: 2048 (order: 2, 16384 bytes)
__ex_table already sorted, skipping sort
xsave: enabled xstate_bv 0x7, cntxt size 0x340
Checking aperture...
No AGP bridge found
Memory: 357688k/507884k available (5832k kernel code, 114752k absent, 35444k reserved, 5095k data, )
Hierarchical RCU implementation.
        RCU dyntick-idle grace-period acceleration is enabled.
        RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=32.
NR_IRQS:33024 nr_irqs:2024 16
Extended CMOS year: 2000
Spurious LAPIC timer interrupt on cpu 0
do_IRQ: 0.47 No irq handler for vector (irq -1)
Console: colour VGA+ 80x25
console [tty0] enabled
console [ttyS0] enabled
Enabling automatic NUMA balancing. Configure with numa_balancing= or sysctl
hpet clockevent registered
tsc: Fast TSC calibration using PIT
tsc: Detected 2699.982 MHz processor
Calibrating delay loop (skipped), value calculated using timer frequency.. 5399.96 BogoMIPS (lpj=10)
pid_max: default: 32768 minimum: 301
Security Framework initialized
AppArmor: AppArmor initialized
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 256
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
Initializing cgroup subsys blkio
Initializing cgroup subsys perf_event
Initializing cgroup subsys hugetlb
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 20 MCE banks
CPU0: Thermal LVT vector (0xfa) already installed
process: using mwait in idle threads
Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0
Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32
tlb_flushall_shift: 5
ACPI: Core revision 20121018
dmar: Host address width 46
dmar: DRHD base: 0x000000d0d00000 flags: 0x0
dmar: IOMMU 0: reg_base_addr d0d00000 ver 1:0 cap d2078c106f0462 ecap f020fe
dmar: DRHD base: 0x000000dc900000 flags: 0x1
dmar: IOMMU 1: reg_base_addr dc900000 ver 1:0 cap d2078c106f0462 ecap f020fe
dmar: RMRR base: 0x000000bf458000 end: 0x000000bf46ffff
dmar: RMRR base: 0x000000bf450000 end: 0x000000bf450fff
dmar: RMRR base: 0x000000bf452000 end: 0x000000bf452fff
dmar: ATSR flags: 0x0
IOAPIC id 2 under DRHD base  0xd0d00000 IOMMU 0
IOAPIC id 0 under DRHD base  0xdc900000 IOMMU 1
IOAPIC id 1 under DRHD base  0xdc900000 IOMMU 1
HPET id 0 under DRHD base 0xdc900000
------------[ cut here ]------------
WARNING: at drivers/iommu/intel_irq_remapping.c:542 intel_enable_irq_remapping+0x7d/0x26f()
Hardware name: PowerEdge R720
Your BIOS is broken and requested that x2apic be disabled
This will leave your machine vulnerable to irq-injection attacks
Use 'intremap=no_x2apic_optout' to override BIOS request
Modules linked in:
Pid: 1, comm: swapper/0 Not tainted 3.8.0-rc2-default+ #4
Call Trace:
 [<ffffffff81047e2a>] warn_slowpath_common+0x7a/0xb0
 [<ffffffff81047f01>] warn_slowpath_fmt+0x41/0x50
 [<ffffffff81afe7ac>] intel_enable_irq_remapping+0x7d/0x26f
 [<ffffffff81afeaf0>] irq_remapping_enable+0x20/0x22
 [<ffffffff81acf048>] enable_IR+0x5d/0x65
 [<ffffffff81acf334>] enable_IR_x2apic+0x95/0x247
 [<ffffffff81026099>] ? cpumask_next+0x19/0x20
 [<ffffffff8159b9b8>] ? set_cpu_sibling_map+0x405/0x422
 [<ffffffff81026831>] ? apic_write+0x11/0x20
 [<ffffffff81ad1e83>] default_setup_apic_routing+0x15/0x6e
 [<ffffffff81accf43>] native_smp_prepare_cpus+0x137/0x234
 [<ffffffff81ac1c8e>] kernel_init_freeable+0xa2/0x1e1
 [<ffffffff815928b0>] ? rest_init+0x80/0x80
 [<ffffffff815928b9>] kernel_init+0x9/0xf0
 [<ffffffff815ae5bc>] ret_from_fork+0x7c/0xb0
 [<ffffffff815928b0>] ? rest_init+0x80/0x80
---[ end trace 5046c9e3737e7b93 ]---
Enabled IRQ remapping in xapic mode
x2apic not enabled, IRQ remapping is in xapic mode
Switched APIC routing to physical flat.
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
smpboot: CPU0: Genuine Intel(R) CPU  @ 2.70GHz (fam: 06, model: 2d, stepping: 05)
TSC deadline timer enabled
Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, Intel PMU driver.
perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode
... version:                3
... bit width:              48
... generic registers:      4
... value mask:             0000ffffffffffff
... max period:             000000007fffffff
... fixed-purpose events:   3
... event mask:             000000070000000f
Brought up 1 CPUs
smpboot: Total of 1 processors activated (5399.96 BogoMIPS)
devtmpfs: initialized
RTC time: 17:51:12, date: 01/07/13
NET: Registered protocol family 16
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: not using MMCONFIG
PCI: Using configuration type 1 for base access
PCI: Dell System detected, enabling pci=bfsort.
bio: create slab <bio-0> at 0
ACPI: Added _OSI(Module Device)
ACPI: Added _OSI(Processor Device)
ACPI: Added _OSI(3.0 _SCP Extensions)
ACPI: Added _OSI(Processor Aggregator Device)
ACPI: EC: Look up EC in DSDT
[Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
ACPI: Interpreter enabled
ACPI: (supports S0 S4 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
PCI: MMCONFIG for 0000 [bus00-1f] at [mem 0xe0000000-0xe1ffffff] (base 0xe0000000) (size reduced!)
ACPI: No dock devices found.
HEST: Table parsing has been initialized.
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3d])
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
pci_root PNP0A08:00: Requesting ACPI _OSC control (0x15)
pci_root PNP0A08:00: ACPI _OSC control (0x15) granted
pci_root PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-1f] only partially covers the
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [bus 00-3d]
pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
pci_bus 0000:00: root bus resource [io  0x0d00-0x1fff]
pci_bus 0000:00: root bus resource [io  0x8000-0x9fff]
pci_bus 0000:00: root bus resource [io  0xa000-0xbfff]
pci_bus 0000:00: root bus resource [io  0xc000-0xdfff]
pci_bus 0000:00: root bus resource [io  0xe000-0xffff]
pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: root bus resource [mem 0xd4000000-0xdfffffff]
pci_bus 0000:00: root bus resource [mem 0xfed10000-0xfed103ff]
pci_bus 0000:00: root bus resource [mem 0xfed11000-0xfed113ff]
pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff]
pci 0000:00:00.0: [8086:3c00] type 00 class 0x060000
pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: [8086:3c02] type 01 class 0x060400
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:02.0: [8086:3c04] type 01 class 0x060400
pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
pci 0000:00:02.2: [8086:3c06] type 01 class 0x060400
pci 0000:00:02.2: PME# supported from D0 D3hot D3cold
pci 0000:00:03.0: [8086:3c08] type 01 class 0x060400
pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
pci 0000:00:03.2: [8086:3c0a] type 01 class 0x060400
pci 0000:00:03.2: PME# supported from D0 D3hot D3cold
pci 0000:00:05.0: [8086:3c28] type 00 class 0x088000
pci 0000:00:05.2: [8086:3c2a] type 00 class 0x088000
pci 0000:00:11.0: [8086:1d3e] type 01 class 0x060400
pci 0000:00:11.0: PME# supported from D0 D3hot D3cold
pci 0000:00:16.0: [8086:1d3a] type 00 class 0x078000
pci 0000:00:16.0: reg 10: [mem 0xfed10000-0xfed1000f 64bit]
pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
pci 0000:00:16.1: [8086:1d3b] type 00 class 0x078000
pci 0000:00:16.1: reg 10: [mem 0xfed11000-0xfed1100f 64bit]
pci 0000:00:16.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.0: [8086:1d2d] type 00 class 0x0c0320
pci 0000:00:1a.0: reg 10: [mem 0xdc8fd000-0xdc8fd3ff]
pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: [8086:1d10] type 01 class 0x060400
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.7: [8086:1d1e] type 01 class 0x060400
pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.0: [8086:1d26] type 00 class 0x0c0320
pci 0000:00:1d.0: reg 10: [mem 0xdc8fe000-0xdc8fe3ff]
pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
pci 0000:00:1f.0: [8086:1d41] type 00 class 0x060100
pci 0000:00:1f.2: [8086:1d02] type 00 class 0x010601
pci 0000:00:1f.2: reg 10: [io  0xcce8-0xccef]
pci 0000:00:1f.2: reg 14: [io  0xccf8-0xccfb]
pci 0000:00:1f.2: reg 18: [io  0xccf0-0xccf7]
pci 0000:00:1f.2: reg 1c: [io  0xccfc-0xccff]
pci 0000:00:1f.2: reg 20: [io  0xccc0-0xccdf]
pci 0000:00:1f.2: reg 24: [mem 0xdc8ff000-0xdc8ff7ff]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:01:00.0: [8086:1521] type 00 class 0x020000
pci 0000:01:00.0: reg 10: [mem 0xd8b00000-0xd8bfffff]
pci 0000:01:00.0: reg 18: [io  0xfc80-0xfc9f]
pci 0000:01:00.0: reg 1c: [mem 0xd8ff0000-0xd8ff3fff]
pci 0000:01:00.0: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
pci 0000:01:00.1: [8086:1521] type 00 class 0x020000
pci 0000:01:00.1: reg 10: [mem 0xd8c00000-0xd8cfffff]
pci 0000:01:00.1: reg 18: [io  0xfca0-0xfcbf]
pci 0000:01:00.1: reg 1c: [mem 0xd8ff4000-0xd8ff7fff]
pci 0000:01:00.1: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.1: PME# supported from D0 D3hot D3cold
pci 0000:01:00.2: [8086:1521] type 00 class 0x020000
pci 0000:01:00.2: reg 10: [mem 0xd8d00000-0xd8dfffff]
pci 0000:01:00.2: reg 18: [io  0xfcc0-0xfcdf]
pci 0000:01:00.2: reg 1c: [mem 0xd8ff8000-0xd8ffbfff]
pci 0000:01:00.2: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.2: PME# supported from D0 D3hot D3cold
pci 0000:01:00.3: [8086:1521] type 00 class 0x020000
pci 0000:01:00.3: reg 10: [mem 0xd8e00000-0xd8efffff]
pci 0000:01:00.3: reg 18: [io  0xfce0-0xfcff]
pci 0000:01:00.3: reg 1c: [mem 0xd8ffc000-0xd8ffffff]
pci 0000:01:00.3: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.3: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:01.0:   bridge window [io  0xf000-0xffff]
pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xd8ffffff]
pci 0000:00:01.0:   bridge window [mem 0xd5000000-0xd51fffff 64bit pref]
pci 0000:00:02.0: PCI bridge to [bus 03]
pci 0000:00:02.2: PCI bridge to [bus 02]
pci 0000:00:02.2:   bridge window [io  0xe000-0xefff]
pci 0000:00:02.2:   bridge window [mem 0xd9000000-0xd9ffffff]
pci 0000:00:03.0: PCI bridge to [bus 04]
pci 0000:05:00.0: [1000:0064] type 00 class 0x010700
pci 0000:05:00.0: reg 10: [io  0xdc00-0xdcff]
pci 0000:05:00.0: reg 14: [mem 0xdaffc000-0xdaffffff 64bit]
pci 0000:05:00.0: reg 1c: [mem 0xdaf80000-0xdafbffff 64bit]
pci 0000:05:00.0: reg 30: [mem 0xda000000-0xda07ffff pref]
pci 0000:05:00.0: supports D1 D2
pci 0000:00:03.2: PCI bridge to [bus 05]
pci 0000:00:03.2:   bridge window [io  0xd000-0xdfff]
pci 0000:00:03.2:   bridge window [mem 0xda000000-0xdaffffff]
pci 0000:00:11.0: PCI bridge to [bus 06]
pci 0000:00:1c.0: PCI bridge to [bus 07]
pci 0000:08:00.0: [1912:0013] type 01 class 0x060400
pci 0000:08:00.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.7: PCI bridge to [bus 08-0c]
pci 0000:00:1c.7:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:00:1c.7:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:00.0: [1912:0013] type 01 class 0x060400
pci 0000:09:00.0: PME# supported from D0 D3hot D3cold
pci 0000:09:01.0: [1912:0013] type 01 class 0x060400
pci 0000:09:01.0: PME# supported from D0 D3hot D3cold
pci 0000:08:00.0: PCI bridge to [bus 09-0c]
pci 0000:08:00.0:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:08:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:0a:00.0: [1912:0012] type 01 class 0x060400
pci 0000:09:00.0: PCI bridge to [bus 0a-0b]
pci 0000:09:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:09:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:0b:00.0: [102b:0534] type 00 class 0x030000
pci 0000:0b:00.0: reg 10: [mem 0xd4000000-0xd4ffffff pref]
pci 0000:0b:00.0: reg 14: [mem 0xdbffc000-0xdbffffff]
pci 0000:0b:00.0: reg 18: [mem 0xdb000000-0xdb7fffff]
pci 0000:0a:00.0: PCI bridge to [bus 0b]
pci 0000:0a:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:0a:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:01.0: PCI bridge to [bus 0c]
pci 0000:09:01.0:   bridge window [mem 0xdc700000-0xdc7fffff]
pci 0000:00:1e.0: PCI bridge to [bus 0d] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0000-0x03af] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x03e0-0x0cf7] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x03b0-0x03df] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0d00-0x1fff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x8000-0x9fff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0xa000-0xbfff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0xc000-0xdfff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0xe000-0xffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xd4000000-0xdfffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xfed10000-0xfed103ff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xfed11000-0xfed113ff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xfed40000-0xfed44fff] (subtractive decode)
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX5._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6._PRT]
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 40-7e])
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1._PRT]
pci_root PNP0A08:01: Requesting ACPI _OSC control (0x15)
pci_root PNP0A08:01: ACPI _OSC control (0x15) granted
pci_root PNP0A08:01: fail to add MMCONFIG information, can't access extended PCI configuration spac.
PCI host bridge to bus 0000:40
pci_bus 0000:40: root bus resource [bus 40-7e]
pci_bus 0000:40: root bus resource [io  0x2000-0x3fff]
pci_bus 0000:40: root bus resource [io  0x4000-0x5fff]
pci_bus 0000:40: root bus resource [io  0x6000-0x7fff]
pci_bus 0000:40: root bus resource [mem 0xcc000000-0xd3ffffff]
pci 0000:40:01.0: [8086:3c02] type 01 class 0x060400
pci 0000:40:01.0: PME# supported from D0 D3hot D3cold
pci 0000:40:02.0: [8086:3c04] type 01 class 0x060400
pci 0000:40:02.0: PME# supported from D0 D3hot D3cold
pci 0000:40:03.0: [8086:3c08] type 01 class 0x060400
pci 0000:40:03.0: PME# supported from D0 D3hot D3cold
pci 0000:40:03.2: [8086:3c0a] type 01 class 0x060400
pci 0000:40:03.2: PME# supported from D0 D3hot D3cold
pci 0000:40:05.0: [8086:3c28] type 00 class 0x088000
pci 0000:40:05.2: [8086:3c2a] type 00 class 0x088000
pci 0000:41:00.0: [10b5:8624] type 01 class 0x060400
pci 0000:41:00.0: reg 10: [mem 0xd0ce0000-0xd0cfffff]
pci 0000:41:00.0: PME# supported from D0 D3hot D3cold
pci 0000:40:01.0: PCI bridge to [bus 41-47]
pci 0000:40:01.0:   bridge window [io  0x2000-0x3fff]
pci 0000:40:01.0:   bridge window [mem 0xd0800000-0xd0cfffff]
pci 0000:40:01.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:42:04.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:04.0: PME# supported from D0 D3hot D3cold
pci 0000:42:05.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:05.0: PME# supported from D0 D3hot D3cold
pci 0000:42:06.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:06.0: PME# supported from D0 D3hot D3cold
pci 0000:42:08.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:08.0: PME# supported from D0 D3hot D3cold
pci 0000:42:09.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:09.0: PME# supported from D0 D3hot D3cold
pci 0000:41:00.0: PCI bridge to [bus 42-47]
pci 0000:41:00.0:   bridge window [io  0x2000-0x3fff]
pci 0000:41:00.0:   bridge window [mem 0xd0800000-0xd0bfffff]
pci 0000:41:00.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:42:04.0: PCI bridge to [bus 43]
pci 0000:44:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:44:00.0: reg 10: [mem 0xd08ff000-0xd08fffff 64bit]
pci 0000:44:00.0: supports D1
pci 0000:44:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:05.0: PCI bridge to [bus 44]
pci 0000:42:05.0:   bridge window [io  0x2000-0x2fff]
pci 0000:42:05.0:   bridge window [mem 0xd0800000-0xd08fffff]
pci 0000:42:05.0:   bridge window [mem 0xcc200000-0xcc3fffff 64bit pref]
pci 0000:45:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:45:00.0: reg 10: [mem 0xd09ff000-0xd09fffff 64bit]
pci 0000:45:00.0: supports D1
pci 0000:45:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:06.0: PCI bridge to [bus 45]
pci 0000:42:06.0:   bridge window [mem 0xd0900000-0xd09fffff]
pci 0000:46:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:46:00.0: reg 10: [mem 0xd0aff000-0xd0afffff 64bit]
pci 0000:46:00.0: supports D1
pci 0000:46:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:08.0: PCI bridge to [bus 46]
pci 0000:42:08.0:   bridge window [mem 0xd0a00000-0xd0afffff]
pci 0000:47:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:47:00.0: reg 10: [mem 0xd0bff000-0xd0bfffff 64bit]
pci 0000:47:00.0: supports D1
pci 0000:47:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:09.0: PCI bridge to [bus 47]
pci 0000:42:09.0:   bridge window [io  0x3000-0x3fff]
pci 0000:42:09.0:   bridge window [mem 0xd0b00000-0xd0bfffff]
pci 0000:42:09.0:   bridge window [mem 0xcc400000-0xcc5fffff 64bit pref]
pci 0000:48:00.0: [8086:10fb] type 00 class 0x020000
pci 0000:48:00.0: reg 10: [mem 0xcc080000-0xcc0fffff 64bit pref]
pci 0000:48:00.0: reg 18: [io  0x7cc0-0x7cdf]
pci 0000:48:00.0: reg 20: [mem 0xcc1f8000-0xcc1fbfff 64bit pref]
pci 0000:48:00.0: reg 30: [mem 0xd0000000-0xd007ffff pref]
pci 0000:48:00.0: PME# supported from D0 D3hot
pci 0000:48:00.1: [8086:10fb] type 00 class 0x020000
pci 0000:48:00.1: reg 10: [mem 0xcc100000-0xcc17ffff 64bit pref]
pci 0000:48:00.1: reg 18: [io  0x7ce0-0x7cff]
pci 0000:48:00.1: reg 20: [mem 0xcc1fc000-0xcc1fffff 64bit pref]
pci 0000:48:00.1: reg 30: [mem 0xd0000000-0xd007ffff pref]
pci 0000:48:00.1: PME# supported from D0 D3hot
pci 0000:40:02.0: PCI bridge to [bus 48]
pci 0000:40:02.0:   bridge window [io  0x7000-0x7fff]
pci 0000:40:02.0:   bridge window [mem 0xd0000000-0xd07fffff]
pci 0000:40:02.0:   bridge window [mem 0xcc000000-0xcc1fffff 64bit pref]
pci 0000:40:03.0: PCI bridge to [bus 49]
pci 0000:40:03.2: PCI bridge to [bus 4a]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXB._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXC._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXD._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXE._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Root Bridge [P0B1] (domain 0000 [bus 3f])
pci_root PNP0A08:02: ACPI _OSC support notification failed, disabling PCIe ASPM
pci_root PNP0A08:02: Unable to request _OSC control (_OSC support mask: 0x08)
pci_root PNP0A08:02: fail to add MMCONFIG information, can't access extended PCI configuration spac.
PCI host bridge to bus 0000:3f
pci_bus 0000:3f: root bus resource [bus 3f]
pci 0000:3f:08.0: [8086:3c80] type 00 class 0x088000
pci 0000:3f:09.0: [8086:3c90] type 00 class 0x088000
pci 0000:3f:0a.0: [8086:3cc0] type 00 class 0x088000
pci 0000:3f:0a.1: [8086:3cc1] type 00 class 0x088000
pci 0000:3f:0a.2: [8086:3cc2] type 00 class 0x088000
pci 0000:3f:0a.3: [8086:3cd0] type 00 class 0x088000
pci 0000:3f:0b.0: [8086:3ce0] type 00 class 0x088000
pci 0000:3f:0b.3: [8086:3ce3] type 00 class 0x088000
pci 0000:3f:0c.0: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.1: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.2: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.3: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.6: [8086:3cf4] type 00 class 0x088000
pci 0000:3f:0c.7: [8086:3cf6] type 00 class 0x088000
pci 0000:3f:0d.0: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.1: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.2: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.3: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.6: [8086:3cf5] type 00 class 0x088000
pci 0000:3f:0e.0: [8086:3ca0] type 00 class 0x088000
pci 0000:3f:0e.1: [8086:3c46] type 00 class 0x110100
pci 0000:3f:0f.0: [8086:3ca8] type 00 class 0x088000
pci 0000:3f:0f.1: [8086:3c71] type 00 class 0x088000
pci 0000:3f:0f.2: [8086:3caa] type 00 class 0x088000
pci 0000:3f:0f.3: [8086:3cab] type 00 class 0x088000
pci 0000:3f:0f.4: [8086:3cac] type 00 class 0x088000
pci 0000:3f:0f.5: [8086:3cad] type 00 class 0x088000
pci 0000:3f:0f.6: [8086:3cae] type 00 class 0x088000
pci 0000:3f:10.0: [8086:3cb0] type 00 class 0x088000
pci 0000:3f:10.1: [8086:3cb1] type 00 class 0x088000
pci 0000:3f:10.2: [8086:3cb2] type 00 class 0x088000
pci 0000:3f:10.3: [8086:3cb3] type 00 class 0x088000
pci 0000:3f:10.4: [8086:3cb4] type 00 class 0x088000
pci 0000:3f:10.5: [8086:3cb5] type 00 class 0x088000
pci 0000:3f:10.6: [8086:3cb6] type 00 class 0x088000
pci 0000:3f:10.7: [8086:3cb7] type 00 class 0x088000
pci 0000:3f:11.0: [8086:3cb8] type 00 class 0x088000
pci 0000:3f:13.0: [8086:3ce4] type 00 class 0x088000
pci 0000:3f:13.1: [8086:3c43] type 00 class 0x110100
pci 0000:3f:13.4: [8086:3ce6] type 00 class 0x110100
pci 0000:3f:13.5: [8086:3c44] type 00 class 0x110100
pci 0000:3f:13.6: [8086:3c45] type 00 class 0x088000
ACPI: Invalid Power Resource to register!
ACPI _OSC control for PCIe not granted, disabling ASPM
ACPI: PCI Interrupt Link [LK00] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK01] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK02] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK03] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK04] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK05] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK06] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK07] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
vgaarb: device added: PCI:0000:0b:00.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
vgaarb: bridge control possible 0000:0b:00.0
SCSI subsystem initialized
ACPI: bus type scsi registered
libata version 3.00 loaded.
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
e820: reserve RAM buffer [mem 0x1effb000-0x1fffffff]
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Switching to clocksource hpet
AppArmor: AppArmor Filesystem Enabled
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:00: [dma 4]
pnp 00:00: Plug and Play ACPI device, IDs PNP0200 (active)
pnp 00:01: Plug and Play ACPI device, IDs PNP0c04 (active)
system 00:02: Plug and Play ACPI device, IDs PNP0c01 (active)
pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)
pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active)
system 00:06: [io  0x0800-0x087f] has been reserved
system 00:06: [io  0x0880-0x08ff] has been reserved
system 00:06: [io  0x0900-0x091f] has been reserved
system 00:06: [io  0x0920-0x0923] has been reserved
system 00:06: [io  0x0924] has been reserved
system 00:06: [io  0x0370-0x0377] has been reserved
system 00:06: [io  0x0ca0-0x0ca7] has been reserved
system 00:06: [io  0x0ca9-0x0cab] has been reserved
system 00:06: [io  0x0cad-0x0caf] has been reserved
system 00:06: [io  0x0cb0-0x0cbf] has been reserved
system 00:06: Plug and Play ACPI device, IDs PNP0c01 (active)
system 00:07: [io  0x0ca8] has been reserved
system 00:07: [io  0x0cac] has been reserved
system 00:07: Plug and Play ACPI device, IDs IPI0001 PNP0c01 (active)
system 00:08: [mem 0xe0000000-0xe3efffff] has been reserved
system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:09: [mem 0xe4000000-0xe7ffffff] has been reserved
system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:0a: [mem 0xe3f00000-0xe3ffffff] has been reserved
system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:0b: [mem 0xdc900000-0xdc901fff] could not be reserved
system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:0c: [mem 0xd0d00000-0xd0d01fff] could not be reserved
system 00:0c: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
pci 0000:01:00.1: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:]
pci 0000:01:00.2: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:]
pci 0000:01:00.3: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:]
pci 0000:48:00.1: address space collision: [mem 0xd0000000-0xd007ffff pref] conflicts with 0000:48:]
pci 0000:01:00.1: BAR 6: assigned [mem 0xd5000000-0xd507ffff pref]
pci 0000:01:00.2: BAR 6: assigned [mem 0xd5080000-0xd50fffff pref]
pci 0000:01:00.3: BAR 6: assigned [mem 0xd5100000-0xd517ffff pref]
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:01.0:   bridge window [io  0xf000-0xffff]
pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xd8ffffff]
pci 0000:00:01.0:   bridge window [mem 0xd5000000-0xd51fffff 64bit pref]
pci 0000:00:02.0: PCI bridge to [bus 03]
pci 0000:00:02.2: PCI bridge to [bus 02]
pci 0000:00:02.2:   bridge window [io  0xe000-0xefff]
pci 0000:00:02.2:   bridge window [mem 0xd9000000-0xd9ffffff]
pci 0000:00:03.0: PCI bridge to [bus 04]
pci 0000:00:03.2: PCI bridge to [bus 05]
pci 0000:00:03.2:   bridge window [io  0xd000-0xdfff]
pci 0000:00:03.2:   bridge window [mem 0xda000000-0xdaffffff]
pci 0000:00:11.0: PCI bridge to [bus 06]
pci 0000:00:1c.0: PCI bridge to [bus 07]
pci 0000:0a:00.0: PCI bridge to [bus 0b]
pci 0000:0a:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:0a:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:00.0: PCI bridge to [bus 0a-0b]
pci 0000:09:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:09:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:01.0: PCI bridge to [bus 0c]
pci 0000:09:01.0:   bridge window [mem 0xdc700000-0xdc7fffff]
pci 0000:08:00.0: PCI bridge to [bus 09-0c]
pci 0000:08:00.0:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:08:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:00:1c.7: PCI bridge to [bus 08-0c]
pci 0000:00:1c.7:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:00:1c.7:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 0d]
pci 0000:42:04.0: PCI bridge to [bus 43]
pci 0000:42:05.0: PCI bridge to [bus 44]
pci 0000:42:05.0:   bridge window [io  0x2000-0x2fff]
pci 0000:42:05.0:   bridge window [mem 0xd0800000-0xd08fffff]
pci 0000:42:05.0:   bridge window [mem 0xcc200000-0xcc3fffff 64bit pref]
pci 0000:42:06.0: PCI bridge to [bus 45]
pci 0000:42:06.0:   bridge window [mem 0xd0900000-0xd09fffff]
pci 0000:42:08.0: PCI bridge to [bus 46]
pci 0000:42:08.0:   bridge window [mem 0xd0a00000-0xd0afffff]
pci 0000:42:09.0: PCI bridge to [bus 47]
pci 0000:42:09.0:   bridge window [io  0x3000-0x3fff]
pci 0000:42:09.0:   bridge window [mem 0xd0b00000-0xd0bfffff]
pci 0000:42:09.0:   bridge window [mem 0xcc400000-0xcc5fffff 64bit pref]
pci 0000:41:00.0: PCI bridge to [bus 42-47]
pci 0000:41:00.0:   bridge window [io  0x2000-0x3fff]
pci 0000:41:00.0:   bridge window [mem 0xd0800000-0xd0bfffff]
pci 0000:41:00.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:40:01.0: PCI bridge to [bus 41-47]
pci 0000:40:01.0:   bridge window [io  0x2000-0x3fff]
pci 0000:40:01.0:   bridge window [mem 0xd0800000-0xd0cfffff]
pci 0000:40:01.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:48:00.1: BAR 6: assigned [mem 0xcc000000-0xcc07ffff pref]
pci 0000:40:02.0: PCI bridge to [bus 48]
pci 0000:40:02.0:   bridge window [io  0x7000-0x7fff]
pci 0000:40:02.0:   bridge window [mem 0xd0000000-0xd07fffff]
pci 0000:40:02.0:   bridge window [mem 0xcc000000-0xcc1fffff 64bit pref]
pci 0000:40:03.0: PCI bridge to [bus 49]
pci 0000:40:03.2: PCI bridge to [bus 4a]
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
pci_bus 0000:00: resource 7 [io  0x0d00-0x1fff]
pci_bus 0000:00: resource 8 [io  0x8000-0x9fff]
pci_bus 0000:00: resource 9 [io  0xa000-0xbfff]
pci_bus 0000:00: resource 10 [io  0xc000-0xdfff]
pci_bus 0000:00: resource 11 [io  0xe000-0xffff]
pci_bus 0000:00: resource 12 [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: resource 13 [mem 0xd4000000-0xdfffffff]
pci_bus 0000:00: resource 14 [mem 0xfed10000-0xfed103ff]
pci_bus 0000:00: resource 15 [mem 0xfed11000-0xfed113ff]
pci_bus 0000:00: resource 16 [mem 0xfed40000-0xfed44fff]
pci_bus 0000:01: resource 0 [io  0xf000-0xffff]
pci_bus 0000:01: resource 1 [mem 0xd8000000-0xd8ffffff]
pci_bus 0000:01: resource 2 [mem 0xd5000000-0xd51fffff 64bit pref]
pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
pci_bus 0000:02: resource 1 [mem 0xd9000000-0xd9ffffff]
pci_bus 0000:05: resource 0 [io  0xd000-0xdfff]
pci_bus 0000:05: resource 1 [mem 0xda000000-0xdaffffff]
pci_bus 0000:08: resource 1 [mem 0xdb000000-0xdc7fffff]
pci_bus 0000:08: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:09: resource 1 [mem 0xdb000000-0xdc7fffff]
pci_bus 0000:09: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:0a: resource 1 [mem 0xdb000000-0xdbffffff]
pci_bus 0000:0a: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:0b: resource 1 [mem 0xdb000000-0xdbffffff]
pci_bus 0000:0b: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:0c: resource 1 [mem 0xdc700000-0xdc7fffff]
pci_bus 0000:0d: resource 4 [io  0x0000-0x03af]
pci_bus 0000:0d: resource 5 [io  0x03e0-0x0cf7]
pci_bus 0000:0d: resource 6 [io  0x03b0-0x03df]
pci_bus 0000:0d: resource 7 [io  0x0d00-0x1fff]
pci_bus 0000:0d: resource 8 [io  0x8000-0x9fff]
pci_bus 0000:0d: resource 9 [io  0xa000-0xbfff]
pci_bus 0000:0d: resource 10 [io  0xc000-0xdfff]
pci_bus 0000:0d: resource 11 [io  0xe000-0xffff]
pci_bus 0000:0d: resource 12 [mem 0x000a0000-0x000bffff]
pci_bus 0000:0d: resource 13 [mem 0xd4000000-0xdfffffff]
pci_bus 0000:0d: resource 14 [mem 0xfed10000-0xfed103ff]
pci_bus 0000:0d: resource 15 [mem 0xfed11000-0xfed113ff]
pci_bus 0000:0d: resource 16 [mem 0xfed40000-0xfed44fff]
pci_bus 0000:40: resource 4 [io  0x2000-0x3fff]
pci_bus 0000:40: resource 5 [io  0x4000-0x5fff]
pci_bus 0000:40: resource 6 [io  0x6000-0x7fff]
pci_bus 0000:40: resource 7 [mem 0xcc000000-0xd3ffffff]
pci_bus 0000:41: resource 0 [io  0x2000-0x3fff]
pci_bus 0000:41: resource 1 [mem 0xd0800000-0xd0cfffff]
pci_bus 0000:41: resource 2 [mem 0xcc200000-0xcc5fffff 64bit pref]
pci_bus 0000:42: resource 0 [io  0x2000-0x3fff]
pci_bus 0000:42: resource 1 [mem 0xd0800000-0xd0bfffff]
pci_bus 0000:42: resource 2 [mem 0xcc200000-0xcc5fffff 64bit pref]
pci_bus 0000:44: resource 0 [io  0x2000-0x2fff]
pci_bus 0000:44: resource 1 [mem 0xd0800000-0xd08fffff]
pci_bus 0000:44: resource 2 [mem 0xcc200000-0xcc3fffff 64bit pref]
pci_bus 0000:45: resource 1 [mem 0xd0900000-0xd09fffff]
pci_bus 0000:46: resource 1 [mem 0xd0a00000-0xd0afffff]
pci_bus 0000:47: resource 0 [io  0x3000-0x3fff]
pci_bus 0000:47: resource 1 [mem 0xd0b00000-0xd0bfffff]
pci_bus 0000:47: resource 2 [mem 0xcc400000-0xcc5fffff 64bit pref]
pci_bus 0000:48: resource 0 [io  0x7000-0x7fff]
pci_bus 0000:48: resource 1 [mem 0xd0000000-0xd07fffff]
pci_bus 0000:48: resource 2 [mem 0xcc000000-0xcc1fffff 64bit pref]
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 4, 65536 bytes)
TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
pci 0000:0b:00.0: Boot video device
PCI: CLS 64 bytes, default 64
Unpacking initramfs...
Freeing initrd memory: 5824k freed
audit: initializing netlink socket (disabled)
type=2000 audit(1357581073.824:1): initialized
HugeTLB registered 2 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 709
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler deadline registered (default)
io scheduler cfq registered
pcieport 0000:00:01.0: irq 106 for MSI/MSI-X
pcieport 0000:00:02.0: irq 107 for MSI/MSI-X
pcieport 0000:00:02.2: irq 108 for MSI/MSI-X
pcieport 0000:00:03.0: irq 109 for MSI/MSI-X
pcieport 0000:00:03.2: irq 110 for MSI/MSI-X
pcieport 0000:00:11.0: irq 111 for MSI/MSI-X
pcieport 0000:00:1c.0: irq 112 for MSI/MSI-X
pcieport 0000:00:1c.7: irq 113 for MSI/MSI-X
pcieport 0000:40:01.0: irq 114 for MSI/MSI-X
pcieport 0000:40:02.0: irq 115 for MSI/MSI-X
pcieport 0000:40:03.0: irq 116 for MSI/MSI-X
pcieport 0000:40:03.2: irq 117 for MSI/MSI-X
pcieport 0000:42:05.0: irq 118 for MSI/MSI-X
pcieport 0000:42:09.0: irq 119 for MSI/MSI-X
pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
pci 0000:01:00.2: Signaling PME through PCIe PME interrupt
pci 0000:01:00.3: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:02.2: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:02.2:pcie01: service driver pcie_pme loaded
pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:03.2: Signaling PME through PCIe PME interrupt
pci 0000:05:00.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:03.2:pcie01: service driver pcie_pme loaded
pcieport 0000:00:11.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:11.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
pcieport 0000:08:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:09:00.0: Signaling PME through PCIe PME interrupt
pci 0000:0a:00.0: Signaling PME through PCIe PME interrupt
pci 0000:0b:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:09:01.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
pcieport 0000:40:01.0: Signaling PME through PCIe PME interrupt
pcieport 0000:41:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:04.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:05.0: Signaling PME through PCIe PME interrupt
pci 0000:44:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:06.0: Signaling PME through PCIe PME interrupt
pci 0000:45:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:08.0: Signaling PME through PCIe PME interrupt
pci 0000:46:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:09.0: Signaling PME through PCIe PME interrupt
pci 0000:47:00.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:01.0:pcie01: service driver pcie_pme loaded
pcieport 0000:40:02.0: Signaling PME through PCIe PME interrupt
pci 0000:48:00.0: Signaling PME through PCIe PME interrupt
pci 0000:48:00.1: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:02.0:pcie01: service driver pcie_pme loaded
pcieport 0000:40:03.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:03.0:pcie01: service driver pcie_pme loaded
pcieport 0000:40:03.2: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:03.2:pcie01: service driver pcie_pme loaded
intel_idle: MWAIT substates: 0x21120
intel_idle: v0.4 model 0x2D
intel_idle: lapic_timer_reliable_states 0xffffffff
ERST: Error Record Serialization Table (ERST) support is initialized.
GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
00:04: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Non-volatile memory driver v1.3
Linux agpgart interface v0.103
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: irq 120 for MSI/MSI-X
ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ems apst
ahci 0000:00:1f.2: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff100 irq 120
ata2: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff180 irq 120
ata3: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff200 irq 120
ata4: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff280 irq 120
ata5: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff300 irq 120
ata6: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff380 irq 120
libphy: Fixed MDIO Bus: probed
i8042: PNP: No PS/2 controller found. Probing ports directly.
i8042: No controller found
tsc: Refined TSC clocksource calibration: 2699.999 MHz
Switching to clocksource tsc
mousedev: PS/2 mouse device common for all mice
rtc_cmos 00:03: RTC can wake from S4
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one day, y3k, 242 bytes nvram, hpet irqs
cpuidle: using governor ladder
cpuidle: using governor menu
ledtrig-cpu: registered to indicate activity on CPUs
EFI Variables Facility v0.08 2004-May-17
TCP: cubic registered
NET: Registered protocol family 10
Key type dns_resolver registered
PM: Checking hibernation image partition /dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-par8
ata6: SATA link down (SStatus 0 SControl 300)
ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
ata1: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata5.00: ATAPI: TEAC DVD-ROM DV-28SW, R.2A, max UDMA/100
ata5.00: configured for UDMA/100
scsi 4:0:0:0: CD-ROM            TEAC     DVD-ROM DV-28SW  R.2A PQ: 0 ANSI: 5
PM: Hibernation image not present or could not be loaded.
registered taskstats version 1
  Magic number: 13:635:895
rtc_cmos 00:03: setting system clock to 2013-01-07 17:51:18 UTC (1357581078)
Freeing unused kernel memory: 1000k freed
Write protecting the kernel read-only data: 10240k
Freeing unused kernel memory: 300k freed
Freeing unused kernel memory: 1500k freed
doing fast boot
SysRq : Changing Loglevel
Loglevel set to 7
megasas: 06.504.01.00-rc1 Mon. Oct. 1 17:00:00 PDT 2012
FATAL: Module ahci not found.
teradata-kdump: Skipping mpt2sas
BIOS EDD facility v0.16 2004-Jun-25, 2 devices found
FATAL: Module jbd not found.
FATAL: Module ext3 not found.
Creating device nodes with udev
udevd (180): /proc/180/oom_adj is deprecated, please use /proc/180/oom_score_adj instead.
udevd version 128 started
mount: devpts already mounted or /dev/pts busy
mount: according to mtab, devpts is already mounted on /dev/pts
Boot logging started on /dev/ttyS0(/dev/console) at Mon Jan  7 12:51:19 2013
Waiting for device /dev/disk/by-label/ROOT-BE2 to appear: ...............

....................................................................................................
Want me to fall back to /dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-part3? (Y/n)
Waiting for device /dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-part3 to appear: ........h
$
$

[-- Attachment #2: lspci --]
[-- Type: text/plain, Size: 11172 bytes --]

00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3c00] (rev 05)
00:01.0 PCI bridge [0604]: Intel Corporation Device [8086:3c02] (rev 05)
00:02.0 PCI bridge [0604]: Intel Corporation Device [8086:3c04] (rev 05)
00:02.2 PCI bridge [0604]: Intel Corporation Device [8086:3c06] (rev 05)
00:03.0 PCI bridge [0604]: Intel Corporation Device [8086:3c08] (rev 05)
00:03.2 PCI bridge [0604]: Intel Corporation Device [8086:3c0a] (rev 05)
00:05.0 System peripheral [0880]: Intel Corporation Device [8086:3c28] (rev 05)
00:05.2 System peripheral [0880]: Intel Corporation Device [8086:3c2a] (rev 05)
00:11.0 PCI bridge [0604]: Intel Corporation Device [8086:1d3e] (rev 05)
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:1d3a] (rev 05)
00:16.1 Communication controller [0780]: Intel Corporation Device [8086:1d3b] (rev 05)
00:1a.0 USB Controller [0c03]: Intel Corporation Device [8086:1d2d] (rev 05)
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:1d10] (rev b5)
00:1c.7 PCI bridge [0604]: Intel Corporation Device [8086:1d1e] (rev b5)
00:1d.0 USB Controller [0c03]: Intel Corporation Device [8086:1d26] (rev 05)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a5)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:1d41] (rev 05)
00:1f.2 SATA controller [0106]: Intel Corporation Device [8086:1d02] (rev 05)
01:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
01:00.1 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
01:00.2 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
01:00.3 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
02:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic Device [1000:005b] (rev 01)
05:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] [1000:0064] (rev 02)
08:00.0 PCI bridge [0604]: Renesas Technology Corp. Device [1912:0013]
09:00.0 PCI bridge [0604]: Renesas Technology Corp. Device [1912:0013]
09:01.0 PCI bridge [0604]: Renesas Technology Corp. Device [1912:0013]
0a:00.0 PCI bridge [0604]: Renesas Technology Corp. Device [1912:0012]
0b:00.0 VGA compatible controller [0300]: Matrox Graphics, Inc. Device [102b:0534]
3f:08.0 System peripheral [0880]: Intel Corporation Device [8086:3c80] (rev 05)
3f:09.0 System peripheral [0880]: Intel Corporation Device [8086:3c90] (rev 05)
3f:0a.0 System peripheral [0880]: Intel Corporation Device [8086:3cc0] (rev 05)
3f:0a.1 System peripheral [0880]: Intel Corporation Device [8086:3cc1] (rev 05)
3f:0a.2 System peripheral [0880]: Intel Corporation Device [8086:3cc2] (rev 05)
3f:0a.3 System peripheral [0880]: Intel Corporation Device [8086:3cd0] (rev 05)
3f:0b.0 System peripheral [0880]: Intel Corporation Device [8086:3ce0] (rev 05)
3f:0b.3 System peripheral [0880]: Intel Corporation Device [8086:3ce3] (rev 05)
3f:0c.0 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
3f:0c.1 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
3f:0c.2 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
3f:0c.3 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
3f:0c.6 System peripheral [0880]: Intel Corporation Device [8086:3cf4] (rev 05)
3f:0c.7 System peripheral [0880]: Intel Corporation Device [8086:3cf6] (rev 05)
3f:0d.0 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
3f:0d.1 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
3f:0d.2 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
3f:0d.3 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
3f:0d.6 System peripheral [0880]: Intel Corporation Device [8086:3cf5] (rev 05)
3f:0e.0 System peripheral [0880]: Intel Corporation Device [8086:3ca0] (rev 05)
3f:0e.1 Performance counters [1101]: Intel Corporation Device [8086:3c46] (rev 05)
3f:0f.0 System peripheral [0880]: Intel Corporation Device [8086:3ca8] (rev 05)
3f:0f.1 System peripheral [0880]: Intel Corporation Device [8086:3c71] (rev 05)
3f:0f.2 System peripheral [0880]: Intel Corporation Device [8086:3caa] (rev 05)
3f:0f.3 System peripheral [0880]: Intel Corporation Device [8086:3cab] (rev 05)
3f:0f.4 System peripheral [0880]: Intel Corporation Device [8086:3cac] (rev 05)
3f:0f.5 System peripheral [0880]: Intel Corporation Device [8086:3cad] (rev 05)
3f:0f.6 System peripheral [0880]: Intel Corporation Device [8086:3cae] (rev 05)
3f:10.0 System peripheral [0880]: Intel Corporation Device [8086:3cb0] (rev 05)
3f:10.1 System peripheral [0880]: Intel Corporation Device [8086:3cb1] (rev 05)
3f:10.2 System peripheral [0880]: Intel Corporation Device [8086:3cb2] (rev 05)
3f:10.3 System peripheral [0880]: Intel Corporation Device [8086:3cb3] (rev 05)
3f:10.4 System peripheral [0880]: Intel Corporation Device [8086:3cb4] (rev 05)
3f:10.5 System peripheral [0880]: Intel Corporation Device [8086:3cb5] (rev 05)
3f:10.6 System peripheral [0880]: Intel Corporation Device [8086:3cb6] (rev 05)
3f:10.7 System peripheral [0880]: Intel Corporation Device [8086:3cb7] (rev 05)
3f:11.0 System peripheral [0880]: Intel Corporation Device [8086:3cb8] (rev 05)
3f:13.0 System peripheral [0880]: Intel Corporation Device [8086:3ce4] (rev 05)
3f:13.1 Performance counters [1101]: Intel Corporation Device [8086:3c43] (rev 05)
3f:13.4 Performance counters [1101]: Intel Corporation Device [8086:3ce6] (rev 05)
3f:13.5 Performance counters [1101]: Intel Corporation Device [8086:3c44] (rev 05)
3f:13.6 System peripheral [0880]: Intel Corporation Device [8086:3c45] (rev 05)
40:01.0 PCI bridge [0604]: Intel Corporation Device [8086:3c02] (rev 05)
40:02.0 PCI bridge [0604]: Intel Corporation Device [8086:3c04] (rev 05)
40:03.0 PCI bridge [0604]: Intel Corporation Device [8086:3c08] (rev 05)
40:03.2 PCI bridge [0604]: Intel Corporation Device [8086:3c0a] (rev 05)
40:05.0 System peripheral [0880]: Intel Corporation Device [8086:3c28] (rev 05)
40:05.2 System peripheral [0880]: Intel Corporation Device [8086:3c2a] (rev 05)
41:00.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] [10b5:8624] (rev bb)
42:04.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] [10b5:8624] (rev bb)
42:05.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] [10b5:8624] (rev bb)
42:06.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] [10b5:8624] (rev bb)
42:08.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] [10b5:8624] (rev bb)
42:09.0 PCI bridge [0604]: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] [10b5:8624] (rev bb)
44:00.0 Encryption controller [1080]: Hifn Inc. DS4100 Secure Multi-Gigabit Server Adapter with Compression [13a3:0037]
45:00.0 Encryption controller [1080]: Hifn Inc. DS4100 Secure Multi-Gigabit Server Adapter with Compression [13a3:0037]
46:00.0 Encryption controller [1080]: Hifn Inc. DS4100 Secure Multi-Gigabit Server Adapter with Compression [13a3:0037]
47:00.0 Encryption controller [1080]: Hifn Inc. DS4100 Secure Multi-Gigabit Server Adapter with Compression [13a3:0037]
48:00.0 Ethernet controller [0200]: Intel Corporation 82599EB 10-Gigabit Network Connection [8086:10fb] (rev 01)
48:00.1 Ethernet controller [0200]: Intel Corporation 82599EB 10-Gigabit Network Connection [8086:10fb] (rev 01)
7f:08.0 System peripheral [0880]: Intel Corporation Device [8086:3c80] (rev 05)
7f:09.0 System peripheral [0880]: Intel Corporation Device [8086:3c90] (rev 05)
7f:0a.0 System peripheral [0880]: Intel Corporation Device [8086:3cc0] (rev 05)
7f:0a.1 System peripheral [0880]: Intel Corporation Device [8086:3cc1] (rev 05)
7f:0a.2 System peripheral [0880]: Intel Corporation Device [8086:3cc2] (rev 05)
7f:0a.3 System peripheral [0880]: Intel Corporation Device [8086:3cd0] (rev 05)
7f:0b.0 System peripheral [0880]: Intel Corporation Device [8086:3ce0] (rev 05)
7f:0b.3 System peripheral [0880]: Intel Corporation Device [8086:3ce3] (rev 05)
7f:0c.0 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
7f:0c.1 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
7f:0c.2 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
7f:0c.3 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
7f:0c.6 System peripheral [0880]: Intel Corporation Device [8086:3cf4] (rev 05)
7f:0c.7 System peripheral [0880]: Intel Corporation Device [8086:3cf6] (rev 05)
7f:0d.0 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
7f:0d.1 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
7f:0d.2 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
7f:0d.3 System peripheral [0880]: Intel Corporation Device [8086:3ce8] (rev 05)
7f:0d.6 System peripheral [0880]: Intel Corporation Device [8086:3cf5] (rev 05)
7f:0e.0 System peripheral [0880]: Intel Corporation Device [8086:3ca0] (rev 05)
7f:0e.1 Performance counters [1101]: Intel Corporation Device [8086:3c46] (rev 05)
7f:0f.0 System peripheral [0880]: Intel Corporation Device [8086:3ca8] (rev 05)
7f:0f.1 System peripheral [0880]: Intel Corporation Device [8086:3c71] (rev 05)
7f:0f.2 System peripheral [0880]: Intel Corporation Device [8086:3caa] (rev 05)
7f:0f.3 System peripheral [0880]: Intel Corporation Device [8086:3cab] (rev 05)
7f:0f.4 System peripheral [0880]: Intel Corporation Device [8086:3cac] (rev 05)
7f:0f.5 System peripheral [0880]: Intel Corporation Device [8086:3cad] (rev 05)
7f:0f.6 System peripheral [0880]: Intel Corporation Device [8086:3cae] (rev 05)
7f:10.0 System peripheral [0880]: Intel Corporation Device [8086:3cb0] (rev 05)
7f:10.1 System peripheral [0880]: Intel Corporation Device [8086:3cb1] (rev 05)
7f:10.2 System peripheral [0880]: Intel Corporation Device [8086:3cb2] (rev 05)
7f:10.3 System peripheral [0880]: Intel Corporation Device [8086:3cb3] (rev 05)
7f:10.4 System peripheral [0880]: Intel Corporation Device [8086:3cb4] (rev 05)
7f:10.5 System peripheral [0880]: Intel Corporation Device [8086:3cb5] (rev 05)
7f:10.6 System peripheral [0880]: Intel Corporation Device [8086:3cb6] (rev 05)
7f:10.7 System peripheral [0880]: Intel Corporation Device [8086:3cb7] (rev 05)
7f:11.0 System peripheral [0880]: Intel Corporation Device [8086:3cb8] (rev 05)
7f:13.0 System peripheral [0880]: Intel Corporation Device [8086:3ce4] (rev 05)
7f:13.1 Performance counters [1101]: Intel Corporation Device [8086:3c43] (rev 05)
7f:13.4 Performance counters [1101]: Intel Corporation Device [8086:3ce6] (rev 05)
7f:13.5 Performance counters [1101]: Intel Corporation Device [8086:3c44] (rev 05)
7f:13.6 System peripheral [0880]: Intel Corporation Device [8086:3c45] (rev 05)

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Yinghai Lu]

On Mon, Jan 7, 2013 at 11:09 AM, Thomas Renninger <trenn@suse.de> wrote:
> e820: BIOS-provided physical RAM map:
> BIOS-e820: [mem 0x0000000000000100-0x000000000009bfff] usable
> BIOS-e820: [mem 0x0000000000100000-0x00000000bd2effff] usable
> BIOS-e820: [mem 0x00000000bd2f0000-0x00000000bd31bfff] reserved
> BIOS-e820: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
> BIOS-e820: [mem 0x00000000bd35b000-0x00000000bfffffff] reserved
> BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
> BIOS-e820: [mem 0x00000000fe000000-0x00000000ffffffff] reserved
> BIOS-e820: [mem 0x0000000100000000-0x000000603fffffff] usable
> debug: ignoring loglevel setting.
> e820: last_pfn = 0x6040000 max_arch_pfn = 0x400000000
> NX (Execute Disable) protection: active
> e820: user-defined physical RAM map:
> user: [mem 0x0000000000000000-0x000000000009ffff] usable
> user: [mem 0x00000000070a0000-0x000000001effafff] usable
> user: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data

can you make sure kdump kernel command line take
"memmap=256M$3584M" ?

it will make mmconf working.

> megasas: 06.504.01.00-rc1 Mon. Oct. 1 17:00:00 PDT 2012

also need to append "debug ignore_loglevel" to see why the disks are not
probed.

Thanks

Yinghai

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Thomas Renninger]

On Monday, January 07, 2013 12:16:42 PM Yinghai Lu wrote:
> On Mon, Jan 7, 2013 at 11:09 AM, Thomas Renninger <trenn@suse.de> wrote:
> > e820: BIOS-provided physical RAM map:
> > BIOS-e820: [mem 0x0000000000000100-0x000000000009bfff] usable
> > BIOS-e820: [mem 0x0000000000100000-0x00000000bd2effff] usable
> > BIOS-e820: [mem 0x00000000bd2f0000-0x00000000bd31bfff] reserved
> > BIOS-e820: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
> > BIOS-e820: [mem 0x00000000bd35b000-0x00000000bfffffff] reserved
> > BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
> > BIOS-e820: [mem 0x00000000fe000000-0x00000000ffffffff] reserved
> > BIOS-e820: [mem 0x0000000100000000-0x000000603fffffff] usable
> > debug: ignoring loglevel setting.
> > e820: last_pfn = 0x6040000 max_arch_pfn = 0x400000000
> > NX (Execute Disable) protection: active
> > e820: user-defined physical RAM map:
> > user: [mem 0x0000000000000000-0x000000000009ffff] usable
> > user: [mem 0x00000000070a0000-0x000000001effafff] usable
> > user: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
> 
> can you make sure kdump kernel command line take
> "memmap=256M$3584M" ?
> 
> it will make mmconf working.
Why is this needed?
This area:
BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
already is reserved?

I tried with: memmap=256M$3584M, memmap=256M\$3584M and
\"memmap=256M\$3584M\"
embedded into:
KDUMP_COMMANDLINE_APPEND=""

resulting in following strings  when letting kdump reload the kexec kernel:
memmap=256M3584M, memmap=256M$3584M and "memmap=256M$3584M"
but all three resulted in:
Malformed early option 'memmap'

I also tried to manually:
/sbin/kexec -p /boot/vmlinuz-3.8.0-rc2-default+ --append="... memmap=256M\$3584M"
without success.
Hm, I should have used single quotes, but really annoying is that the line:
Command line:
is cut to 100 bytes in kdump case and I cannot verify what got passed
(cmp with the provided serial output below).

Here is one full command line as generated by the kdump tools:

Loading kdump kernel: /sbin/kexec -p /boot/vmlinuz-3.8.0-rc2-default+ --append="root=/dev/disk/by-label/ROOT-BE2 resume=/dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-part8 nmi_watchdog=0 elevator=noop log_buf_len=4M printk.time=0 udev_timeout=180 cgroup_disable=memory console=tty0 console=ttyS0,115200n elevator=deadline sysrq=yes reset_devices irqpoll maxcpus=1  sysrq=7 debug ignore_loglevel memmap=256M$3584M" --initrd=/boot/initrd-3.8.0-rc2-default+-kdump

> 
> > megasas: 06.504.01.00-rc1 Mon. Oct. 1 17:00:00 PDT 2012
> 
> also need to append "debug ignore_loglevel" to see why the disks are not
> probed.

with additional debug param, but with bad memmap param:
linux-dwlr:~ # SysRq : Trigger a crash
BUG: unable to handle kernel NULL pointer dereference at           (null)
IP: [<ffffffff813b05b1>] sysrq_handle_crash+0x11/0x20
PGD 2f62e6b067 PUD 2f63b3f067 PMD 0
Oops: 0002 [#1] SMP
Modules linked in: nfsv3 nfs_acl nfs fscache lockd sunrpc af_packet igb ipmi_devintf ipmi_si ipmi_ms
CPU 12
Pid: 20173, comm: bash Tainted: G        W    3.8.0-rc2-default+ #4 Dell Inc. PowerEdge R720/0M1GCR
RIP: 0010:[<ffffffff813b05b1>]  [<ffffffff813b05b1>] sysrq_handle_crash+0x11/0x20
RSP: 0018:ffff882f57f09e38  EFLAGS: 00010092
RAX: 000000000000000f RBX: 0000000000000063 RCX: 0000000000001966
RDX: 00000000000039ae RSI: 0000000000000082 RDI: 0000000000000063
RBP: ffff882f57f09e38 R08: 000000000002127c R09: ffff88603fc00000
R10: 00000000000005f2 R11: 00000000000005f1 R12: ffffffff81a57ec0
R13: 0000000000000286 R14: 0000000000000001 R15: 0000000000000000
FS:  00007f5680caa700(0000) GS:ffff882f7fcc0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000002f655e0000 CR4: 00000000000407e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process bash (pid: 20173, threadinfo ffff882f57f08000, task ffff882f61cec400)
Stack:
 ffff882f57f09e78 ffffffff813b0d29 ffff882f65729440 0000000000000002
 ffff882f639223c0 00007f5680b47000 0000000000000002 fffffffffffffffb
 ffff882f57f09e98 ffffffff813b0dcd ffff882f57f09eb8 ffff882f659ce480
Call Trace:
 [<ffffffff813b0d29>] __handle_sysrq+0x129/0x190
 [<ffffffff813b0dcd>] write_sysrq_trigger+0x3d/0x40
 [<ffffffff811d9d46>] proc_reg_write+0x76/0xb0
 [<ffffffff81177496>] vfs_write+0xc6/0x180
 [<ffffffff811777ca>] sys_write+0x5a/0xa0
 [<ffffffff815ae669>] system_call_fastpath+0x16/0x1b
Code: ff e9 78 ff ff ff 45 01 f4 45 39 65 2c 75 cd 4c 89 ef e8 83 f7 ff ff eb c3 90 55 c7 05 f5 f3
RIP  [<ffffffff813b05b1>] sysrq_handle_crash+0x11/0x20
 RSP <ffff882f57f09e38>
CR2: 0000000000000000
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.8.0-rc2-default+ (trenn@ett) (gcc version 4.5.1 20101208 [gcc-4_5-branch revision 13
Command line: root=/dev/disk/by-label/ROOT-BE2 resume=/dev/disk/by-id/scsi-36d4ae52076eef40017f5c96K
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000100-0x000000000009bfff] usable
BIOS-e820: [mem 0x0000000000100000-0x00000000bd2effff] usable
BIOS-e820: [mem 0x00000000bd2f0000-0x00000000bd31bfff] reserved
BIOS-e820: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
BIOS-e820: [mem 0x00000000bd35b000-0x00000000bfffffff] reserved
BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
BIOS-e820: [mem 0x00000000fe000000-0x00000000ffffffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x000000603fffffff] usable
debug: ignoring loglevel setting.
e820: last_pfn = 0x6040000 max_arch_pfn = 0x400000000
NX (Execute Disable) protection: active
e820: user-defined physical RAM map:
user: [mem 0x0000000000000000-0x000000000009ffff] usable
user: [mem 0x00000000070a0000-0x000000001effafff] usable
user: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
SMBIOS 2.7 present.
DMI: Dell Inc. PowerEdge R720/0M1GCR, BIOS 0.3.35 12/15/2011
e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
e820: remove [mem 0x000a0000-0x000fffff] usable
No AGP bridge found
e820: last_pfn = 0x1effb max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-BFFFF uncachable
  C0000-CBFFF write-protect
  CC000-D7FFF write-back
  D8000-EBFFF uncachable
  EC000-FFFFF write-protect
MTRR variable ranges enabled:
  0 base 000000000000 mask 3FC000000000 write-back
  1 base 004000000000 mask 3FE000000000 write-back
  2 base 006000000000 mask 3FFFC0000000 write-back
  3 base 0000C0000000 mask 3FFFC0000000 uncachable
  4 disabled
  5 disabled
  6 disabled
  7 disabled
  8 disabled
  9 disabled
x86 PAT enabled: cpu 0, old 0x7010600070106, new 0x7010600070106
e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
found SMP MP-table at [mem 0x000fe710-0x000fe71f] mapped at [ffff8800000fe710]
initial memory mapped: [mem 0x00000000-0x1fffffff]
Base memory trampoline at [ffff880000096000] 96000 size 24576
Using GB pages for direct mapping
init_memory_mapping: [mem 0x00000000-0x1effafff]
 [mem 0x00000000-0x1edfffff] page 2M
 [mem 0x1ee00000-0x1effafff] page 4k
kernel direct mapping tables up to 0x1effafff @ [mem 0x1eff8000-0x1effafff]
log_buf_len: 4194304
early log buf free: 258360(98%)
RAMDISK: [mem 0x1ea3f000-0x1efeefff]
ACPI: RSDP 00000000000f10d0 00024 (v02 DELL  )
ACPI: XSDT 00000000000f11d4 0009C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: FACP 00000000bd34111c 000F4 (v03 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: DSDT 00000000bd31c000 05FCD (v01 DELL   PE_SC3   00000001 INTL 20110211)
ACPI: FACS 00000000bd343000 00040
ACPI: APIC 00000000bd340478 0016A (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SPCR 00000000bd3405e4 00050 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: HPET 00000000bd340638 00038 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: DMAR 00000000bd340674 00158 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: MCFG 00000000bd340950 0003C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: WD__ 00000000bd340990 00134 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SLIC 00000000bd340ac8 00176 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: ERST 00000000bd322170 00270 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: HEST 00000000bd3223e0 0055C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: BERT 00000000bd321fd0 00030 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: EINJ 00000000bd322000 00170 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SRAT 00000000bd340cf0 003C0 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: TCPA 00000000bd3410b4 00064 (v02 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SSDT 00000000bd344000 0AA14 (v01 INTEL  PPM RCM  80000001 INTL 20061109)
ACPI: Local APIC address 0xfee00000
SRAT: PXM 1 -> APIC 0x00 -> Node 0
SRAT: PXM 2 -> APIC 0x20 -> Node 1
SRAT: PXM 1 -> APIC 0x02 -> Node 0
SRAT: PXM 2 -> APIC 0x22 -> Node 1
SRAT: PXM 1 -> APIC 0x04 -> Node 0
SRAT: PXM 2 -> APIC 0x24 -> Node 1
SRAT: PXM 1 -> APIC 0x06 -> Node 0
SRAT: PXM 2 -> APIC 0x26 -> Node 1
SRAT: PXM 1 -> APIC 0x08 -> Node 0
SRAT: PXM 2 -> APIC 0x28 -> Node 1
SRAT: PXM 1 -> APIC 0x0a -> Node 0
SRAT: PXM 2 -> APIC 0x2a -> Node 1
SRAT: PXM 1 -> APIC 0x0c -> Node 0
SRAT: PXM 2 -> APIC 0x2c -> Node 1
SRAT: PXM 1 -> APIC 0x0e -> Node 0
SRAT: PXM 2 -> APIC 0x2e -> Node 1
SRAT: PXM 1 -> APIC 0x01 -> Node 0
SRAT: PXM 2 -> APIC 0x21 -> Node 1
SRAT: PXM 1 -> APIC 0x03 -> Node 0
SRAT: PXM 2 -> APIC 0x23 -> Node 1
SRAT: PXM 1 -> APIC 0x05 -> Node 0
SRAT: PXM 2 -> APIC 0x25 -> Node 1
SRAT: PXM 1 -> APIC 0x07 -> Node 0
SRAT: PXM 2 -> APIC 0x27 -> Node 1
SRAT: PXM 1 -> APIC 0x09 -> Node 0
SRAT: PXM 2 -> APIC 0x29 -> Node 1
SRAT: PXM 1 -> APIC 0x0b -> Node 0
SRAT: PXM 2 -> APIC 0x2b -> Node 1
SRAT: PXM 1 -> APIC 0x0d -> Node 0
SRAT: PXM 2 -> APIC 0x2d -> Node 1
SRAT: PXM 1 -> APIC 0x0f -> Node 0
SRAT: PXM 2 -> APIC 0x2f -> Node 1
SRAT: Node 0 PXM 1 [mem 0x00000000-0x303fffffff]
SRAT: Node 1 PXM 2 [mem 0x3040000000-0x603fffffff]
Initmem setup node 0 [mem 0x00000000-0x1effafff]
  NODE_DATA [mem 0x1e62b000-0x1e63efff]
 [ffffea0000000000-ffffea00007fffff] PMD -> [ffff88001d600000-ffff88001ddfffff] on node 0
Zone ranges:
  DMA      [mem 0x00010000-0x00ffffff]
  DMA32    [mem 0x01000000-0xffffffff]
  Normal   empty
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x00010000-0x0009ffff]
  node   0: [mem 0x070a0000-0x1effafff]
On node 0 totalpages: 98283
  DMA zone: 3 pages used for memmap
  DMA zone: 10 pages reserved
  DMA zone: 131 pages, LIFO batch:0
  DMA32 zone: 1534 pages used for memmap
  DMA32 zone: 96605 pages, LIFO batch:31
pci 0000:01:00.0 save state
pci 0000:01:00.1 save state
pci 0000:01:00.2 save state
pci 0000:01:00.3 save state
pci 0000:02:00.0 save state
pci 0000:05:00.0 save state
pci 0000:48:00.0 save state
pci 0000:48:00.1 save state
pci 0000:44:00.0 save state
pci 0000:45:00.0 save state
pci 0000:46:00.0 save state
pci 0000:47:00.0 save state
pci 0000:00:01.0 reset
pci 0000:00:02.2 reset
pci 0000:00:03.2 reset
pci 0000:40:02.0 reset
pci 0000:42:05.0 reset
pci 0000:42:06.0 reset
pci 0000:42:08.0 reset
pci 0000:42:09.0 reset
pci 0000:01:00.0 restore state
pci 0000:01:00.1 restore state
pci 0000:01:00.2 restore state
pci 0000:01:00.3 restore state
pci 0000:02:00.0 restore state
pci 0000:05:00.0 restore state
pci 0000:48:00.0 restore state
pci 0000:48:00.1 restore state
pci 0000:44:00.0 restore state
pci 0000:45:00.0 restore state
pci 0000:46:00.0 restore state
pci 0000:47:00.0 restore state
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x20] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x22] enabled)
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x24] enabled)
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x08] lapic_id[0x26] enabled)
ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] enabled)
ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x28] enabled)
ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] enabled)
ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2a] enabled)
ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] enabled)
ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2c] enabled)
ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] enabled)
ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2e] enabled)
ACPI: LAPIC (acpi_id[0x11] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x12] lapic_id[0x21] enabled)
ACPI: LAPIC (acpi_id[0x13] lapic_id[0x03] enabled)
ACPI: LAPIC (acpi_id[0x14] lapic_id[0x23] enabled)
ACPI: LAPIC (acpi_id[0x15] lapic_id[0x05] enabled)
ACPI: LAPIC (acpi_id[0x16] lapic_id[0x25] enabled)
ACPI: LAPIC (acpi_id[0x17] lapic_id[0x07] enabled)
ACPI: LAPIC (acpi_id[0x18] lapic_id[0x27] enabled)
ACPI: LAPIC (acpi_id[0x19] lapic_id[0x09] enabled)
ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x29] enabled)
ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x0b] enabled)
ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x2b] enabled)
ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x0d] enabled)
ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x2d] enabled)
ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x0f] enabled)
ACPI: LAPIC (acpi_id[0x20] lapic_id[0x2f] enabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x01] address[0xfec3f000] gsi_base[32])
IOAPIC[1]: apic_id 1, version 32, address 0xfec3f000, GSI 32-55
ACPI: IOAPIC (id[0x02] address[0xfec7f000] gsi_base[64])
IOAPIC[2]: apic_id 2, version 32, address 0xfec7f000, GSI 64-87
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a701 base: 0xfed00000
smpboot: Allowing 32 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 104
PM: Registered nosave memory: 00000000000a0000 - 00000000070a0000
e820: [mem 0x1effb000-0xbd31bfff] available for PCI devices
Booting paravirtualized kernel on bare hardware
setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:32 nr_node_ids:2
PERCPU: Embedded 27 pages/cpu @ffff88001e000000 s81728 r8192 d20672 u131072
pcpu-alloc: s81728 r8192 d20672 u131072 alloc=1*2097152
pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
pcpu-alloc: [0] 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 96736
Policy zone: DMA32
Kernel command line: root=/dev/disk/by-label/ROOT-BE2 resume=/dev/disk/by-id/scsi-36d4ae52076eef400K
Disabling memory control group subsystem
Misrouted IRQ fixup and polling support enabled
This may significantly impact system performance
PID hash table entries: 2048 (order: 2, 16384 bytes)
__ex_table already sorted, skipping sort
xsave: enabled xstate_bv 0x7, cntxt size 0x340
Checking aperture...
No AGP bridge found
Memory: 357688k/507884k available (5832k kernel code, 114752k absent, 35444k reserved, 5095k data, )
Hierarchical RCU implementation.
        RCU dyntick-idle grace-period acceleration is enabled.
        RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=32.
NR_IRQS:33024 nr_irqs:2024 16
Extended CMOS year: 2000
Spurious LAPIC timer interrupt on cpu 0
Console: colour VGA+ 80x25
console [tty0] enabled
console [ttyS0] enabled
Enabling automatic NUMA balancing. Configure with numa_balancing= or sysctl
hpet clockevent registered
tsc: Fast TSC calibration using PIT
tsc: Detected 2700.011 MHz processor
Calibrating delay loop (skipped), value calculated using timer frequency.. 5400.02 BogoMIPS (lpj=10)
pid_max: default: 32768 minimum: 301
Security Framework initialized
AppArmor: AppArmor initialized
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 256
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
Initializing cgroup subsys blkio
Initializing cgroup subsys perf_event
Initializing cgroup subsys hugetlb
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 6
mce: CPU supports 20 MCE banks
CPU0: Thermal LVT vector (0xfa) already installed
process: using mwait in idle threads
Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0
Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32
tlb_flushall_shift: 5
ACPI: Core revision 20121018
dmar: Host address width 46
dmar: DRHD base: 0x000000d0d00000 flags: 0x0
dmar: IOMMU 0: reg_base_addr d0d00000 ver 1:0 cap d2078c106f0462 ecap f020fe
dmar: DRHD base: 0x000000dc900000 flags: 0x1
dmar: IOMMU 1: reg_base_addr dc900000 ver 1:0 cap d2078c106f0462 ecap f020fe
dmar: RMRR base: 0x000000bf458000 end: 0x000000bf46ffff
dmar: RMRR base: 0x000000bf450000 end: 0x000000bf450fff
dmar: RMRR base: 0x000000bf452000 end: 0x000000bf452fff
dmar: ATSR flags: 0x0
IOAPIC id 2 under DRHD base  0xd0d00000 IOMMU 0
IOAPIC id 0 under DRHD base  0xdc900000 IOMMU 1
IOAPIC id 1 under DRHD base  0xdc900000 IOMMU 1
HPET id 0 under DRHD base 0xdc900000
------------[ cut here ]------------
WARNING: at drivers/iommu/intel_irq_remapping.c:542 intel_enable_irq_remapping+0x7d/0x26f()
Hardware name: PowerEdge R720
Your BIOS is broken and requested that x2apic be disabled
This will leave your machine vulnerable to irq-injection attacks
Use 'intremap=no_x2apic_optout' to override BIOS request
Modules linked in:
Pid: 1, comm: swapper/0 Not tainted 3.8.0-rc2-default+ #4
Call Trace:
 [<ffffffff81047e2a>] warn_slowpath_common+0x7a/0xb0
 [<ffffffff81047f01>] warn_slowpath_fmt+0x41/0x50
 [<ffffffff81afe7ac>] intel_enable_irq_remapping+0x7d/0x26f
 [<ffffffff81afeaf0>] irq_remapping_enable+0x20/0x22
 [<ffffffff81acf048>] enable_IR+0x5d/0x65
 [<ffffffff81acf334>] enable_IR_x2apic+0x95/0x247
 [<ffffffff81026099>] ? cpumask_next+0x19/0x20
 [<ffffffff8159b9b8>] ? set_cpu_sibling_map+0x405/0x422
 [<ffffffff81026831>] ? apic_write+0x11/0x20
 [<ffffffff81ad1e83>] default_setup_apic_routing+0x15/0x6e
 [<ffffffff81accf43>] native_smp_prepare_cpus+0x137/0x234
 [<ffffffff81ac1c8e>] kernel_init_freeable+0xa2/0x1e1
 [<ffffffff815928b0>] ? rest_init+0x80/0x80
 [<ffffffff815928b9>] kernel_init+0x9/0xf0
 [<ffffffff815ae5bc>] ret_from_fork+0x7c/0xb0
 [<ffffffff815928b0>] ? rest_init+0x80/0x80
---[ end trace 8f259c928ef86db3 ]---
Enabled IRQ remapping in xapic mode
x2apic not enabled, IRQ remapping is in xapic mode
Switched APIC routing to physical flat.
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
smpboot: CPU0: Genuine Intel(R) CPU  @ 2.70GHz (fam: 06, model: 2d, stepping: 05)
TSC deadline timer enabled
Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, Intel PMU driver.
perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode
... version:                3
... bit width:              48
... generic registers:      4
... value mask:             0000ffffffffffff
... max period:             000000007fffffff
... fixed-purpose events:   3
... event mask:             000000070000000f
Brought up 1 CPUs
smpboot: Total of 1 processors activated (5400.02 BogoMIPS)
devtmpfs: initialized
RTC time:  0:09:43, date: 01/08/13
NET: Registered protocol family 16
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: not using MMCONFIG
PCI: Using configuration type 1 for base access
PCI: Dell System detected, enabling pci=bfsort.
bio: create slab <bio-0> at 0
ACPI: Added _OSI(Module Device)
ACPI: Added _OSI(Processor Device)
ACPI: Added _OSI(3.0 _SCP Extensions)
ACPI: Added _OSI(Processor Aggregator Device)
ACPI: EC: Look up EC in DSDT
[Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
ACPI: Interpreter enabled
ACPI: (supports S0 S4 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
PCI: MMCONFIG for 0000 [bus00-1f] at [mem 0xe0000000-0xe1ffffff] (base 0xe0000000) (size reduced!)
ACPI: No dock devices found.
HEST: Table parsing has been initialized.
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3d])
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
pci_root PNP0A08:00: Requesting ACPI _OSC control (0x15)
pci_root PNP0A08:00: ACPI _OSC control (0x15) granted
pci_root PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-1f] only partially covers the
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [bus 00-3d]
pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
pci_bus 0000:00: root bus resource [io  0x0d00-0x1fff]
pci_bus 0000:00: root bus resource [io  0x8000-0x9fff]
pci_bus 0000:00: root bus resource [io  0xa000-0xbfff]
pci_bus 0000:00: root bus resource [io  0xc000-0xdfff]
pci_bus 0000:00: root bus resource [io  0xe000-0xffff]
pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: root bus resource [mem 0xd4000000-0xdfffffff]
pci_bus 0000:00: root bus resource [mem 0xfed10000-0xfed103ff]
pci_bus 0000:00: root bus resource [mem 0xfed11000-0xfed113ff]
pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff]
pci 0000:00:00.0: [8086:3c00] type 00 class 0x060000
pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: [8086:3c02] type 01 class 0x060400
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:02.0: [8086:3c04] type 01 class 0x060400
pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
pci 0000:00:02.2: [8086:3c06] type 01 class 0x060400
pci 0000:00:02.2: PME# supported from D0 D3hot D3cold
pci 0000:00:03.0: [8086:3c08] type 01 class 0x060400
pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
pci 0000:00:03.2: [8086:3c0a] type 01 class 0x060400
pci 0000:00:03.2: PME# supported from D0 D3hot D3cold
pci 0000:00:05.0: [8086:3c28] type 00 class 0x088000
pci 0000:00:05.2: [8086:3c2a] type 00 class 0x088000
pci 0000:00:11.0: [8086:1d3e] type 01 class 0x060400
pci 0000:00:11.0: PME# supported from D0 D3hot D3cold
pci 0000:00:16.0: [8086:1d3a] type 00 class 0x078000
pci 0000:00:16.0: reg 10: [mem 0xfed10000-0xfed1000f 64bit]
pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
pci 0000:00:16.1: [8086:1d3b] type 00 class 0x078000
pci 0000:00:16.1: reg 10: [mem 0xfed11000-0xfed1100f 64bit]
pci 0000:00:16.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.0: [8086:1d2d] type 00 class 0x0c0320
pci 0000:00:1a.0: reg 10: [mem 0xdc8fd000-0xdc8fd3ff]
pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: [8086:1d10] type 01 class 0x060400
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.7: [8086:1d1e] type 01 class 0x060400
pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.0: [8086:1d26] type 00 class 0x0c0320
pci 0000:00:1d.0: reg 10: [mem 0xdc8fe000-0xdc8fe3ff]
pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
pci 0000:00:1f.0: [8086:1d41] type 00 class 0x060100
pci 0000:00:1f.2: [8086:1d02] type 00 class 0x010601
pci 0000:00:1f.2: reg 10: [io  0xcce8-0xccef]
pci 0000:00:1f.2: reg 14: [io  0xccf8-0xccfb]
pci 0000:00:1f.2: reg 18: [io  0xccf0-0xccf7]
pci 0000:00:1f.2: reg 1c: [io  0xccfc-0xccff]
pci 0000:00:1f.2: reg 20: [io  0xccc0-0xccdf]
pci 0000:00:1f.2: reg 24: [mem 0xdc8ff000-0xdc8ff7ff]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:01:00.0: [8086:1521] type 00 class 0x020000
pci 0000:01:00.0: reg 10: [mem 0xd8b00000-0xd8bfffff]
pci 0000:01:00.0: reg 18: [io  0xfc80-0xfc9f]
pci 0000:01:00.0: reg 1c: [mem 0xd8ff0000-0xd8ff3fff]
pci 0000:01:00.0: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
pci 0000:01:00.1: [8086:1521] type 00 class 0x020000
pci 0000:01:00.1: reg 10: [mem 0xd8c00000-0xd8cfffff]
pci 0000:01:00.1: reg 18: [io  0xfca0-0xfcbf]
pci 0000:01:00.1: reg 1c: [mem 0xd8ff4000-0xd8ff7fff]
pci 0000:01:00.1: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.1: PME# supported from D0 D3hot D3cold
pci 0000:01:00.2: [8086:1521] type 00 class 0x020000
pci 0000:01:00.2: reg 10: [mem 0xd8d00000-0xd8dfffff]
pci 0000:01:00.2: reg 18: [io  0xfcc0-0xfcdf]
pci 0000:01:00.2: reg 1c: [mem 0xd8ff8000-0xd8ffbfff]
pci 0000:01:00.2: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.2: PME# supported from D0 D3hot D3cold
pci 0000:01:00.3: [8086:1521] type 00 class 0x020000
pci 0000:01:00.3: reg 10: [mem 0xd8e00000-0xd8efffff]
pci 0000:01:00.3: reg 18: [io  0xfce0-0xfcff]
pci 0000:01:00.3: reg 1c: [mem 0xd8ffc000-0xd8ffffff]
pci 0000:01:00.3: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.3: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:01.0:   bridge window [io  0xf000-0xffff]
pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xd8ffffff]
pci 0000:00:01.0:   bridge window [mem 0xd5000000-0xd51fffff 64bit pref]
pci 0000:00:02.0: PCI bridge to [bus 03]
pci 0000:00:02.2: PCI bridge to [bus 02]
pci 0000:00:02.2:   bridge window [io  0xe000-0xefff]
pci 0000:00:02.2:   bridge window [mem 0xd9000000-0xd9ffffff]
pci 0000:00:03.0: PCI bridge to [bus 04]
pci 0000:05:00.0: [1000:0064] type 00 class 0x010700
pci 0000:05:00.0: reg 10: [io  0xdc00-0xdcff]
pci 0000:05:00.0: reg 14: [mem 0xdaffc000-0xdaffffff 64bit]
pci 0000:05:00.0: reg 1c: [mem 0xdaf80000-0xdafbffff 64bit]
pci 0000:05:00.0: reg 30: [mem 0xda000000-0xda07ffff pref]
pci 0000:05:00.0: supports D1 D2
pci 0000:00:03.2: PCI bridge to [bus 05]
pci 0000:00:03.2:   bridge window [io  0xd000-0xdfff]
pci 0000:00:03.2:   bridge window [mem 0xda000000-0xdaffffff]
pci 0000:00:11.0: PCI bridge to [bus 06]
pci 0000:00:1c.0: PCI bridge to [bus 07]
pci 0000:08:00.0: [1912:0013] type 01 class 0x060400
pci 0000:08:00.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.7: PCI bridge to [bus 08-0c]
pci 0000:00:1c.7:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:00:1c.7:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:00.0: [1912:0013] type 01 class 0x060400
pci 0000:09:00.0: PME# supported from D0 D3hot D3cold
pci 0000:09:01.0: [1912:0013] type 01 class 0x060400
pci 0000:09:01.0: PME# supported from D0 D3hot D3cold
pci 0000:08:00.0: PCI bridge to [bus 09-0c]
pci 0000:08:00.0:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:08:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:0a:00.0: [1912:0012] type 01 class 0x060400
pci 0000:09:00.0: PCI bridge to [bus 0a-0b]
pci 0000:09:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:09:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:0b:00.0: [102b:0534] type 00 class 0x030000
pci 0000:0b:00.0: reg 10: [mem 0xd4000000-0xd4ffffff pref]
pci 0000:0b:00.0: reg 14: [mem 0xdbffc000-0xdbffffff]
pci 0000:0b:00.0: reg 18: [mem 0xdb000000-0xdb7fffff]
pci 0000:0a:00.0: PCI bridge to [bus 0b]
pci 0000:0a:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:0a:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:01.0: PCI bridge to [bus 0c]
pci 0000:09:01.0:   bridge window [mem 0xdc700000-0xdc7fffff]
pci 0000:00:1e.0: PCI bridge to [bus 0d] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0000-0x03af] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x03e0-0x0cf7] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x03b0-0x03df] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0d00-0x1fff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x8000-0x9fff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0xa000-0xbfff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0xc000-0xdfff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0xe000-0xffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xd4000000-0xdfffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xfed10000-0xfed103ff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xfed11000-0xfed113ff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xfed40000-0xfed44fff] (subtractive decode)
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX5._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6._PRT]
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 40-7e])
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1._PRT]
pci_root PNP0A08:01: Requesting ACPI _OSC control (0x15)
pci_root PNP0A08:01: ACPI _OSC control (0x15) granted
pci_root PNP0A08:01: fail to add MMCONFIG information, can't access extended PCI configuration spac.
PCI host bridge to bus 0000:40
pci_bus 0000:40: root bus resource [bus 40-7e]
pci_bus 0000:40: root bus resource [io  0x2000-0x3fff]
pci_bus 0000:40: root bus resource [io  0x4000-0x5fff]
pci_bus 0000:40: root bus resource [io  0x6000-0x7fff]
pci_bus 0000:40: root bus resource [mem 0xcc000000-0xd3ffffff]
pci 0000:40:01.0: [8086:3c02] type 01 class 0x060400
pci 0000:40:01.0: PME# supported from D0 D3hot D3cold
pci 0000:40:02.0: [8086:3c04] type 01 class 0x060400
pci 0000:40:02.0: PME# supported from D0 D3hot D3cold
pci 0000:40:03.0: [8086:3c08] type 01 class 0x060400
pci 0000:40:03.0: PME# supported from D0 D3hot D3cold
pci 0000:40:03.2: [8086:3c0a] type 01 class 0x060400
pci 0000:40:03.2: PME# supported from D0 D3hot D3cold
pci 0000:40:05.0: [8086:3c28] type 00 class 0x088000
pci 0000:40:05.2: [8086:3c2a] type 00 class 0x088000
pci 0000:41:00.0: [10b5:8624] type 01 class 0x060400
pci 0000:41:00.0: reg 10: [mem 0xd0ce0000-0xd0cfffff]
pci 0000:41:00.0: PME# supported from D0 D3hot D3cold
pci 0000:40:01.0: PCI bridge to [bus 41-47]
pci 0000:40:01.0:   bridge window [io  0x2000-0x3fff]
pci 0000:40:01.0:   bridge window [mem 0xd0800000-0xd0cfffff]
pci 0000:40:01.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:42:04.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:04.0: PME# supported from D0 D3hot D3cold
pci 0000:42:05.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:05.0: PME# supported from D0 D3hot D3cold
pci 0000:42:06.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:06.0: PME# supported from D0 D3hot D3cold
pci 0000:42:08.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:08.0: PME# supported from D0 D3hot D3cold
pci 0000:42:09.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:09.0: PME# supported from D0 D3hot D3cold
pci 0000:41:00.0: PCI bridge to [bus 42-47]
pci 0000:41:00.0:   bridge window [io  0x2000-0x3fff]
pci 0000:41:00.0:   bridge window [mem 0xd0800000-0xd0bfffff]
pci 0000:41:00.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:42:04.0: PCI bridge to [bus 43]
pci 0000:44:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:44:00.0: reg 10: [mem 0xd08ff000-0xd08fffff 64bit]
pci 0000:44:00.0: supports D1
pci 0000:44:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:05.0: PCI bridge to [bus 44]
pci 0000:42:05.0:   bridge window [io  0x2000-0x2fff]
pci 0000:42:05.0:   bridge window [mem 0xd0800000-0xd08fffff]
pci 0000:42:05.0:   bridge window [mem 0xcc200000-0xcc3fffff 64bit pref]
pci 0000:45:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:45:00.0: reg 10: [mem 0xd09ff000-0xd09fffff 64bit]
pci 0000:45:00.0: supports D1
pci 0000:45:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:06.0: PCI bridge to [bus 45]
pci 0000:42:06.0:   bridge window [mem 0xd0900000-0xd09fffff]
pci 0000:46:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:46:00.0: reg 10: [mem 0xd0aff000-0xd0afffff 64bit]
pci 0000:46:00.0: supports D1
pci 0000:46:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:08.0: PCI bridge to [bus 46]
pci 0000:42:08.0:   bridge window [mem 0xd0a00000-0xd0afffff]
pci 0000:47:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:47:00.0: reg 10: [mem 0xd0bff000-0xd0bfffff 64bit]
pci 0000:47:00.0: supports D1
pci 0000:47:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:09.0: PCI bridge to [bus 47]
pci 0000:42:09.0:   bridge window [io  0x3000-0x3fff]
pci 0000:42:09.0:   bridge window [mem 0xd0b00000-0xd0bfffff]
pci 0000:42:09.0:   bridge window [mem 0xcc400000-0xcc5fffff 64bit pref]
pci 0000:48:00.0: [8086:10fb] type 00 class 0x020000
pci 0000:48:00.0: reg 10: [mem 0xcc080000-0xcc0fffff 64bit pref]
pci 0000:48:00.0: reg 18: [io  0x7cc0-0x7cdf]
pci 0000:48:00.0: reg 20: [mem 0xcc1f8000-0xcc1fbfff 64bit pref]
pci 0000:48:00.0: reg 30: [mem 0xd0000000-0xd007ffff pref]
pci 0000:48:00.0: PME# supported from D0 D3hot
pci 0000:48:00.1: [8086:10fb] type 00 class 0x020000
pci 0000:48:00.1: reg 10: [mem 0xcc100000-0xcc17ffff 64bit pref]
pci 0000:48:00.1: reg 18: [io  0x7ce0-0x7cff]
pci 0000:48:00.1: reg 20: [mem 0xcc1fc000-0xcc1fffff 64bit pref]
pci 0000:48:00.1: reg 30: [mem 0xd0000000-0xd007ffff pref]
pci 0000:48:00.1: PME# supported from D0 D3hot
pci 0000:40:02.0: PCI bridge to [bus 48]
pci 0000:40:02.0:   bridge window [io  0x7000-0x7fff]
pci 0000:40:02.0:   bridge window [mem 0xd0000000-0xd07fffff]
pci 0000:40:02.0:   bridge window [mem 0xcc000000-0xcc1fffff 64bit pref]
pci 0000:40:03.0: PCI bridge to [bus 49]
pci 0000:40:03.2: PCI bridge to [bus 4a]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXB._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXC._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXD._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXE._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Root Bridge [P0B1] (domain 0000 [bus 3f])
pci_root PNP0A08:02: ACPI _OSC support notification failed, disabling PCIe ASPM
pci_root PNP0A08:02: Unable to request _OSC control (_OSC support mask: 0x08)
pci_root PNP0A08:02: fail to add MMCONFIG information, can't access extended PCI configuration spac.
PCI host bridge to bus 0000:3f
pci_bus 0000:3f: root bus resource [bus 3f]
pci 0000:3f:08.0: [8086:3c80] type 00 class 0x088000
pci 0000:3f:09.0: [8086:3c90] type 00 class 0x088000
pci 0000:3f:0a.0: [8086:3cc0] type 00 class 0x088000
pci 0000:3f:0a.1: [8086:3cc1] type 00 class 0x088000
pci 0000:3f:0a.2: [8086:3cc2] type 00 class 0x088000
pci 0000:3f:0a.3: [8086:3cd0] type 00 class 0x088000
pci 0000:3f:0b.0: [8086:3ce0] type 00 class 0x088000
pci 0000:3f:0b.3: [8086:3ce3] type 00 class 0x088000
pci 0000:3f:0c.0: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.1: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.2: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.3: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.6: [8086:3cf4] type 00 class 0x088000
pci 0000:3f:0c.7: [8086:3cf6] type 00 class 0x088000
pci 0000:3f:0d.0: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.1: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.2: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.3: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.6: [8086:3cf5] type 00 class 0x088000
pci 0000:3f:0e.0: [8086:3ca0] type 00 class 0x088000
pci 0000:3f:0e.1: [8086:3c46] type 00 class 0x110100
pci 0000:3f:0f.0: [8086:3ca8] type 00 class 0x088000
pci 0000:3f:0f.1: [8086:3c71] type 00 class 0x088000
pci 0000:3f:0f.2: [8086:3caa] type 00 class 0x088000
pci 0000:3f:0f.3: [8086:3cab] type 00 class 0x088000
pci 0000:3f:0f.4: [8086:3cac] type 00 class 0x088000
pci 0000:3f:0f.5: [8086:3cad] type 00 class 0x088000
pci 0000:3f:0f.6: [8086:3cae] type 00 class 0x088000
pci 0000:3f:10.0: [8086:3cb0] type 00 class 0x088000
pci 0000:3f:10.1: [8086:3cb1] type 00 class 0x088000
pci 0000:3f:10.2: [8086:3cb2] type 00 class 0x088000
pci 0000:3f:10.3: [8086:3cb3] type 00 class 0x088000
pci 0000:3f:10.4: [8086:3cb4] type 00 class 0x088000
pci 0000:3f:10.5: [8086:3cb5] type 00 class 0x088000
pci 0000:3f:10.6: [8086:3cb6] type 00 class 0x088000
pci 0000:3f:10.7: [8086:3cb7] type 00 class 0x088000
pci 0000:3f:11.0: [8086:3cb8] type 00 class 0x088000
pci 0000:3f:13.0: [8086:3ce4] type 00 class 0x088000
pci 0000:3f:13.1: [8086:3c43] type 00 class 0x110100
pci 0000:3f:13.4: [8086:3ce6] type 00 class 0x110100
pci 0000:3f:13.5: [8086:3c44] type 00 class 0x110100
pci 0000:3f:13.6: [8086:3c45] type 00 class 0x088000
ACPI: Invalid Power Resource to register!
ACPI _OSC control for PCIe not granted, disabling ASPM
ACPI: PCI Interrupt Link [LK00] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK01] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK02] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK03] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK04] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK05] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK06] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK07] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
vgaarb: device added: PCI:0000:0b:00.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
vgaarb: bridge control possible 0000:0b:00.0
SCSI subsystem initialized
ACPI: bus type scsi registered
libata version 3.00 loaded.
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
e820: reserve RAM buffer [mem 0x1effb000-0x1fffffff]
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Switching to clocksource hpet
AppArmor: AppArmor Filesystem Enabled
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:00: [dma 4]
pnp 00:00: Plug and Play ACPI device, IDs PNP0200 (active)
pnp 00:01: Plug and Play ACPI device, IDs PNP0c04 (active)
system 00:02: Plug and Play ACPI device, IDs PNP0c01 (active)
pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)
pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active)
system 00:06: [io  0x0800-0x087f] has been reserved
system 00:06: [io  0x0880-0x08ff] has been reserved
system 00:06: [io  0x0900-0x091f] has been reserved
system 00:06: [io  0x0920-0x0923] has been reserved
system 00:06: [io  0x0924] has been reserved
system 00:06: [io  0x0370-0x0377] has been reserved
system 00:06: [io  0x0ca0-0x0ca7] has been reserved
system 00:06: [io  0x0ca9-0x0cab] has been reserved
system 00:06: [io  0x0cad-0x0caf] has been reserved
system 00:06: [io  0x0cb0-0x0cbf] has been reserved
system 00:06: Plug and Play ACPI device, IDs PNP0c01 (active)
system 00:07: [io  0x0ca8] has been reserved
system 00:07: [io  0x0cac] has been reserved
system 00:07: Plug and Play ACPI device, IDs IPI0001 PNP0c01 (active)
system 00:08: [mem 0xe0000000-0xe3efffff] has been reserved
system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:09: [mem 0xe4000000-0xe7ffffff] has been reserved
system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:0a: [mem 0xe3f00000-0xe3ffffff] has been reserved
system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:0b: [mem 0xdc900000-0xdc901fff] could not be reserved
system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:0c: [mem 0xd0d00000-0xd0d01fff] could not be reserved
system 00:0c: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
pci 0000:01:00.1: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:]
pci 0000:01:00.2: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:]
pci 0000:01:00.3: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:]
pci 0000:48:00.1: address space collision: [mem 0xd0000000-0xd007ffff pref] conflicts with 0000:48:]
pci 0000:01:00.1: BAR 6: assigned [mem 0xd5000000-0xd507ffff pref]
pci 0000:01:00.2: BAR 6: assigned [mem 0xd5080000-0xd50fffff pref]
pci 0000:01:00.3: BAR 6: assigned [mem 0xd5100000-0xd517ffff pref]
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:01.0:   bridge window [io  0xf000-0xffff]
pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xd8ffffff]
pci 0000:00:01.0:   bridge window [mem 0xd5000000-0xd51fffff 64bit pref]
pci 0000:00:02.0: PCI bridge to [bus 03]
pci 0000:00:02.2: PCI bridge to [bus 02]
pci 0000:00:02.2:   bridge window [io  0xe000-0xefff]
pci 0000:00:02.2:   bridge window [mem 0xd9000000-0xd9ffffff]
pci 0000:00:03.0: PCI bridge to [bus 04]
pci 0000:00:03.2: PCI bridge to [bus 05]
pci 0000:00:03.2:   bridge window [io  0xd000-0xdfff]
pci 0000:00:03.2:   bridge window [mem 0xda000000-0xdaffffff]
pci 0000:00:11.0: PCI bridge to [bus 06]
pci 0000:00:1c.0: PCI bridge to [bus 07]
pci 0000:0a:00.0: PCI bridge to [bus 0b]
pci 0000:0a:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:0a:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:00.0: PCI bridge to [bus 0a-0b]
pci 0000:09:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:09:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:01.0: PCI bridge to [bus 0c]
pci 0000:09:01.0:   bridge window [mem 0xdc700000-0xdc7fffff]
pci 0000:08:00.0: PCI bridge to [bus 09-0c]
pci 0000:08:00.0:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:08:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:00:1c.7: PCI bridge to [bus 08-0c]
pci 0000:00:1c.7:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:00:1c.7:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 0d]
pci 0000:42:04.0: PCI bridge to [bus 43]
pci 0000:42:05.0: PCI bridge to [bus 44]
pci 0000:42:05.0:   bridge window [io  0x2000-0x2fff]
pci 0000:42:05.0:   bridge window [mem 0xd0800000-0xd08fffff]
pci 0000:42:05.0:   bridge window [mem 0xcc200000-0xcc3fffff 64bit pref]
pci 0000:42:06.0: PCI bridge to [bus 45]
pci 0000:42:06.0:   bridge window [mem 0xd0900000-0xd09fffff]
pci 0000:42:08.0: PCI bridge to [bus 46]
pci 0000:42:08.0:   bridge window [mem 0xd0a00000-0xd0afffff]
pci 0000:42:09.0: PCI bridge to [bus 47]
pci 0000:42:09.0:   bridge window [io  0x3000-0x3fff]
pci 0000:42:09.0:   bridge window [mem 0xd0b00000-0xd0bfffff]
pci 0000:42:09.0:   bridge window [mem 0xcc400000-0xcc5fffff 64bit pref]
pci 0000:41:00.0: PCI bridge to [bus 42-47]
pci 0000:41:00.0:   bridge window [io  0x2000-0x3fff]
pci 0000:41:00.0:   bridge window [mem 0xd0800000-0xd0bfffff]
pci 0000:41:00.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:40:01.0: PCI bridge to [bus 41-47]
pci 0000:40:01.0:   bridge window [io  0x2000-0x3fff]
pci 0000:40:01.0:   bridge window [mem 0xd0800000-0xd0cfffff]
pci 0000:40:01.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:48:00.1: BAR 6: assigned [mem 0xcc000000-0xcc07ffff pref]
pci 0000:40:02.0: PCI bridge to [bus 48]
pci 0000:40:02.0:   bridge window [io  0x7000-0x7fff]
pci 0000:40:02.0:   bridge window [mem 0xd0000000-0xd07fffff]
pci 0000:40:02.0:   bridge window [mem 0xcc000000-0xcc1fffff 64bit pref]
pci 0000:40:03.0: PCI bridge to [bus 49]
pci 0000:40:03.2: PCI bridge to [bus 4a]
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
pci_bus 0000:00: resource 7 [io  0x0d00-0x1fff]
pci_bus 0000:00: resource 8 [io  0x8000-0x9fff]
pci_bus 0000:00: resource 9 [io  0xa000-0xbfff]
pci_bus 0000:00: resource 10 [io  0xc000-0xdfff]
pci_bus 0000:00: resource 11 [io  0xe000-0xffff]
pci_bus 0000:00: resource 12 [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: resource 13 [mem 0xd4000000-0xdfffffff]
pci_bus 0000:00: resource 14 [mem 0xfed10000-0xfed103ff]
pci_bus 0000:00: resource 15 [mem 0xfed11000-0xfed113ff]
pci_bus 0000:00: resource 16 [mem 0xfed40000-0xfed44fff]
pci_bus 0000:01: resource 0 [io  0xf000-0xffff]
pci_bus 0000:01: resource 1 [mem 0xd8000000-0xd8ffffff]
pci_bus 0000:01: resource 2 [mem 0xd5000000-0xd51fffff 64bit pref]
pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
pci_bus 0000:02: resource 1 [mem 0xd9000000-0xd9ffffff]
pci_bus 0000:05: resource 0 [io  0xd000-0xdfff]
pci_bus 0000:05: resource 1 [mem 0xda000000-0xdaffffff]
pci_bus 0000:08: resource 1 [mem 0xdb000000-0xdc7fffff]
pci_bus 0000:08: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:09: resource 1 [mem 0xdb000000-0xdc7fffff]
pci_bus 0000:09: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:0a: resource 1 [mem 0xdb000000-0xdbffffff]
pci_bus 0000:0a: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:0b: resource 1 [mem 0xdb000000-0xdbffffff]
pci_bus 0000:0b: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:0c: resource 1 [mem 0xdc700000-0xdc7fffff]
pci_bus 0000:0d: resource 4 [io  0x0000-0x03af]
pci_bus 0000:0d: resource 5 [io  0x03e0-0x0cf7]
pci_bus 0000:0d: resource 6 [io  0x03b0-0x03df]
pci_bus 0000:0d: resource 7 [io  0x0d00-0x1fff]
pci_bus 0000:0d: resource 8 [io  0x8000-0x9fff]
pci_bus 0000:0d: resource 9 [io  0xa000-0xbfff]
pci_bus 0000:0d: resource 10 [io  0xc000-0xdfff]
pci_bus 0000:0d: resource 11 [io  0xe000-0xffff]
pci_bus 0000:0d: resource 12 [mem 0x000a0000-0x000bffff]
pci_bus 0000:0d: resource 13 [mem 0xd4000000-0xdfffffff]
pci_bus 0000:0d: resource 14 [mem 0xfed10000-0xfed103ff]
pci_bus 0000:0d: resource 15 [mem 0xfed11000-0xfed113ff]
pci_bus 0000:0d: resource 16 [mem 0xfed40000-0xfed44fff]
pci_bus 0000:40: resource 4 [io  0x2000-0x3fff]
pci_bus 0000:40: resource 5 [io  0x4000-0x5fff]
pci_bus 0000:40: resource 6 [io  0x6000-0x7fff]
pci_bus 0000:40: resource 7 [mem 0xcc000000-0xd3ffffff]
pci_bus 0000:41: resource 0 [io  0x2000-0x3fff]
pci_bus 0000:41: resource 1 [mem 0xd0800000-0xd0cfffff]
pci_bus 0000:41: resource 2 [mem 0xcc200000-0xcc5fffff 64bit pref]
pci_bus 0000:42: resource 0 [io  0x2000-0x3fff]
pci_bus 0000:42: resource 1 [mem 0xd0800000-0xd0bfffff]
pci_bus 0000:42: resource 2 [mem 0xcc200000-0xcc5fffff 64bit pref]
pci_bus 0000:44: resource 0 [io  0x2000-0x2fff]
pci_bus 0000:44: resource 1 [mem 0xd0800000-0xd08fffff]
pci_bus 0000:44: resource 2 [mem 0xcc200000-0xcc3fffff 64bit pref]
pci_bus 0000:45: resource 1 [mem 0xd0900000-0xd09fffff]
pci_bus 0000:46: resource 1 [mem 0xd0a00000-0xd0afffff]
pci_bus 0000:47: resource 0 [io  0x3000-0x3fff]
pci_bus 0000:47: resource 1 [mem 0xd0b00000-0xd0bfffff]
pci_bus 0000:47: resource 2 [mem 0xcc400000-0xcc5fffff 64bit pref]
pci_bus 0000:48: resource 0 [io  0x7000-0x7fff]
pci_bus 0000:48: resource 1 [mem 0xd0000000-0xd07fffff]
pci_bus 0000:48: resource 2 [mem 0xcc000000-0xcc1fffff 64bit pref]
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 4, 65536 bytes)
TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
pci 0000:0b:00.0: Boot video device
PCI: CLS 64 bytes, default 64
Unpacking initramfs...
Freeing initrd memory: 5824k freed
audit: initializing netlink socket (disabled)
type=2000 audit(1357603783.820:1): initialized
HugeTLB registered 2 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 709
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler deadline registered (default)
io scheduler cfq registered
pcieport 0000:00:01.0: irq 106 for MSI/MSI-X
pcieport 0000:00:02.0: irq 107 for MSI/MSI-X
pcieport 0000:00:02.2: irq 108 for MSI/MSI-X
pcieport 0000:00:03.0: irq 109 for MSI/MSI-X
pcieport 0000:00:03.2: irq 110 for MSI/MSI-X
pcieport 0000:00:11.0: irq 111 for MSI/MSI-X
pcieport 0000:00:1c.0: irq 112 for MSI/MSI-X
pcieport 0000:00:1c.7: irq 113 for MSI/MSI-X
pcieport 0000:40:01.0: irq 114 for MSI/MSI-X
pcieport 0000:40:02.0: irq 115 for MSI/MSI-X
pcieport 0000:40:03.0: irq 116 for MSI/MSI-X
pcieport 0000:40:03.2: irq 117 for MSI/MSI-X
pcieport 0000:42:05.0: irq 118 for MSI/MSI-X
pcieport 0000:42:09.0: irq 119 for MSI/MSI-X
pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
pci 0000:01:00.2: Signaling PME through PCIe PME interrupt
pci 0000:01:00.3: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:02.2: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:02.2:pcie01: service driver pcie_pme loaded
pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:03.2: Signaling PME through PCIe PME interrupt
pci 0000:05:00.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:03.2:pcie01: service driver pcie_pme loaded
pcieport 0000:00:11.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:11.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
pcieport 0000:08:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:09:00.0: Signaling PME through PCIe PME interrupt
pci 0000:0a:00.0: Signaling PME through PCIe PME interrupt
pci 0000:0b:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:09:01.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
pcieport 0000:40:01.0: Signaling PME through PCIe PME interrupt
pcieport 0000:41:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:04.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:05.0: Signaling PME through PCIe PME interrupt
pci 0000:44:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:06.0: Signaling PME through PCIe PME interrupt
pci 0000:45:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:08.0: Signaling PME through PCIe PME interrupt
pci 0000:46:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:09.0: Signaling PME through PCIe PME interrupt
pci 0000:47:00.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:01.0:pcie01: service driver pcie_pme loaded
pcieport 0000:40:02.0: Signaling PME through PCIe PME interrupt
pci 0000:48:00.0: Signaling PME through PCIe PME interrupt
pci 0000:48:00.1: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:02.0:pcie01: service driver pcie_pme loaded
pcieport 0000:40:03.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:03.0:pcie01: service driver pcie_pme loaded
pcieport 0000:40:03.2: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:03.2:pcie01: service driver pcie_pme loaded
intel_idle: MWAIT substates: 0x21120
intel_idle: v0.4 model 0x2D
intel_idle: lapic_timer_reliable_states 0xffffffff
ERST: Error Record Serialization Table (ERST) support is initialized.
GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
00:04: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Non-volatile memory driver v1.3
Linux agpgart interface v0.103
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: irq 120 for MSI/MSI-X
ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ems apst
ahci 0000:00:1f.2: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff100 irq 120
ata2: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff180 irq 120
ata3: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff200 irq 120
ata4: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff280 irq 120
ata5: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff300 irq 120
ata6: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff380 irq 120
libphy: Fixed MDIO Bus: probed
i8042: PNP: No PS/2 controller found. Probing ports directly.
i8042: No controller found
tsc: Refined TSC clocksource calibration: 2699.999 MHz
Switching to clocksource tsc
mousedev: PS/2 mouse device common for all mice
rtc_cmos 00:03: RTC can wake from S4
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one day, y3k, 242 bytes nvram, hpet irqs
cpuidle: using governor ladder
cpuidle: using governor menu
ledtrig-cpu: registered to indicate activity on CPUs
EFI Variables Facility v0.08 2004-May-17
TCP: cubic registered
NET: Registered protocol family 10
Key type dns_resolver registered
PM: Checking hibernation image partition /dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-par8
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
ata1: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata6: SATA link down (SStatus 0 SControl 300)
ata5.00: ATAPI: TEAC DVD-ROM DV-28SW, R.2A, max UDMA/100
ata5.00: configured for UDMA/100
scsi 4:0:0:0: CD-ROM            TEAC     DVD-ROM DV-28SW  R.2A PQ: 0 ANSI: 5
PM: Hibernation image not present or could not be loaded.
registered taskstats version 1
  Magic number: 13:181:152
rtc_cmos 00:03: setting system clock to 2013-01-08 00:09:48 UTC (1357603788)
Freeing unused kernel memory: 1000k freed
Write protecting the kernel read-only data: 10240k
Freeing unused kernel memory: 300k freed
Freeing unused kernel memory: 1500k freed
doing fast boot
SysRq : Changing Loglevel
Loglevel set to 7
megasas: 06.504.01.00-rc1 Mon. Oct. 1 17:00:00 PDT 2012
FATAL: Module ahci not found.
teradata-kdump: Skipping mpt2sas
BIOS EDD facility v0.16 2004-Jun-25, 2 devices found
FATAL: Module jbd not found.
FATAL: Module ext3 not found.
preping 03-storage.sh
running 03-storage.sh
udevd (184): /proc/184/oom_adj is deprecated, please use /proc/184/oom_score_adj instead.

running 04-udev.sh
Creating deudevd version 128 started
vice nodes with udev
preping 05-blogd.sh
running 05-blogd.sh
mount: devpts already mounted or /dev/pts busy
mount: according to mtab, devpts is already mounted on /dev/pts
Boot logging started on /dev/ttyS0(/dev/console) at Mon Jan  7 19:09:49 2013
preping 05-clock.sh
running 05-clock.sh
preping 11-block.sh
running 11-block.sh
preping 11-usb.sh
running 11-usb.sh
preping 21-devinit_done.sh
running 21-devinit_done.sh
preping 81-mount.sh
running 81-mount.sh
Waiting for device /dev/disk/by-label/ROOT-BE2 to appear: ..........................................
.

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Yinghai Lu]

On Mon, Jan 7, 2013 at 4:42 PM, Thomas Renninger <trenn@suse.de> wrote:
> memmap=256M$3584M

may need to change to:

memmap=256M\$\$3584M

Thanks

Yinghai

[PATCH] Only reset e820 once, even with multiple memmap=exactmap params

[Thomas Renninger]

On Tuesday, January 08, 2013 04:04:56 AM Yinghai Lu wrote:
> On Mon, Jan 7, 2013 at 4:42 PM, Thomas Renninger <trenn@suse.de> wrote:
> > memmap=256M$3584M
> 
> may need to change to:
> 
> memmap=256M\$\$3584M
The problem is (beside the special char $) that
memmap=exactmap boot param resets all e820 maps every time the
parameter is processed.
And:
/sbin/kexec -p xy --append="..." --initrd yx
seem to magically add (append):
memmap=exactmap memmap=640K@0K memmap=392556K@115328K elfcorehdr=507884K memmap=252K#3099760K

therefore all memmap= I try to pass are voided out by:
memmap=exactmap
which is always added by kexec after my params.

I could come around with attached patch and passing:
/sbin/kexec -p xy --append='... memmap=exactmap memmap=256M$3584M' --initrd yx

Now mmconfig is working in kdump kernel.
This would mean mmconfig is broken by design in kexec?

Only way to fix this I can think of is to export
mmconfig area through /sys  (../kernel/debug/mmconfig?, possibly
already in X$Y format?) in the productive kernel and make kexec add it
like the other memmap= params automatically.

I'll attach the output in a separate mail.

   Thomas

---

x86 e820: Do not reset e820 map twice, even if memmap=exactmap is passed as boot param several times

This is needed to be able to explicitly pass (debug) e820
modifications through kexec via memmap=.
Otherwise those get voided by kexec appending memmap=exactmap always
after the user defined boot parameters.

Signed-off-by: Thomas Renninger <trenn@suse.de>

 linux-2.6_t/arch/x86/kernel/e820.c |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

Index: git/linux-2.6_t/arch/x86/kernel/e820.c
===================================================================
--- git.orig/linux-2.6_t/arch/x86/kernel/e820.c
+++ git/linux-2.6_t/arch/x86/kernel/e820.c
@@ -845,7 +845,9 @@ static int __init parse_memmap_opt(char
 
 	if (!strncmp(p, "exactmap", 8)) {
 #ifdef CONFIG_CRASH_DUMP
-		/*
+		/* memmap=exactmap passed twice, do not reset tables again */
+		if (saved_max_pfn)
+			return 0;		/*
 		 * If we are doing a crash dump, we still need to know
 		 * the real mem size before original memory map is
 		 * reset.

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Thomas Renninger]

On Monday, January 07, 2013 09:16:42 PM Yinghai Lu wrote:
> On Mon, Jan 7, 2013 at 11:09 AM, Thomas Renninger <trenn@suse.de> wrote:
...
> can you make sure kdump kernel command line take
> "memmap=256M$3584M" ?
> 
> it will make mmconf working.
> 
> > megasas: 06.504.01.00-rc1 Mon. Oct. 1 17:00:00 PDT 2012
> 
> also need to append "debug ignore_loglevel" to see why the disks are not
> probed.
Same output with above addtions (mmconf fixed in kdump
and debug ignore_loglevel passed as well and serial output
not truncated):

BTW: If you search for "Command line:" one can see why my explicity
memmap= tries failed...

^[[1mlinux-dwlr:/archteam/trenn/git/linux-2.6_t # ^[[m\x0fSysRq : Trigger a crash
BUG: unable to handle kernel NULL pointer dereference at           (null)
IP: [<ffffffff813b05b1>] sysrq_handle_crash+0x11/0x20
PGD 2f63259067 PUD 2f5ab85067 PMD 0 
Oops: 0002 [#1] SMP 
Modules linked in: nfsv3 nfs_acl nfs fscache lockd sunrpc af_packet igb ipmi_devintf ipmi_si ipmi_msghandler mperf fuse loop e1000 joydev hid_generic kvm_intel 
coretemp kvm crc32c_intel ghash_clmulni_intel aesni_intel ablk_helper cryptd lrw aes_x86_64 xts gf128mul usbhid iTCO_wdt iTCO_vendor_support gpio_ich dcdbas ixgbe 
ehci_pci ehci_hcd tpm_tis tpm usbcore shpchp tpm_bios pcspkr mptctl sr_mod dca microcode sb_edac mptbase lpc_ich pci_hotplug edac_core sg cdrom mfd_core mdio 
usb_common ptp button mei acpi_power_meter pps_core acpi_pad edd fan thermal processor thermal_sys mpt2sas scsi_transport_sas raid_class megaraid_sas
CPU 6 
Pid: 23403, comm: bash Tainted: G        W    3.8.0-rc2-default+ #4 Dell Inc. PowerEdge R720/0M1GCR
RIP: 0010:[<ffffffff813b05b1>]  [<ffffffff813b05b1>] sysrq_handle_crash+0x11/0x20
RSP: 0018:ffff882f5a9f1e38  EFLAGS: 00010092
RAX: 000000000000000f RBX: 0000000000000063 RCX: 00000000000019a9
RDX: 0000000000003aaa RSI: 0000000000000082 RDI: 0000000000000063
RBP: ffff882f5a9f1e38 R08: 0000000000021e2c R09: ffff88603fc00000
R10: 000000000000061b R11: 000000000000061a R12: ffffffff81a57ec0
R13: 0000000000000286 R14: 0000000000000001 R15: 0000000000000000
FS:  00007fc7262d4700(0000) GS:ffff882f7fc60000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000002f5a4bc000 CR4: 00000000000407e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process bash (pid: 23403, threadinfo ffff882f5a9f0000, task ffff882f5ab621c0)
Stack:
 ffff882f5a9f1e78 ffffffff813b0d29 ffff882f64365400 0000000000000002
 ffff882f63a838c0 00007fc726171000 0000000000000002 fffffffffffffffb
 ffff882f5a9f1e98 ffffffff813b0dcd ffff882f5a9f1eb8 ffff885f652fd8c0
Call Trace:
 [<ffffffff813b0d29>] __handle_sysrq+0x129/0x190
 [<ffffffff813b0dcd>] write_sysrq_trigger+0x3d/0x40
 [<ffffffff811d9d46>] proc_reg_write+0x76/0xb0
 [<ffffffff81177496>] vfs_write+0xc6/0x180
 [<ffffffff811777ca>] sys_write+0x5a/0xa0
 [<ffffffff815ae669>] system_call_fastpath+0x16/0x1b
Code: ff e9 78 ff ff ff 45 01 f4 45 39 65 2c 75 cd 4c 89 ef e8 83 f7 ff ff eb c3 90 55 c7 05 f5 f3 84 00 01 00 00 00 48 89 e5 0f ae f8 <c6> 04 25 00 00 00 00 01 c9 
c3 0f 1f 44 00 00 55 31 c0 48 89 e5 
RIP  [<ffffffff813b05b1>] sysrq_handle_crash+0x11/0x20
 RSP <ffff882f5a9f1e38>
CR2: 0000000000000000
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.8.0-rc2-default+ (trenn@ett) (gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux) ) #5 SMP Tue Jan 8 17:04:17 CET 2013
Command line: root=/dev/disk/by-label/ROOT-BE2 resume=/dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-part8 nmi_watchdog=0 elevator=noop log_buf_len=4M 
printk.time=0 udev_timeout=180 cgroup_disable=memory console=tty0 console=ttyS0,115200n elevator=deadline sysrq=yes reset_devices irqpoll maxcpus=1  sysrq=7 debug 
ignore_loglevel memmap=exactmap memmap=256M$3584M memmap=exactmap memmap=640K@0K memmap=392556K@115328K elfcorehdr=507884K memmap=252K#3099760K
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000100-0x000000000009bfff] usable
BIOS-e820: [mem 0x0000000000100000-0x00000000bd2effff] usable
BIOS-e820: [mem 0x00000000bd2f0000-0x00000000bd31bfff] reserved
BIOS-e820: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
BIOS-e820: [mem 0x00000000bd35b000-0x00000000bfffffff] reserved
BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
BIOS-e820: [mem 0x00000000fe000000-0x00000000ffffffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x000000603fffffff] usable
debug: ignoring loglevel setting.
e820: last_pfn = 0x6040000 max_arch_pfn = 0x400000000
NX (Execute Disable) protection: active
e820: user-defined physical RAM map:
user: [mem 0x0000000000000000-0x000000000009ffff] usable
user: [mem 0x00000000070a0000-0x000000001effafff] usable
user: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
user: [mem 0x00000000e0000000-0x00000000efffffff] reserved
SMBIOS 2.7 present.
DMI: Dell Inc. PowerEdge R720/0M1GCR, BIOS 0.3.35 12/15/2011
e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
e820: remove [mem 0x000a0000-0x000fffff] usable
No AGP bridge found
e820: last_pfn = 0x1effb max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-BFFFF uncachable
  C0000-CBFFF write-protect
  CC000-D7FFF write-back
  D8000-EBFFF uncachable
  EC000-FFFFF write-protect
MTRR variable ranges enabled:
  0 base 000000000000 mask 3FC000000000 write-back
  1 base 004000000000 mask 3FE000000000 write-back
  2 base 006000000000 mask 3FFFC0000000 write-back
  3 base 0000C0000000 mask 3FFFC0000000 uncachable
  4 disabled
  5 disabled
  6 disabled
  7 disabled
  8 disabled
  9 disabled
x86 PAT enabled: cpu 0, old 0x7010600070106, new 0x7010600070106
e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
found SMP MP-table at [mem 0x000fe710-0x000fe71f] mapped at [ffff8800000fe710]
initial memory mapped: [mem 0x00000000-0x1fffffff]
Base memory trampoline at [ffff880000096000] 96000 size 24576
Using GB pages for direct mapping
init_memory_mapping: [mem 0x00000000-0x1effafff]
 [mem 0x00000000-0x1edfffff] page 2M
 [mem 0x1ee00000-0x1effafff] page 4k
kernel direct mapping tables up to 0x1effafff @ [mem 0x1eff8000-0x1effafff]
log_buf_len: 4194304
early log buf free: 258268(98%)
RAMDISK: [mem 0x1ea3f000-0x1efeefff]
ACPI: RSDP 00000000000f10d0 00024 (v02 DELL  )
ACPI: XSDT 00000000000f11d4 0009C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: FACP 00000000bd34111c 000F4 (v03 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: DSDT 00000000bd31c000 05FCD (v01 DELL   PE_SC3   00000001 INTL 20110211)
ACPI: FACS 00000000bd343000 00040
ACPI: APIC 00000000bd340478 0016A (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SPCR 00000000bd3405e4 00050 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: HPET 00000000bd340638 00038 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: DMAR 00000000bd340674 00158 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: MCFG 00000000bd340950 0003C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: WD__ 00000000bd340990 00134 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SLIC 00000000bd340ac8 00176 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: ERST 00000000bd322170 00270 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: HEST 00000000bd3223e0 0055C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: BERT 00000000bd321fd0 00030 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: EINJ 00000000bd322000 00170 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SRAT 00000000bd340cf0 003C0 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: TCPA 00000000bd3410b4 00064 (v02 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SSDT 00000000bd344000 0AA14 (v01 INTEL  PPM RCM  80000001 INTL 20061109)
ACPI: Local APIC address 0xfee00000
SRAT: PXM 1 -> APIC 0x00 -> Node 0
SRAT: PXM 2 -> APIC 0x20 -> Node 1
SRAT: PXM 1 -> APIC 0x02 -> Node 0
SRAT: PXM 2 -> APIC 0x22 -> Node 1
SRAT: PXM 1 -> APIC 0x04 -> Node 0
SRAT: PXM 2 -> APIC 0x24 -> Node 1
SRAT: PXM 1 -> APIC 0x06 -> Node 0
SRAT: PXM 2 -> APIC 0x26 -> Node 1
SRAT: PXM 1 -> APIC 0x08 -> Node 0
SRAT: PXM 2 -> APIC 0x28 -> Node 1
SRAT: PXM 1 -> APIC 0x0a -> Node 0
SRAT: PXM 2 -> APIC 0x2a -> Node 1
SRAT: PXM 1 -> APIC 0x0c -> Node 0
SRAT: PXM 2 -> APIC 0x2c -> Node 1
SRAT: PXM 1 -> APIC 0x0e -> Node 0
SRAT: PXM 2 -> APIC 0x2e -> Node 1
SRAT: PXM 1 -> APIC 0x01 -> Node 0
SRAT: PXM 2 -> APIC 0x21 -> Node 1
SRAT: PXM 1 -> APIC 0x03 -> Node 0
SRAT: PXM 2 -> APIC 0x23 -> Node 1
SRAT: PXM 1 -> APIC 0x05 -> Node 0
SRAT: PXM 2 -> APIC 0x25 -> Node 1
SRAT: PXM 1 -> APIC 0x07 -> Node 0
SRAT: PXM 2 -> APIC 0x27 -> Node 1
SRAT: PXM 1 -> APIC 0x09 -> Node 0
SRAT: PXM 2 -> APIC 0x29 -> Node 1
SRAT: PXM 1 -> APIC 0x0b -> Node 0
SRAT: PXM 2 -> APIC 0x2b -> Node 1
SRAT: PXM 1 -> APIC 0x0d -> Node 0
SRAT: PXM 2 -> APIC 0x2d -> Node 1
SRAT: PXM 1 -> APIC 0x0f -> Node 0
SRAT: PXM 2 -> APIC 0x2f -> Node 1
SRAT: Node 0 PXM 1 [mem 0x00000000-0x303fffffff]
SRAT: Node 1 PXM 2 [mem 0x3040000000-0x603fffffff]
Initmem setup node 0 [mem 0x00000000-0x1effafff]
  NODE_DATA [mem 0x1e62b000-0x1e63efff]
 [ffffea0000000000-ffffea00007fffff] PMD -> [ffff88001d600000-ffff88001ddfffff] on node 0
Zone ranges:
  DMA      [mem 0x00010000-0x00ffffff]
  DMA32    [mem 0x01000000-0xffffffff]
  Normal   empty
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x00010000-0x0009ffff]
  node   0: [mem 0x070a0000-0x1effafff]
On node 0 totalpages: 98283
  DMA zone: 3 pages used for memmap
  DMA zone: 10 pages reserved
  DMA zone: 131 pages, LIFO batch:0
  DMA32 zone: 1534 pages used for memmap
  DMA32 zone: 96605 pages, LIFO batch:31
pci 0000:01:00.0 save state
pci 0000:01:00.1 save state
pci 0000:01:00.2 save state
pci 0000:01:00.3 save state
pci 0000:02:00.0 save state
pci 0000:05:00.0 save state
pci 0000:48:00.0 save state
pci 0000:48:00.1 save state
pci 0000:44:00.0 save state
pci 0000:45:00.0 save state
pci 0000:46:00.0 save state
pci 0000:47:00.0 save state
pci 0000:00:01.0 reset
pci 0000:00:02.2 reset
pci 0000:00:03.2 reset
pci 0000:40:02.0 reset
pci 0000:42:05.0 reset
pci 0000:42:06.0 reset
pci 0000:42:08.0 reset
pci 0000:42:09.0 reset
pci 0000:01:00.0 restore state
pci 0000:01:00.1 restore state
pci 0000:01:00.2 restore state
pci 0000:01:00.3 restore state
pci 0000:02:00.0 restore state
pci 0000:05:00.0 restore state
pci 0000:48:00.0 restore state
pci 0000:48:00.1 restore state
pci 0000:44:00.0 restore state
pci 0000:45:00.0 restore state
pci 0000:46:00.0 restore state
pci 0000:47:00.0 restore state
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x20] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x22] enabled)
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x24] enabled)
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x08] lapic_id[0x26] enabled)
ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] enabled)
ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x28] enabled)
ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] enabled)
ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2a] enabled)
ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] enabled)
ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2c] enabled)
ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] enabled)
ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2e] enabled)
ACPI: LAPIC (acpi_id[0x11] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x12] lapic_id[0x21] enabled)
ACPI: LAPIC (acpi_id[0x13] lapic_id[0x03] enabled)
ACPI: LAPIC (acpi_id[0x14] lapic_id[0x23] enabled)
ACPI: LAPIC (acpi_id[0x15] lapic_id[0x05] enabled)
ACPI: LAPIC (acpi_id[0x16] lapic_id[0x25] enabled)
ACPI: LAPIC (acpi_id[0x17] lapic_id[0x07] enabled)
ACPI: LAPIC (acpi_id[0x18] lapic_id[0x27] enabled)
ACPI: LAPIC (acpi_id[0x19] lapic_id[0x09] enabled)
ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x29] enabled)
ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x0b] enabled)
ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x2b] enabled)
ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x0d] enabled)
ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x2d] enabled)
ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x0f] enabled)
ACPI: LAPIC (acpi_id[0x20] lapic_id[0x2f] enabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x01] address[0xfec3f000] gsi_base[32])
IOAPIC[1]: apic_id 1, version 32, address 0xfec3f000, GSI 32-55
ACPI: IOAPIC (id[0x02] address[0xfec7f000] gsi_base[64])
IOAPIC[2]: apic_id 2, version 32, address 0xfec7f000, GSI 64-87
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a701 base: 0xfed00000
smpboot: Allowing 32 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 104
PM: Registered nosave memory: 00000000000a0000 - 00000000070a0000
e820: [mem 0x1effb000-0xbd31bfff] available for PCI devices
Booting paravirtualized kernel on bare hardware
setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:32 nr_node_ids:2
PERCPU: Embedded 27 pages/cpu @ffff88001e000000 s81728 r8192 d20672 u131072
pcpu-alloc: s81728 r8192 d20672 u131072 alloc=1*2097152
pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 
pcpu-alloc: [0] 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 96736
Policy zone: DMA32
Kernel command line: root=/dev/disk/by-label/ROOT-BE2 resume=/dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-part8 nmi_watchdog=0 elevator=noop 
log_buf_len=4M printk.time=0 udev_timeout=180 cgroup_disable=memory console=tty0 console=ttyS0,115200n elevator=deadline sysrq=yes reset_devices irqpoll maxcpus=1  
sysrq=7 debug ignore_loglevel memmap=exactmap memmap=256M$3584M memmap=exactmap memmap=640K@0K memmap=392556K@115328K elfcorehdr=507884K memmap=252K#3099760K
Disabling memory control group subsystem
Misrouted IRQ fixup and polling support enabled
This may significantly impact system performance
PID hash table entries: 2048 (order: 2, 16384 bytes)
__ex_table already sorted, skipping sort
xsave: enabled xstate_bv 0x7, cntxt size 0x340
Checking aperture...
No AGP bridge found
Memory: 357688k/507884k available (5832k kernel code, 114752k absent, 35444k reserved, 5095k data, 1000k init)
Hierarchical RCU implementation.
	RCU dyntick-idle grace-period acceleration is enabled.
	RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=32.
NR_IRQS:33024 nr_irqs:2024 16
Extended CMOS year: 2000
Spurious LAPIC timer interrupt on cpu 0
do_IRQ: 0.64 No irq handler for vector (irq -1)
Console: colour VGA+ 80x25
console [tty0] enabled
console [ttyS0] enabled
Enabling automatic NUMA balancing. Configure with numa_balancing= or sysctl
hpet clockevent registered
tsc: Fast TSC calibration using PIT
tsc: Detected 2699.996 MHz processor
Calibrating delay loop (skipped), value calculated using timer frequency.. 5399.99 BogoMIPS (lpj=10799984)
pid_max: default: 32768 minimum: 301
Security Framework initialized
AppArmor: AppArmor initialized
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 256
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
Initializing cgroup subsys blkio
Initializing cgroup subsys perf_event
Initializing cgroup subsys hugetlb
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 3
mce: CPU supports 20 MCE banks
CPU0: Thermal LVT vector (0xfa) already installed
process: using mwait in idle threads
Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0
Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32
tlb_flushall_shift: 5
ACPI: Core revision 20121018
dmar: Host address width 46
dmar: DRHD base: 0x000000d0d00000 flags: 0x0
dmar: IOMMU 0: reg_base_addr d0d00000 ver 1:0 cap d2078c106f0462 ecap f020fe
dmar: DRHD base: 0x000000dc900000 flags: 0x1
dmar: IOMMU 1: reg_base_addr dc900000 ver 1:0 cap d2078c106f0462 ecap f020fe
dmar: RMRR base: 0x000000bf458000 end: 0x000000bf46ffff
dmar: RMRR base: 0x000000bf450000 end: 0x000000bf450fff
dmar: RMRR base: 0x000000bf452000 end: 0x000000bf452fff
dmar: ATSR flags: 0x0
IOAPIC id 2 under DRHD base  0xd0d00000 IOMMU 0
IOAPIC id 0 under DRHD base  0xdc900000 IOMMU 1
IOAPIC id 1 under DRHD base  0xdc900000 IOMMU 1
HPET id 0 under DRHD base 0xdc900000
------------[ cut here ]------------
WARNING: at drivers/iommu/intel_irq_remapping.c:542 intel_enable_irq_remapping+0x7d/0x26f()
Hardware name: PowerEdge R720
Your BIOS is broken and requested that x2apic be disabled
This will leave your machine vulnerable to irq-injection attacks
Use 'intremap=no_x2apic_optout' to override BIOS request
Modules linked in:
Pid: 1, comm: swapper/0 Not tainted 3.8.0-rc2-default+ #5
Call Trace:
 [<ffffffff81047e2a>] warn_slowpath_common+0x7a/0xb0
 [<ffffffff81047f01>] warn_slowpath_fmt+0x41/0x50
 [<ffffffff81afe7ba>] intel_enable_irq_remapping+0x7d/0x26f
 [<ffffffff81afeafe>] irq_remapping_enable+0x20/0x22
 [<ffffffff81acf056>] enable_IR+0x5d/0x65
 [<ffffffff81acf342>] enable_IR_x2apic+0x95/0x247
 [<ffffffff81026099>] ? cpumask_next+0x19/0x20
 [<ffffffff8159b9b8>] ? set_cpu_sibling_map+0x405/0x422
 [<ffffffff81026831>] ? apic_write+0x11/0x20
 [<ffffffff81ad1e91>] default_setup_apic_routing+0x15/0x6e
 [<ffffffff81accf51>] native_smp_prepare_cpus+0x137/0x234
 [<ffffffff81ac1c8e>] kernel_init_freeable+0xa2/0x1e1
 [<ffffffff815928b0>] ? rest_init+0x80/0x80
 [<ffffffff815928b9>] kernel_init+0x9/0xf0
 [<ffffffff815ae5bc>] ret_from_fork+0x7c/0xb0
 [<ffffffff815928b0>] ? rest_init+0x80/0x80
---[ end trace 4561b4650a4b3e01 ]---
Enabled IRQ remapping in xapic mode
x2apic not enabled, IRQ remapping is in xapic mode
Switched APIC routing to physical flat.
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
smpboot: CPU0: Genuine Intel(R) CPU  @ 2.70GHz (fam: 06, model: 2d, stepping: 05)
TSC deadline timer enabled
Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, Intel PMU driver.
perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode
... version:                3
... bit width:              48
... generic registers:      4
... value mask:             0000ffffffffffff
... max period:             000000007fffffff
... fixed-purpose events:   3
... event mask:             000000070000000f
Brought up 1 CPUs
smpboot: Total of 1 processors activated (5399.99 BogoMIPS)
devtmpfs: initialized
RTC time: 16:20:31, date: 01/08/13
NET: Registered protocol family 16
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
PCI: Using configuration type 1 for base access
PCI: Dell System detected, enabling pci=bfsort.
bio: create slab <bio-0> at 0
ACPI: Added _OSI(Module Device)
ACPI: Added _OSI(Processor Device)
ACPI: Added _OSI(3.0 _SCP Extensions)
ACPI: Added _OSI(Processor Aggregator Device)
ACPI: EC: Look up EC in DSDT
[Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
ACPI: Interpreter enabled
ACPI: (supports S0 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: No dock devices found.
HEST: Table parsing has been initialized.
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3d])
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
pci_root PNP0A08:00: Requesting ACPI _OSC control (0x15)
pci_root PNP0A08:00: ACPI _OSC control (0x15) granted
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [bus 00-3d]
pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
pci_bus 0000:00: root bus resource [io  0x0d00-0x1fff]
pci_bus 0000:00: root bus resource [io  0x8000-0x9fff]
pci_bus 0000:00: root bus resource [io  0xa000-0xbfff]
pci_bus 0000:00: root bus resource [io  0xc000-0xdfff]
pci_bus 0000:00: root bus resource [io  0xe000-0xffff]
pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: root bus resource [mem 0xd4000000-0xdfffffff]
pci_bus 0000:00: root bus resource [mem 0xfed10000-0xfed103ff]
pci_bus 0000:00: root bus resource [mem 0xfed11000-0xfed113ff]
pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff]
pci 0000:00:00.0: [8086:3c00] type 00 class 0x060000
pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: [8086:3c02] type 01 class 0x060400
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:02.0: [8086:3c04] type 01 class 0x060400
pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
pci 0000:00:02.2: [8086:3c06] type 01 class 0x060400
pci 0000:00:02.2: PME# supported from D0 D3hot D3cold
pci 0000:00:03.0: [8086:3c08] type 01 class 0x060400
pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
pci 0000:00:03.2: [8086:3c0a] type 01 class 0x060400
pci 0000:00:03.2: PME# supported from D0 D3hot D3cold
pci 0000:00:05.0: [8086:3c28] type 00 class 0x088000
pci 0000:00:05.2: [8086:3c2a] type 00 class 0x088000
pci 0000:00:11.0: [8086:1d3e] type 01 class 0x060400
pci 0000:00:11.0: PME# supported from D0 D3hot D3cold
pci 0000:00:16.0: [8086:1d3a] type 00 class 0x078000
pci 0000:00:16.0: reg 10: [mem 0xfed10000-0xfed1000f 64bit]
pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
pci 0000:00:16.1: [8086:1d3b] type 00 class 0x078000
pci 0000:00:16.1: reg 10: [mem 0xfed11000-0xfed1100f 64bit]
pci 0000:00:16.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.0: [8086:1d2d] type 00 class 0x0c0320
pci 0000:00:1a.0: reg 10: [mem 0xdc8fd000-0xdc8fd3ff]
pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: [8086:1d10] type 01 class 0x060400
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.7: [8086:1d1e] type 01 class 0x060400
pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.0: [8086:1d26] type 00 class 0x0c0320
pci 0000:00:1d.0: reg 10: [mem 0xdc8fe000-0xdc8fe3ff]
pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
pci 0000:00:1f.0: [8086:1d41] type 00 class 0x060100
pci 0000:00:1f.2: [8086:1d02] type 00 class 0x010601
pci 0000:00:1f.2: reg 10: [io  0xcce8-0xccef]
pci 0000:00:1f.2: reg 14: [io  0xccf8-0xccfb]
pci 0000:00:1f.2: reg 18: [io  0xccf0-0xccf7]
pci 0000:00:1f.2: reg 1c: [io  0xccfc-0xccff]
pci 0000:00:1f.2: reg 20: [io  0xccc0-0xccdf]
pci 0000:00:1f.2: reg 24: [mem 0xdc8ff000-0xdc8ff7ff]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:01:00.0: [8086:1521] type 00 class 0x020000
pci 0000:01:00.0: reg 10: [mem 0xd8b00000-0xd8bfffff]
pci 0000:01:00.0: reg 18: [io  0xfc80-0xfc9f]
pci 0000:01:00.0: reg 1c: [mem 0xd8ff0000-0xd8ff3fff]
pci 0000:01:00.0: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
pci 0000:01:00.1: [8086:1521] type 00 class 0x020000
pci 0000:01:00.1: reg 10: [mem 0xd8c00000-0xd8cfffff]
pci 0000:01:00.1: reg 18: [io  0xfca0-0xfcbf]
pci 0000:01:00.1: reg 1c: [mem 0xd8ff4000-0xd8ff7fff]
pci 0000:01:00.1: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.1: PME# supported from D0 D3hot D3cold
pci 0000:01:00.2: [8086:1521] type 00 class 0x020000
pci 0000:01:00.2: reg 10: [mem 0xd8d00000-0xd8dfffff]
pci 0000:01:00.2: reg 18: [io  0xfcc0-0xfcdf]
pci 0000:01:00.2: reg 1c: [mem 0xd8ff8000-0xd8ffbfff]
pci 0000:01:00.2: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.2: PME# supported from D0 D3hot D3cold
pci 0000:01:00.3: [8086:1521] type 00 class 0x020000
pci 0000:01:00.3: reg 10: [mem 0xd8e00000-0xd8efffff]
pci 0000:01:00.3: reg 18: [io  0xfce0-0xfcff]
pci 0000:01:00.3: reg 1c: [mem 0xd8ffc000-0xd8ffffff]
pci 0000:01:00.3: reg 30: [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.3: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:01.0:   bridge window [io  0xf000-0xffff]
pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xd8ffffff]
pci 0000:00:01.0:   bridge window [mem 0xd5000000-0xd51fffff 64bit pref]
pci 0000:00:02.0: PCI bridge to [bus 03]
pci 0000:00:02.2: PCI bridge to [bus 02]
pci 0000:00:02.2:   bridge window [io  0xe000-0xefff]
pci 0000:00:02.2:   bridge window [mem 0xd9000000-0xd9ffffff]
pci 0000:00:03.0: PCI bridge to [bus 04]
pci 0000:05:00.0: [1000:0064] type 00 class 0x010700
pci 0000:05:00.0: reg 10: [io  0xdc00-0xdcff]
pci 0000:05:00.0: reg 14: [mem 0xdaffc000-0xdaffffff 64bit]
pci 0000:05:00.0: reg 1c: [mem 0xdaf80000-0xdafbffff 64bit]
pci 0000:05:00.0: reg 30: [mem 0xda000000-0xda07ffff pref]
pci 0000:05:00.0: supports D1 D2
pci 0000:00:03.2: PCI bridge to [bus 05]
pci 0000:00:03.2:   bridge window [io  0xd000-0xdfff]
pci 0000:00:03.2:   bridge window [mem 0xda000000-0xdaffffff]
pci 0000:00:11.0: PCI bridge to [bus 06]
pci 0000:00:1c.0: PCI bridge to [bus 07]
pci 0000:08:00.0: [1912:0013] type 01 class 0x060400
pci 0000:08:00.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.7: PCI bridge to [bus 08-0c]
pci 0000:00:1c.7:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:00:1c.7:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:00.0: [1912:0013] type 01 class 0x060400
pci 0000:09:00.0: PME# supported from D0 D3hot D3cold
pci 0000:09:01.0: [1912:0013] type 01 class 0x060400
pci 0000:09:01.0: PME# supported from D0 D3hot D3cold
pci 0000:08:00.0: PCI bridge to [bus 09-0c]
pci 0000:08:00.0:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:08:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:0a:00.0: [1912:0012] type 01 class 0x060400
pci 0000:09:00.0: PCI bridge to [bus 0a-0b]
pci 0000:09:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:09:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:0b:00.0: [102b:0534] type 00 class 0x030000
pci 0000:0b:00.0: reg 10: [mem 0xd4000000-0xd4ffffff pref]
pci 0000:0b:00.0: reg 14: [mem 0xdbffc000-0xdbffffff]
pci 0000:0b:00.0: reg 18: [mem 0xdb000000-0xdb7fffff]
pci 0000:0a:00.0: PCI bridge to [bus 0b]
pci 0000:0a:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:0a:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:01.0: PCI bridge to [bus 0c]
pci 0000:09:01.0:   bridge window [mem 0xdc700000-0xdc7fffff]
pci 0000:00:1e.0: PCI bridge to [bus 0d] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0000-0x03af] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x03e0-0x0cf7] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x03b0-0x03df] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0d00-0x1fff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x8000-0x9fff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0xa000-0xbfff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0xc000-0xdfff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0xe000-0xffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xd4000000-0xdfffffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xfed10000-0xfed103ff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xfed11000-0xfed113ff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0xfed40000-0xfed44fff] (subtractive decode)
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX5._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6._PRT]
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: Invalid Power Resource to register!
ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 40-7e])
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1._PRT]
pci_root PNP0A08:01: Requesting ACPI _OSC control (0x15)
pci_root PNP0A08:01: ACPI _OSC control (0x15) granted
PCI host bridge to bus 0000:40
pci_bus 0000:40: root bus resource [bus 40-7e]
pci_bus 0000:40: root bus resource [io  0x2000-0x3fff]
pci_bus 0000:40: root bus resource [io  0x4000-0x5fff]
pci_bus 0000:40: root bus resource [io  0x6000-0x7fff]
pci_bus 0000:40: root bus resource [mem 0xcc000000-0xd3ffffff]
pci 0000:40:01.0: [8086:3c02] type 01 class 0x060400
pci 0000:40:01.0: PME# supported from D0 D3hot D3cold
pci 0000:40:02.0: [8086:3c04] type 01 class 0x060400
pci 0000:40:02.0: PME# supported from D0 D3hot D3cold
pci 0000:40:03.0: [8086:3c08] type 01 class 0x060400
pci 0000:40:03.0: PME# supported from D0 D3hot D3cold
pci 0000:40:03.2: [8086:3c0a] type 01 class 0x060400
pci 0000:40:03.2: PME# supported from D0 D3hot D3cold
pci 0000:40:05.0: [8086:3c28] type 00 class 0x088000
pci 0000:40:05.2: [8086:3c2a] type 00 class 0x088000
pci 0000:41:00.0: [10b5:8624] type 01 class 0x060400
pci 0000:41:00.0: reg 10: [mem 0xd0ce0000-0xd0cfffff]
pci 0000:41:00.0: PME# supported from D0 D3hot D3cold
pci 0000:40:01.0: PCI bridge to [bus 41-47]
pci 0000:40:01.0:   bridge window [io  0x2000-0x3fff]
pci 0000:40:01.0:   bridge window [mem 0xd0800000-0xd0cfffff]
pci 0000:40:01.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:42:04.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:04.0: PME# supported from D0 D3hot D3cold
pci 0000:42:05.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:05.0: PME# supported from D0 D3hot D3cold
pci 0000:42:06.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:06.0: PME# supported from D0 D3hot D3cold
pci 0000:42:08.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:08.0: PME# supported from D0 D3hot D3cold
pci 0000:42:09.0: [10b5:8624] type 01 class 0x060400
pci 0000:42:09.0: PME# supported from D0 D3hot D3cold
pci 0000:41:00.0: PCI bridge to [bus 42-47]
pci 0000:41:00.0:   bridge window [io  0x2000-0x3fff]
pci 0000:41:00.0:   bridge window [mem 0xd0800000-0xd0bfffff]
pci 0000:41:00.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:42:04.0: PCI bridge to [bus 43]
pci 0000:44:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:44:00.0: reg 10: [mem 0xd08ff000-0xd08fffff 64bit]
pci 0000:44:00.0: supports D1
pci 0000:44:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:05.0: PCI bridge to [bus 44]
pci 0000:42:05.0:   bridge window [io  0x2000-0x2fff]
pci 0000:42:05.0:   bridge window [mem 0xd0800000-0xd08fffff]
pci 0000:42:05.0:   bridge window [mem 0xcc200000-0xcc3fffff 64bit pref]
pci 0000:45:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:45:00.0: reg 10: [mem 0xd09ff000-0xd09fffff 64bit]
pci 0000:45:00.0: supports D1
pci 0000:45:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:06.0: PCI bridge to [bus 45]
pci 0000:42:06.0:   bridge window [mem 0xd0900000-0xd09fffff]
pci 0000:46:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:46:00.0: reg 10: [mem 0xd0aff000-0xd0afffff 64bit]
pci 0000:46:00.0: supports D1
pci 0000:46:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:08.0: PCI bridge to [bus 46]
pci 0000:42:08.0:   bridge window [mem 0xd0a00000-0xd0afffff]
pci 0000:47:00.0: [13a3:0037] type 00 class 0x108000
pci 0000:47:00.0: reg 10: [mem 0xd0bff000-0xd0bfffff 64bit]
pci 0000:47:00.0: supports D1
pci 0000:47:00.0: PME# supported from D0 D1 D3hot
pci 0000:42:09.0: PCI bridge to [bus 47]
pci 0000:42:09.0:   bridge window [io  0x3000-0x3fff]
pci 0000:42:09.0:   bridge window [mem 0xd0b00000-0xd0bfffff]
pci 0000:42:09.0:   bridge window [mem 0xcc400000-0xcc5fffff 64bit pref]
pci 0000:48:00.0: [8086:10fb] type 00 class 0x020000
pci 0000:48:00.0: reg 10: [mem 0xcc080000-0xcc0fffff 64bit pref]
pci 0000:48:00.0: reg 18: [io  0x7cc0-0x7cdf]
pci 0000:48:00.0: reg 20: [mem 0xcc1f8000-0xcc1fbfff 64bit pref]
pci 0000:48:00.0: reg 30: [mem 0xd0000000-0xd007ffff pref]
pci 0000:48:00.0: PME# supported from D0 D3hot
pci 0000:48:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.1: [8086:10fb] type 00 class 0x020000
pci 0000:48:00.1: reg 10: [mem 0xcc100000-0xcc17ffff 64bit pref]
pci 0000:48:00.1: reg 18: [io  0x7ce0-0x7cff]
pci 0000:48:00.1: reg 20: [mem 0xcc1fc000-0xcc1fffff 64bit pref]
pci 0000:48:00.1: reg 30: [mem 0xd0000000-0xd007ffff pref]
pci 0000:48:00.1: PME# supported from D0 D3hot
pci 0000:48:00.1: reg 184: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.1: reg 190: [mem 0x00000000-0x00003fff 64bit]
pci 0000:40:02.0: PCI bridge to [bus 48]
pci 0000:40:02.0:   bridge window [io  0x7000-0x7fff]
pci 0000:40:02.0:   bridge window [mem 0xd0000000-0xd07fffff]
pci 0000:40:02.0:   bridge window [mem 0xcc000000-0xcc1fffff 64bit pref]
pci 0000:40:03.0: PCI bridge to [bus 49]
pci 0000:40:03.2: PCI bridge to [bus 4a]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXB._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXC._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXD._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXE._PRT]
ACPI: Invalid Power Resource to register!
ACPI: PCI Root Bridge [P0B1] (domain 0000 [bus 3f])
pci_root PNP0A08:02: ACPI _OSC support notification failed, disabling PCIe ASPM
pci_root PNP0A08:02: Unable to request _OSC control (_OSC support mask: 0x08)
PCI host bridge to bus 0000:3f
pci_bus 0000:3f: root bus resource [bus 3f]
pci 0000:3f:08.0: [8086:3c80] type 00 class 0x088000
pci 0000:3f:09.0: [8086:3c90] type 00 class 0x088000
pci 0000:3f:0a.0: [8086:3cc0] type 00 class 0x088000
pci 0000:3f:0a.1: [8086:3cc1] type 00 class 0x088000
pci 0000:3f:0a.2: [8086:3cc2] type 00 class 0x088000
pci 0000:3f:0a.3: [8086:3cd0] type 00 class 0x088000
pci 0000:3f:0b.0: [8086:3ce0] type 00 class 0x088000
pci 0000:3f:0b.3: [8086:3ce3] type 00 class 0x088000
pci 0000:3f:0c.0: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.1: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.2: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.3: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0c.6: [8086:3cf4] type 00 class 0x088000
pci 0000:3f:0c.7: [8086:3cf6] type 00 class 0x088000
pci 0000:3f:0d.0: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.1: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.2: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.3: [8086:3ce8] type 00 class 0x088000
pci 0000:3f:0d.6: [8086:3cf5] type 00 class 0x088000
pci 0000:3f:0e.0: [8086:3ca0] type 00 class 0x088000
pci 0000:3f:0e.1: [8086:3c46] type 00 class 0x110100
pci 0000:3f:0f.0: [8086:3ca8] type 00 class 0x088000
pci 0000:3f:0f.1: [8086:3c71] type 00 class 0x088000
pci 0000:3f:0f.2: [8086:3caa] type 00 class 0x088000
pci 0000:3f:0f.3: [8086:3cab] type 00 class 0x088000
pci 0000:3f:0f.4: [8086:3cac] type 00 class 0x088000
pci 0000:3f:0f.5: [8086:3cad] type 00 class 0x088000
pci 0000:3f:0f.6: [8086:3cae] type 00 class 0x088000
pci 0000:3f:10.0: [8086:3cb0] type 00 class 0x088000
pci 0000:3f:10.1: [8086:3cb1] type 00 class 0x088000
pci 0000:3f:10.2: [8086:3cb2] type 00 class 0x088000
pci 0000:3f:10.3: [8086:3cb3] type 00 class 0x088000
pci 0000:3f:10.4: [8086:3cb4] type 00 class 0x088000
pci 0000:3f:10.5: [8086:3cb5] type 00 class 0x088000
pci 0000:3f:10.6: [8086:3cb6] type 00 class 0x088000
pci 0000:3f:10.7: [8086:3cb7] type 00 class 0x088000
pci 0000:3f:11.0: [8086:3cb8] type 00 class 0x088000
pci 0000:3f:13.0: [8086:3ce4] type 00 class 0x088000
pci 0000:3f:13.1: [8086:3c43] type 00 class 0x110100
pci 0000:3f:13.4: [8086:3ce6] type 00 class 0x110100
pci 0000:3f:13.5: [8086:3c44] type 00 class 0x110100
pci 0000:3f:13.6: [8086:3c45] type 00 class 0x088000
ACPI: Invalid Power Resource to register!
ACPI _OSC control for PCIe not granted, disabling ASPM
ACPI: PCI Interrupt Link [LK00] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK01] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK02] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK03] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK04] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK05] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK06] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LK07] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
vgaarb: device added: PCI:0000:0b:00.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
vgaarb: bridge control possible 0000:0b:00.0
SCSI subsystem initialized
ACPI: bus type scsi registered
libata version 3.00 loaded.
PCI: Using ACPI for IRQ routing
PCI: Discovered peer bus 7f
PCI: root bus 7f: using default resources
PCI: Probing PCI hardware (bus 7f)
PCI host bridge to bus 0000:7f
pci_bus 0000:7f: root bus resource [io  0x0000-0xffff]
pci_bus 0000:7f: root bus resource [mem 0x00000000-0x3fffffffffff]
pci_bus 0000:7f: No busn resource found for root bus, will use [bus 7f-ff]
pci 0000:7f:08.0: [8086:3c80] type 00 class 0x088000
pci 0000:7f:09.0: [8086:3c90] type 00 class 0x088000
pci 0000:7f:0a.0: [8086:3cc0] type 00 class 0x088000
pci 0000:7f:0a.1: [8086:3cc1] type 00 class 0x088000
pci 0000:7f:0a.2: [8086:3cc2] type 00 class 0x088000
pci 0000:7f:0a.3: [8086:3cd0] type 00 class 0x088000
pci 0000:7f:0b.0: [8086:3ce0] type 00 class 0x088000
pci 0000:7f:0b.3: [8086:3ce3] type 00 class 0x088000
pci 0000:7f:0c.0: [8086:3ce8] type 00 class 0x088000
pci 0000:7f:0c.1: [8086:3ce8] type 00 class 0x088000
pci 0000:7f:0c.2: [8086:3ce8] type 00 class 0x088000
pci 0000:7f:0c.3: [8086:3ce8] type 00 class 0x088000
pci 0000:7f:0c.6: [8086:3cf4] type 00 class 0x088000
pci 0000:7f:0c.7: [8086:3cf6] type 00 class 0x088000
pci 0000:7f:0d.0: [8086:3ce8] type 00 class 0x088000
pci 0000:7f:0d.1: [8086:3ce8] type 00 class 0x088000
pci 0000:7f:0d.2: [8086:3ce8] type 00 class 0x088000
pci 0000:7f:0d.3: [8086:3ce8] type 00 class 0x088000
pci 0000:7f:0d.6: [8086:3cf5] type 00 class 0x088000
pci 0000:7f:0e.0: [8086:3ca0] type 00 class 0x088000
pci 0000:7f:0e.1: [8086:3c46] type 00 class 0x110100
pci 0000:7f:0f.0: [8086:3ca8] type 00 class 0x088000
pci 0000:7f:0f.1: [8086:3c71] type 00 class 0x088000
pci 0000:7f:0f.2: [8086:3caa] type 00 class 0x088000
pci 0000:7f:0f.3: [8086:3cab] type 00 class 0x088000
pci 0000:7f:0f.4: [8086:3cac] type 00 class 0x088000
pci 0000:7f:0f.5: [8086:3cad] type 00 class 0x088000
pci 0000:7f:0f.6: [8086:3cae] type 00 class 0x088000
pci 0000:7f:10.0: [8086:3cb0] type 00 class 0x088000
pci 0000:7f:10.1: [8086:3cb1] type 00 class 0x088000
pci 0000:7f:10.2: [8086:3cb2] type 00 class 0x088000
pci 0000:7f:10.3: [8086:3cb3] type 00 class 0x088000
pci 0000:7f:10.4: [8086:3cb4] type 00 class 0x088000
pci 0000:7f:10.5: [8086:3cb5] type 00 class 0x088000
pci 0000:7f:10.6: [8086:3cb6] type 00 class 0x088000
pci 0000:7f:10.7: [8086:3cb7] type 00 class 0x088000
pci 0000:7f:11.0: [8086:3cb8] type 00 class 0x088000
pci 0000:7f:13.0: [8086:3ce4] type 00 class 0x088000
pci 0000:7f:13.1: [8086:3c43] type 00 class 0x110100
pci 0000:7f:13.4: [8086:3ce6] type 00 class 0x110100
pci 0000:7f:13.5: [8086:3c44] type 00 class 0x110100
pci 0000:7f:13.6: [8086:3c45] type 00 class 0x088000
pci_bus 0000:7f: busn_res: [bus 7f-ff] end is updated to 7f
PCI: pci_cache_line_size set to 64 bytes
e820: reserve RAM buffer [mem 0x1effb000-0x1fffffff]
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Switching to clocksource hpet
AppArmor: AppArmor Filesystem Enabled
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:00: [dma 4]
pnp 00:00: Plug and Play ACPI device, IDs PNP0200 (active)
pnp 00:01: Plug and Play ACPI device, IDs PNP0c04 (active)
system 00:02: Plug and Play ACPI device, IDs PNP0c01 (active)
pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)
pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active)
system 00:06: [io  0x0800-0x087f] has been reserved
system 00:06: [io  0x0880-0x08ff] has been reserved
system 00:06: [io  0x0900-0x091f] has been reserved
system 00:06: [io  0x0920-0x0923] has been reserved
system 00:06: [io  0x0924] has been reserved
system 00:06: [io  0x0370-0x0377] has been reserved
system 00:06: [io  0x0ca0-0x0ca7] has been reserved
system 00:06: [io  0x0ca9-0x0cab] has been reserved
system 00:06: [io  0x0cad-0x0caf] has been reserved
system 00:06: [io  0x0cb0-0x0cbf] has been reserved
system 00:06: Plug and Play ACPI device, IDs PNP0c01 (active)
system 00:07: [io  0x0ca8] has been reserved
system 00:07: [io  0x0cac] has been reserved
system 00:07: Plug and Play ACPI device, IDs IPI0001 PNP0c01 (active)
system 00:08: [mem 0xe0000000-0xe3efffff] has been reserved
system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:09: [mem 0xe4000000-0xe7ffffff] has been reserved
system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:0a: [mem 0xe3f00000-0xe3ffffff] has been reserved
system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:0b: [mem 0xdc900000-0xdc901fff] could not be reserved
system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:0c: [mem 0xd0d00000-0xd0d01fff] could not be reserved
system 00:0c: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
pci 0000:01:00.1: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:00.0 [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.2: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:00.0 [mem 0xd8000000-0xd807ffff pref]
pci 0000:01:00.3: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:00.0 [mem 0xd8000000-0xd807ffff pref]
pci 0000:48:00.1: address space collision: [mem 0xd0000000-0xd007ffff pref] conflicts with 0000:48:00.0 [mem 0xd0000000-0xd007ffff pref]
pci 0000:01:00.1: BAR 6: assigned [mem 0xd5000000-0xd507ffff pref]
pci 0000:01:00.2: BAR 6: assigned [mem 0xd5080000-0xd50fffff pref]
pci 0000:01:00.3: BAR 6: assigned [mem 0xd5100000-0xd517ffff pref]
pci 0000:00:01.0: PCI bridge to [bus 01]
pci 0000:00:01.0:   bridge window [io  0xf000-0xffff]
pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xd8ffffff]
pci 0000:00:01.0:   bridge window [mem 0xd5000000-0xd51fffff 64bit pref]
pci 0000:00:02.0: PCI bridge to [bus 03]
pci 0000:00:02.2: PCI bridge to [bus 02]
pci 0000:00:02.2:   bridge window [io  0xe000-0xefff]
pci 0000:00:02.2:   bridge window [mem 0xd9000000-0xd9ffffff]
pci 0000:00:03.0: PCI bridge to [bus 04]
pci 0000:00:03.2: PCI bridge to [bus 05]
pci 0000:00:03.2:   bridge window [io  0xd000-0xdfff]
pci 0000:00:03.2:   bridge window [mem 0xda000000-0xdaffffff]
pci 0000:00:11.0: PCI bridge to [bus 06]
pci 0000:00:1c.0: PCI bridge to [bus 07]
pci 0000:0a:00.0: PCI bridge to [bus 0b]
pci 0000:0a:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:0a:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:00.0: PCI bridge to [bus 0a-0b]
pci 0000:09:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
pci 0000:09:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:09:01.0: PCI bridge to [bus 0c]
pci 0000:09:01.0:   bridge window [mem 0xdc700000-0xdc7fffff]
pci 0000:08:00.0: PCI bridge to [bus 09-0c]
pci 0000:08:00.0:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:08:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:00:1c.7: PCI bridge to [bus 08-0c]
pci 0000:00:1c.7:   bridge window [mem 0xdb000000-0xdc7fffff]
pci 0000:00:1c.7:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 0d]
pci 0000:42:04.0: PCI bridge to [bus 43]
pci 0000:42:05.0: PCI bridge to [bus 44]
pci 0000:42:05.0:   bridge window [io  0x2000-0x2fff]
pci 0000:42:05.0:   bridge window [mem 0xd0800000-0xd08fffff]
pci 0000:42:05.0:   bridge window [mem 0xcc200000-0xcc3fffff 64bit pref]
pci 0000:42:06.0: PCI bridge to [bus 45]
pci 0000:42:06.0:   bridge window [mem 0xd0900000-0xd09fffff]
pci 0000:42:08.0: PCI bridge to [bus 46]
pci 0000:42:08.0:   bridge window [mem 0xd0a00000-0xd0afffff]
pci 0000:42:09.0: PCI bridge to [bus 47]
pci 0000:42:09.0:   bridge window [io  0x3000-0x3fff]
pci 0000:42:09.0:   bridge window [mem 0xd0b00000-0xd0bfffff]
pci 0000:42:09.0:   bridge window [mem 0xcc400000-0xcc5fffff 64bit pref]
pci 0000:41:00.0: PCI bridge to [bus 42-47]
pci 0000:41:00.0:   bridge window [io  0x2000-0x3fff]
pci 0000:41:00.0:   bridge window [mem 0xd0800000-0xd0bfffff]
pci 0000:41:00.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:40:01.0: PCI bridge to [bus 41-47]
pci 0000:40:01.0:   bridge window [io  0x2000-0x3fff]
pci 0000:40:01.0:   bridge window [mem 0xd0800000-0xd0cfffff]
pci 0000:40:01.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
pci 0000:48:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.1: reg 184: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.1: reg 190: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.1: reg 184: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.1: BAR 6: assigned [mem 0xcc000000-0xcc07ffff pref]
pci 0000:48:00.0: reg 184: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.0: BAR 7: assigned [mem 0xd0080000-0xd017ffff 64bit]
pci 0000:48:00.0: reg 190: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.0: BAR 10: assigned [mem 0xd0180000-0xd027ffff 64bit]
pci 0000:48:00.1: reg 184: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.1: BAR 7: assigned [mem 0xd0280000-0xd037ffff 64bit]
pci 0000:48:00.1: reg 190: [mem 0x00000000-0x00003fff 64bit]
pci 0000:48:00.1: BAR 10: assigned [mem 0xd0380000-0xd047ffff 64bit]
pci 0000:40:02.0: PCI bridge to [bus 48]
pci 0000:40:02.0:   bridge window [io  0x7000-0x7fff]
pci 0000:40:02.0:   bridge window [mem 0xd0000000-0xd07fffff]
pci 0000:40:02.0:   bridge window [mem 0xcc000000-0xcc1fffff 64bit pref]
pci 0000:40:03.0: PCI bridge to [bus 49]
pci 0000:40:03.2: PCI bridge to [bus 4a]
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
pci_bus 0000:00: resource 7 [io  0x0d00-0x1fff]
pci_bus 0000:00: resource 8 [io  0x8000-0x9fff]
pci_bus 0000:00: resource 9 [io  0xa000-0xbfff]
pci_bus 0000:00: resource 10 [io  0xc000-0xdfff]
pci_bus 0000:00: resource 11 [io  0xe000-0xffff]
pci_bus 0000:00: resource 12 [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: resource 13 [mem 0xd4000000-0xdfffffff]
pci_bus 0000:00: resource 14 [mem 0xfed10000-0xfed103ff]
pci_bus 0000:00: resource 15 [mem 0xfed11000-0xfed113ff]
pci_bus 0000:00: resource 16 [mem 0xfed40000-0xfed44fff]
pci_bus 0000:01: resource 0 [io  0xf000-0xffff]
pci_bus 0000:01: resource 1 [mem 0xd8000000-0xd8ffffff]
pci_bus 0000:01: resource 2 [mem 0xd5000000-0xd51fffff 64bit pref]
pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
pci_bus 0000:02: resource 1 [mem 0xd9000000-0xd9ffffff]
pci_bus 0000:05: resource 0 [io  0xd000-0xdfff]
pci_bus 0000:05: resource 1 [mem 0xda000000-0xdaffffff]
pci_bus 0000:08: resource 1 [mem 0xdb000000-0xdc7fffff]
pci_bus 0000:08: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:09: resource 1 [mem 0xdb000000-0xdc7fffff]
pci_bus 0000:09: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:0a: resource 1 [mem 0xdb000000-0xdbffffff]
pci_bus 0000:0a: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:0b: resource 1 [mem 0xdb000000-0xdbffffff]
pci_bus 0000:0b: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
pci_bus 0000:0c: resource 1 [mem 0xdc700000-0xdc7fffff]
pci_bus 0000:0d: resource 4 [io  0x0000-0x03af]
pci_bus 0000:0d: resource 5 [io  0x03e0-0x0cf7]
pci_bus 0000:0d: resource 6 [io  0x03b0-0x03df]
pci_bus 0000:0d: resource 7 [io  0x0d00-0x1fff]
pci_bus 0000:0d: resource 8 [io  0x8000-0x9fff]
pci_bus 0000:0d: resource 9 [io  0xa000-0xbfff]
pci_bus 0000:0d: resource 10 [io  0xc000-0xdfff]
pci_bus 0000:0d: resource 11 [io  0xe000-0xffff]
pci_bus 0000:0d: resource 12 [mem 0x000a0000-0x000bffff]
pci_bus 0000:0d: resource 13 [mem 0xd4000000-0xdfffffff]
pci_bus 0000:0d: resource 14 [mem 0xfed10000-0xfed103ff]
pci_bus 0000:0d: resource 15 [mem 0xfed11000-0xfed113ff]
pci_bus 0000:0d: resource 16 [mem 0xfed40000-0xfed44fff]
pci_bus 0000:40: resource 4 [io  0x2000-0x3fff]
pci_bus 0000:40: resource 5 [io  0x4000-0x5fff]
pci_bus 0000:40: resource 6 [io  0x6000-0x7fff]
pci_bus 0000:40: resource 7 [mem 0xcc000000-0xd3ffffff]
pci_bus 0000:41: resource 0 [io  0x2000-0x3fff]
pci_bus 0000:41: resource 1 [mem 0xd0800000-0xd0cfffff]
pci_bus 0000:41: resource 2 [mem 0xcc200000-0xcc5fffff 64bit pref]
pci_bus 0000:42: resource 0 [io  0x2000-0x3fff]
pci_bus 0000:42: resource 1 [mem 0xd0800000-0xd0bfffff]
pci_bus 0000:42: resource 2 [mem 0xcc200000-0xcc5fffff 64bit pref]
pci_bus 0000:44: resource 0 [io  0x2000-0x2fff]
pci_bus 0000:44: resource 1 [mem 0xd0800000-0xd08fffff]
pci_bus 0000:44: resource 2 [mem 0xcc200000-0xcc3fffff 64bit pref]
pci_bus 0000:45: resource 1 [mem 0xd0900000-0xd09fffff]
pci_bus 0000:46: resource 1 [mem 0xd0a00000-0xd0afffff]
pci_bus 0000:47: resource 0 [io  0x3000-0x3fff]
pci_bus 0000:47: resource 1 [mem 0xd0b00000-0xd0bfffff]
pci_bus 0000:47: resource 2 [mem 0xcc400000-0xcc5fffff 64bit pref]
pci_bus 0000:48: resource 0 [io  0x7000-0x7fff]
pci_bus 0000:48: resource 1 [mem 0xd0000000-0xd07fffff]
pci_bus 0000:48: resource 2 [mem 0xcc000000-0xcc1fffff 64bit pref]
pci_bus 0000:7f: resource 4 [io  0x0000-0xffff]
pci_bus 0000:7f: resource 5 [mem 0x00000000-0x3fffffffffff]
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 4, 65536 bytes)
TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
pci 0000:0b:00.0: Boot video device
PCI: CLS 64 bytes, default 64
Unpacking initramfs...
Freeing initrd memory: 5824k freed
audit: initializing netlink socket (disabled)
type=2000 audit(1357662032.152:1): initialized
HugeTLB registered 2 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 709
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler deadline registered (default)
io scheduler cfq registered
pcieport 0000:00:01.0: irq 106 for MSI/MSI-X
pcieport 0000:00:02.0: irq 107 for MSI/MSI-X
pcieport 0000:00:02.2: irq 108 for MSI/MSI-X
pcieport 0000:00:03.0: irq 109 for MSI/MSI-X
pcieport 0000:00:03.2: irq 110 for MSI/MSI-X
pcieport 0000:00:11.0: irq 111 for MSI/MSI-X
pcieport 0000:00:1c.0: irq 112 for MSI/MSI-X
pcieport 0000:00:1c.7: irq 113 for MSI/MSI-X
pcieport 0000:40:01.0: irq 114 for MSI/MSI-X
pcieport 0000:40:02.0: irq 115 for MSI/MSI-X
pcieport 0000:40:03.0: irq 116 for MSI/MSI-X
pcieport 0000:40:03.2: irq 117 for MSI/MSI-X
pcieport 0000:41:00.0: irq 118 for MSI/MSI-X
pcieport 0000:42:04.0: irq 119 for MSI/MSI-X
pcieport 0000:42:05.0: irq 120 for MSI/MSI-X
pcieport 0000:42:06.0: irq 121 for MSI/MSI-X
pcieport 0000:42:08.0: irq 122 for MSI/MSI-X
pcieport 0000:42:09.0: irq 123 for MSI/MSI-X
pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
pci 0000:01:00.2: Signaling PME through PCIe PME interrupt
pci 0000:01:00.3: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:02.2: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:02.2:pcie01: service driver pcie_pme loaded
pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:03.2: Signaling PME through PCIe PME interrupt
pci 0000:05:00.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:03.2:pcie01: service driver pcie_pme loaded
pcieport 0000:00:11.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:11.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
pcieport 0000:08:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:09:00.0: Signaling PME through PCIe PME interrupt
pci 0000:0a:00.0: Signaling PME through PCIe PME interrupt
pci 0000:0b:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:09:01.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
pcieport 0000:40:01.0: Signaling PME through PCIe PME interrupt
pcieport 0000:41:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:04.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:05.0: Signaling PME through PCIe PME interrupt
pci 0000:44:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:06.0: Signaling PME through PCIe PME interrupt
pci 0000:45:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:08.0: Signaling PME through PCIe PME interrupt
pci 0000:46:00.0: Signaling PME through PCIe PME interrupt
pcieport 0000:42:09.0: Signaling PME through PCIe PME interrupt
pci 0000:47:00.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:01.0:pcie01: service driver pcie_pme loaded
pcieport 0000:40:02.0: Signaling PME through PCIe PME interrupt
pci 0000:48:00.0: Signaling PME through PCIe PME interrupt
pci 0000:48:00.1: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:02.0:pcie01: service driver pcie_pme loaded
pcieport 0000:40:03.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:03.0:pcie01: service driver pcie_pme loaded
pcieport 0000:40:03.2: Signaling PME through PCIe PME interrupt
pcie_pme 0000:40:03.2:pcie01: service driver pcie_pme loaded
intel_idle: MWAIT substates: 0x21120
intel_idle: v0.4 model 0x2D
intel_idle: lapic_timer_reliable_states 0xffffffff
ERST: Error Record Serialization Table (ERST) support is initialized.
GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
00:04: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Non-volatile memory driver v1.3
Linux agpgart interface v0.103
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: irq 124 for MSI/MSI-X
ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ems apst 
ahci 0000:00:1f.2: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff100 irq 124
ata2: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff180 irq 124
ata3: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff200 irq 124
ata4: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff280 irq 124
ata5: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff300 irq 124
ata6: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff380 irq 124
libphy: Fixed MDIO Bus: probed
i8042: PNP: No PS/2 controller found. Probing ports directly.
i8042: No controller found
tsc: Refined TSC clocksource calibration: 2699.999 MHz
Switching to clocksource tsc
mousedev: PS/2 mouse device common for all mice
rtc_cmos 00:03: RTC can wake from S4
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one day, y3k, 242 bytes nvram, hpet irqs
cpuidle: using governor ladder
cpuidle: using governor menu
ledtrig-cpu: registered to indicate activity on CPUs
EFI Variables Facility v0.08 2004-May-17
TCP: cubic registered
NET: Registered protocol family 10
Key type dns_resolver registered
PM: Checking hibernation image partition /dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-part8
ata3: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
ata6: SATA link down (SStatus 0 SControl 300)
ata1: SATA link down (SStatus 0 SControl 300)
ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
ata5.00: ATAPI: TEAC DVD-ROM DV-28SW, R.2A, max UDMA/100
ata5.00: configured for UDMA/100
scsi 4:0:0:0: CD-ROM            TEAC     DVD-ROM DV-28SW  R.2A PQ: 0 ANSI: 5
PM: Hibernation image not present or could not be loaded.
registered taskstats version 1
  Magic number: 13:536:337
tty tty58: hash matches
rtc_cmos 00:03: setting system clock to 2013-01-08 16:20:37 UTC (1357662037)
Freeing unused kernel memory: 1000k freed
Write protecting the kernel read-only data: 10240k
Freeing unused kernel memory: 300k freed
Freeing unused kernel memory: 1500k freed
doing fast boot
SysRq : Changing Loglevel
Loglevel set to 7
megasas: 06.504.01.00-rc1 Mon. Oct. 1 17:00:00 PDT 2012
FATAL: Module ahci not found.
teradata-kdump: Skipping mpt2sas
BIOS EDD facility v0.16 2004-Jun-25, 2 devices found
FATAL: Module jbd not found.
FATAL: Module ext3 not found.
preping 03-storage.sh
running 03-storage.sh
preping 04-udev.sh
udevd (186): /proc/186/oom_adj is deprecated, please use /proc/186/oom_score_adj instead.

running 04-udev.sh
Creating device nodes with udevd version 128 started
udev
preping 05-blogd.sh
running 05-blogd.sh
mount: devpts already mounted or /dev/pts busy
mount: according to mtab, devpts is already mounted on /dev/pts

Boot logging started on /dev/ttyS0(/dev/console) at Tue Jan  8 11:20:38 2013

preping 05-clock.sh

running 05-clock.sh

preping 11-block.sh

running 11-block.sh

preping 11-usb.sh

running 11-usb.sh

preping 21-devinit_done.sh

running 21-devinit_done.sh

preping 81-mount.sh

running 81-mount.sh

Waiting for device /dev/disk/by-label/ROOT-BE2 to appear: ...-- 101:inferno -- time-stamp -- 2013-01-08 17:22:39 --

Re: [PATCH] Only reset e820 once, even with multiple memmap=exactmap params

[Yinghai Lu]

On Tue, Jan 8, 2013 at 8:47 AM, Thomas Renninger <trenn@suse.de> wrote:
> On Tuesday, January 08, 2013 04:04:56 AM Yinghai Lu wrote:
>> On Mon, Jan 7, 2013 at 4:42 PM, Thomas Renninger <trenn@suse.de> wrote:
>> > memmap=256M$3584M
>>
>> may need to change to:
>>
>> memmap=256M\$\$3584M
> The problem is (beside the special char $) that
> memmap=exactmap boot param resets all e820 maps every time the
> parameter is processed.
> And:
> /sbin/kexec -p xy --append="..." --initrd yx
> seem to magically add (append):
> memmap=exactmap memmap=640K@0K memmap=392556K@115328K elfcorehdr=507884K memmap=252K#3099760K
>
> therefore all memmap= I try to pass are voided out by:
> memmap=exactmap
> which is always added by kexec after my params.
>
> I could come around with attached patch and passing:
> /sbin/kexec -p xy --append='... memmap=exactmap memmap=256M$3584M' --initrd yx
>
> Now mmconfig is working in kdump kernel.
> This would mean mmconfig is broken by design in kexec?
>
> Only way to fix this I can think of is to export
> mmconfig area through /sys  (../kernel/debug/mmconfig?, possibly
> already in X$Y format?) in the productive kernel and make kexec add it
> like the other memmap= params automatically.
>
> I'll attach the output in a separate mail.
>
>    Thomas
>
> ---
>
> x86 e820: Do not reset e820 map twice, even if memmap=exactmap is passed as boot param several times
>
> This is needed to be able to explicitly pass (debug) e820
> modifications through kexec via memmap=.
> Otherwise those get voided by kexec appending memmap=exactmap always
> after the user defined boot parameters.
>
> Signed-off-by: Thomas Renninger <trenn@suse.de>
>
>  linux-2.6_t/arch/x86/kernel/e820.c |    4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> Index: git/linux-2.6_t/arch/x86/kernel/e820.c
> ===================================================================
> --- git.orig/linux-2.6_t/arch/x86/kernel/e820.c
> +++ git/linux-2.6_t/arch/x86/kernel/e820.c
> @@ -845,7 +845,9 @@ static int __init parse_memmap_opt(char
>
>         if (!strncmp(p, "exactmap", 8)) {
>  #ifdef CONFIG_CRASH_DUMP
> -               /*
> +               /* memmap=exactmap passed twice, do not reset tables again */
> +               if (saved_max_pfn)
> +                       return 0;               /*
>                  * If we are doing a crash dump, we still need to know
>                  * the real mem size before original memory map is
>                  * reset.

that exactmap logic still have problem:
We need to check exactmap at first, aka need to scan the whole comand line to
see if exactmap is there at first and reset e820 tables then handle
other memmap opt.

Also please update your patch after

tip/x86/mm2

I have one patch that process memmap= with "," there.

http://git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=commitdiff;h=9710f581bb4c35589ac046b0cfc0deb7f369fc85

We could put exactmap scanning in new parse_memmap_opt.

Thanks

Yinghai

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Yinghai Lu]

On Tue, Jan 8, 2013 at 8:50 AM, Thomas Renninger <trenn@suse.de> wrote:
> megaraid_sas

can you check if your initrd for kdump kernel has that driver and
module that it depends on like
scsi sas transport etc ?

Thanks

Yinghai

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Thomas Renninger]

On Tuesday, January 08, 2013 09:27:55 AM Yinghai Lu wrote:
> On Tue, Jan 8, 2013 at 8:50 AM, Thomas Renninger <trenn@suse.de> wrote:
> > megaraid_sas
> 
> can you check if your initrd for kdump kernel has that driver and
> module that it depends on like
> scsi sas transport etc ?

Removing the 5 patches and the disk works and the
dump is written.

I can look a bit further at the memmap=exactmap issue tomorrow.
I can also double check above then, but I am rather sure about it
already:
I tried plain vanilla -> worked, dumping started
I tried with only these 5 patches added -> no disk.


Some questions:

You try to initialize the PCI subsystem in a way the BIOS typically has
to do it in kexec case?

Reacting and trying to handle error condtitions more gracefully
at the place where they are caught could be another approach which
imo makes sense to implement in parallel.

In my case for example I see:
"Present field in the IRTE entry is clear"
DMAR errors. I expect this comes from a device which still throws
interrupts, but irq vector got not set-up or registered in the kexec'ed 
kernel.

I could imagine this is the same error which happens when an irq is
wrongly configured and spurious interrupts happen (but in irq remapped case).
In my case it's not sever as I only see this message once, but according
to another report, they see about 80 of such DMAR error messages per
second. This seem to result in endless DMAR error interrupts and finally
a dead system.

I wonder whether the DMAR error handler could already invoke a PCIe
reset.
I found:
int pci_set_pcie_reset_state(struct pci_dev *dev, enum pcie_reset_state state)
which unfortunatly is only implemented for PPC, but would it make sense to
implement this one and trigger function level reset if several specific DMAR
errors are seen (or other PCI(e) error handlers get active?)?

If this does not help the next step could be to stop DMAR error interrupt
handling or other iommu commands to keep the machine alive, even if one
device keeps firing interrupts to an unconfigured irq vector (or whatever other
things could happen).

Just some ideas...
Comments appreciated.

   Thomas

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Takao Indoh]

Hi Thomas,

(2013/01/09 11:32), Thomas Renninger wrote:
> On Tuesday, January 08, 2013 09:27:55 AM Yinghai Lu wrote:
>> On Tue, Jan 8, 2013 at 8:50 AM, Thomas Renninger <trenn@suse.de> wrote:
>>> megaraid_sas
>>
>> can you check if your initrd for kdump kernel has that driver and
>> module that it depends on like
>> scsi sas transport etc ?
>
> Removing the 5 patches and the disk works and the
> dump is written.
>
> I can look a bit further at the memmap=exactmap issue tomorrow.
> I can also double check above then, but I am rather sure about it
> already:
> I tried plain vanilla -> worked, dumping started

It seems that there are several disk controllers in your system.

00:1f.2 SATA controller [0106]: Intel Corporation Device [8086:1d02] (rev 05)
02:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic Device [1000:005b] (rev 01)
05:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] [1000:0064] (rev 02)

Which disk are you using to save the vmcore?


> I tried with only these 5 patches added -> no disk.
>
>
> Some questions:
>
> You try to initialize the PCI subsystem in a way the BIOS typically has
> to do it in kexec case?

These patches sends hot reset to endpoints to reset them, it may be
different way from BIOS initialization.

> Reacting and trying to handle error condtitions more gracefully
> at the place where they are caught could be another approach which
> imo makes sense to implement in parallel.
>
> In my case for example I see:
> "Present field in the IRTE entry is clear"
> DMAR errors. I expect this comes from a device which still throws
> interrupts, but irq vector got not set-up or registered in the kexec'ed
> kernel.
>
> I could imagine this is the same error which happens when an irq is
> wrongly configured and spurious interrupts happen (but in irq remapped case).
> In my case it's not sever as I only see this message once, but according
> to another report, they see about 80 of such DMAR error messages per
> second. This seem to result in endless DMAR error interrupts and finally
> a dead system.
>
> I wonder whether the DMAR error handler could already invoke a PCIe
> reset.
> I found:
> int pci_set_pcie_reset_state(struct pci_dev *dev, enum pcie_reset_state state)
> which unfortunatly is only implemented for PPC, but would it make sense to
> implement this one and trigger function level reset if several specific DMAR
> errors are seen (or other PCI(e) error handlers get active?)?

Or AER framework may be able to handle this. Actually it has a function
to reset endpoint when error is detected.

Thanks,
Takao Indoh

>
> If this does not help the next step could be to stop DMAR error interrupt
> handling or other iommu commands to keep the machine alive, even if one
> device keeps firing interrupts to an unconfigured irq vector (or whatever other
> things could happen).
>
> Just some ideas...
> Comments appreciated.
>
>     Thomas
>
>

Re: [PATCH] Only reset e820 once, even with multiple memmap=exactmap params

[Thomas Renninger]

On Tuesday, January 08, 2013 09:19:18 AM Yinghai Lu wrote:
...
> 
> that exactmap logic still have problem:
> We need to check exactmap at first, aka need to scan the whole comand line
> to see if exactmap is there at first and reset e820 tables then handle
> other memmap opt.
> 
> Also please update your patch after
> 
> tip/x86/mm2
> 
> I have one patch that process memmap= with "," there.
> 
> http://git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=commitdiff;h=9710f58
> 1bb4c35589ac046b0cfc0deb7f369fc85
> 
> We could put exactmap scanning in new parse_memmap_opt.

I still do not understand why:

Kexec (kexec/firmware_memmap.c) is setting up the e820 map from:
/sys/firmware/memmap/*
and pass it via bootloader structures.
And this e820 table gets immediately voided by memmap=exactmap
and a new one passed via boot parameters is set up.
If I read this correctly, this is what happens?

Can kexec simply pass the memory to use via memmap=X@Y
Then take the original e820 table, but not the usable entries (those
are coming from above memmap=X@Y).
That would mean that the kexec kernel takes all the
original ACPI, ACPI NVS, reserved, unusable (everthing but usable) entries
from the original e820 table and identifies the usable memory from
memmap boot param?

This would be much smarter than trying to pass the mmconf reserved
area and I could imagine other issues will show up if the reserved areas
do not match the original ones in the kexec kernel.

If this really can be done and memmap=exactmap was only used by kexec,
it's logic could be redefined from "drop all e820 entries" to
"drop all usable e820 entries" and no further adjustings in kexec/kernel are
needed to get mmconf working (and other issues may be avoided before
they happen). Beside that ACPI reserved aread is not needed anymore to get
passed via memmap=X#Y by kexec.

   Thomas

Re: [PATCH] Only reset e820 once, even with multiple memmap=exactmap params

[Vivek Goyal]

On Thu, Jan 10, 2013 at 04:21:49AM +0100, Thomas Renninger wrote:
> On Tuesday, January 08, 2013 09:19:18 AM Yinghai Lu wrote:
> ...
> > 
> > that exactmap logic still have problem:
> > We need to check exactmap at first, aka need to scan the whole comand line
> > to see if exactmap is there at first and reset e820 tables then handle
> > other memmap opt.
> > 
> > Also please update your patch after
> > 
> > tip/x86/mm2
> > 
> > I have one patch that process memmap= with "," there.
> > 
> > http://git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=commitdiff;h=9710f58
> > 1bb4c35589ac046b0cfc0deb7f369fc85
> > 
> > We could put exactmap scanning in new parse_memmap_opt.
> 
> I still do not understand why:
> 
> Kexec (kexec/firmware_memmap.c) is setting up the e820 map from:
> /sys/firmware/memmap/*

Kexe reads it from /sys/firmware/memmap/* because that's supposed to
be e820 map as passed by BIOS. And if user has specified some
command line options like mem=X, /sys/firmware/memmap/* is not truncated
but one exported using /proc/iomem is truncated accordingly.

So if we pass mem=1G in first kernel but not in second kernel, we want
second kernel to see whole of the system memory and not just 1G.

> and pass it via bootloader structures.

That's how bootloader is supposed to pass e820 memory map to kernel and
kexec is a bootloader.

> And this e820 table gets immediately voided by memmap=exactmap
> and a new one passed via boot parameters is set up.
> If I read this correctly, this is what happens?

This happens only in case of kdump and not kexec. In case of kdump
we want second kernel to use only selected memory areas.

In fact this is one improvement area. Instead of using memmap= entries
in kdump case, we should probably modify the e820 map passed in 
zero page and get rid of memmap= entries.

Thanks
Vivek

Re: [PATCH] Only reset e820 once, even with multiple memmap=exactmap params

[Yinghai Lu]

On Thu, Jan 10, 2013 at 6:26 AM, Vivek Goyal <vgoyal@redhat.com> wrote:
>
> This happens only in case of kdump and not kexec. In case of kdump
> we want second kernel to use only selected memory areas.
>
> In fact this is one improvement area. Instead of using memmap= entries
> in kdump case, we should probably modify the e820 map passed in
> zero page and get rid of memmap= entries.

then how the kdump kernel get saved_max_pfn?

may have problem for read_oldmem with crashed kernel.

Yinghai

Re: [PATCH] Only reset e820 once, even with multiple memmap=exactmap params

[Vivek Goyal]

On Thu, Jan 10, 2013 at 08:53:18AM -0800, Yinghai Lu wrote:
> On Thu, Jan 10, 2013 at 6:26 AM, Vivek Goyal <vgoyal@redhat.com> wrote:
> >
> > This happens only in case of kdump and not kexec. In case of kdump
> > we want second kernel to use only selected memory areas.
> >
> > In fact this is one improvement area. Instead of using memmap= entries
> > in kdump case, we should probably modify the e820 map passed in
> > zero page and get rid of memmap= entries.
> 
> then how the kdump kernel get saved_max_pfn?
> 

Oh, I forgot about that. May be we can pass saved_max_pfn on command line
instead of passing all memmap= entries.

Thanks
Vivek

Re: [PATCH] Only reset e820 once, even with multiple memmap=exactmap params

[Yinghai Lu]

On Thu, Jan 10, 2013 at 9:01 AM, Vivek Goyal <vgoyal@redhat.com> wrote:
> On Thu, Jan 10, 2013 at 08:53:18AM -0800, Yinghai Lu wrote:
>> On Thu, Jan 10, 2013 at 6:26 AM, Vivek Goyal <vgoyal@redhat.com> wrote:
>> >
>> > This happens only in case of kdump and not kexec. In case of kdump
>> > we want second kernel to use only selected memory areas.
>> >
>> > In fact this is one improvement area. Instead of using memmap= entries
>> > in kdump case, we should probably modify the e820 map passed in
>> > zero page and get rid of memmap= entries.
>>
>> then how the kdump kernel get saved_max_pfn?
>>
>
> Oh, I forgot about that. May be we can pass saved_max_pfn on command line
> instead of passing all memmap= entries.

then we create another kernel version/kexec tools dependency.

kexec tools need to check kernel version, to see if saved_max_pfn= is supported.

Re: [PATCH] Only reset e820 once, even with multiple memmap=exactmap params

[Yinghai Lu]

[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]

On Wed, Jan 9, 2013 at 7:21 PM, Thomas Renninger <trenn@suse.de> wrote:
> I still do not understand why:
>
> Kexec (kexec/firmware_memmap.c) is setting up the e820 map from:
> /sys/firmware/memmap/*
> and pass it via bootloader structures.
> And this e820 table gets immediately voided by memmap=exactmap
> and a new one passed via boot parameters is set up.
> If I read this correctly, this is what happens?

yes, kdump scripts append those memmap.

>
> Can kexec simply pass the memory to use via memmap=X@Y
> Then take the original e820 table, but not the usable entries (those
> are coming from above memmap=X@Y).
> That would mean that the kexec kernel takes all the
> original ACPI, ACPI NVS, reserved, unusable (everthing but usable) entries
> from the original e820 table and identifies the usable memory from
> memmap boot param?

kdump scripts already do that for acpi regions, need to update it
to append that for mmconf.

>
> This would be much smarter than trying to pass the mmconf reserved
> area and I could imagine other issues will show up if the reserved areas
> do not match the original ones in the kexec kernel.
>
> If this really can be done and memmap=exactmap was only used by kexec,
> it's logic could be redefined from "drop all e820 entries" to
> "drop all usable e820 entries" and no further adjustings in kexec/kernel are
> needed to get mmconf working (and other issues may be avoided before
> they happen). Beside that ACPI reserved aread is not needed anymore to get
> passed via memmap=X#Y by kexec.

yes, we have other user for debug  like simulating user memmap for some bugs.

current problem for exactmap is that we don't scan that at first.

attached patch could help that.

Thanks

Yinghai

[-- Attachment #2: parse_exactmap_one_time.patch --]
[-- Type: application/octet-stream, Size: 1019 bytes --]

---
 arch/x86/kernel/e820.c |   12 ++++++++++++
 1 file changed, 12 insertions(+)

Index: linux-2.6/arch/x86/kernel/e820.c
===================================================================
--- linux-2.6.orig/arch/x86/kernel/e820.c
+++ linux-2.6/arch/x86/kernel/e820.c
@@ -835,6 +835,8 @@ static int __init parse_memopt(char *p)
 }
 early_param("mem", parse_memopt);
 
+static bool __initdata exactmap_parsed;
+
 static int __init parse_memmap_one(char *p)
 {
 	char *oldp;
@@ -844,6 +846,10 @@ static int __init parse_memmap_one(char
 		return -EINVAL;
 
 	if (!strncmp(p, "exactmap", 8)) {
+		if (exactmap_parsed)
+			return 0;
+
+		exactmap_parsed = true;
 #ifdef CONFIG_CRASH_DUMP
 		/*
 		 * If we are doing a crash dump, we still need to know
@@ -879,6 +885,12 @@ static int __init parse_memmap_one(char
 }
 static int __init parse_memmap_opt(char *str)
 {
+	char *p = boot_command_line;
+
+	p = strstr(p, "exactmap");
+	if (p)
+		parse_memmap_one("exactmap");
+
 	while (str) {
 		char *k = strchr(str, ',');
 

[PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Thomas Renninger]

[-- Attachment #1: Type: Text/Plain, Size: 4508 bytes --]

On Friday, January 11, 2013 12:34:37 AM Yinghai Lu wrote:
> On Wed, Jan 9, 2013 at 7:21 PM, Thomas Renninger <trenn@suse.de> wrote:
...
> > Can kexec simply pass the memory to use via memmap=X@Y
> > Then take the original e820 table, but not the usable entries (those
> > are coming from above memmap=X@Y).
> > That would mean that the kexec kernel takes all the
> > original ACPI, ACPI NVS, reserved, unusable (everthing but usable)
> > entries from the original e820 table and identifies the usable memory
> > from memmap boot param?
> 
> kdump scripts already do that for acpi regions, need to update it
> to append that for mmconf.

No, this must get fixed properly:
Use "unusable (ACPI, reserved, whatever..)" regions from the e820 table
passed through bootloader structure.

Only replace "usable" memory areas with the ones passed via memmap=
if memmap=exactmap is passed.

Only taking mmconf area is wrong, kdump kernel has to honour *all*
original reserved memory areas and the info is already there.
I also do not see any kernel vs kexec version incompatibilities with
my approach. Future kexec version can clean up and do not need to
pass ACPI memory area/range via memmap=X#Y anymore.

You find a suitable patch at the end.
I just zeroed out the e820 usable entries (same as e820_remove_range()
above), sanitize_e820_map() should fix that up and it's ensured that
it is called in memmap=exactmap case.

Find serial output of a try (same machine as with my previous posts).
There you find the correctly modified e820 user defined table (all
unusable entries, but usable entries are adjusted) until mmconf
is used gracefully.

> > This would be much smarter than trying to pass the mmconf reserved
> > area and I could imagine other issues will show up if the reserved
> > areas do not match the original ones in the kexec kernel.
> >
> > If this really can be done and memmap=exactmap was only used by kexec,
> > it's logic could be redefined from "drop all e820 entries" to
> > "drop all usable e820 entries" and no further adjustings in
> > kexec/kernel are needed to get mmconf working (and other issues may be
> > avoided before they happen). Beside that ACPI reserved aread is not
> > needed anymore to get passed via memmap=X#Y by kexec.

> yes, we have other user for debug  like simulating user memmap for some
> bugs.
> current problem for exactmap is that we don't scan that at first.
> attached patch could help that.

Yep, this is what I would have come up as well or similar. I looked
at it, but I had no time for doing it and trying out.

You may want to add:
Reviewed-by: Thomas Renninger <trenn@suse.de>
if someone reposts.

   Thomas

-------------------
x86 e820: only void usable memory areas in memmap=exactmap case

All unusable (reserved, ACPI, ACPI NVS,...) areas have to be
honored in kdump case.
Othwerise ACPI parts will quickly run into trouble when trying
to for example early_ioremap reserved areas which are not
declared reserved in kdump kernel.
mmconf area must also be a reserved mem region.
...

Passing unusable memory via memmap= is a design flaw as
this information is already (exactly for this purpose) passed
via bootloader structure.
In kdump case (when memmap=exactmap is passed), only void
(do not use) usable memory regions from the passed e820 table
and use memory areas defined via memmap=X@Y boot parameter instead.
But do still use the "unusable" memory regions from the original e820
table.

Signed-off-by: Thomas Renninger <trenn@suse.de>

---
 arch/x86/kernel/e820.c |   19 ++++++++++++++++++-
 1 files changed, 18 insertions(+), 1 deletions(-)

diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
index dc0b9f0..ae2d657 100644
--- a/arch/x86/kernel/e820.c
+++ b/arch/x86/kernel/e820.c
@@ -559,6 +559,19 @@ u64 __init e820_remove_range(u64 start, u64 size, unsigned old_type,
 	return real_removed_size;
 }
 
+static void __init e820_remove_range_type(u32 type)
+{
+	int i;
+
+	for (i = 0; i < e820.nr_map; i++) {
+		struct e820entry *ei = &e820.map[i];
+		if (ei->type == type) {
+			memset(ei, 0, sizeof(struct e820entry));
+			continue;
+		}
+	}
+}
+
 void __init update_e820(void)
 {
 	u32 nr_map;
@@ -858,7 +871,11 @@ static int __init parse_memmap_one(char *p)
 		 */
 		saved_max_pfn = e820_end_of_ram_pfn();
 #endif
-		e820.nr_map = 0;
+		/*
+		 * Remove all usable memory (this is for kdump), usable
+		 * memory will be passed via memmap=X@Y parameter
+		 */
+		e820_remove_range_type(E820_RAM);
 		userdef = 1;
 		return 0;
 	}

[-- Attachment #2: screen.xy --]
[-- Type: text/plain, Size: 16495 bytes --]

RIP  [<ffffffff813b05b1>] sysrq_handle_crash+0x11/0x20
 RSP <ffff882f5ca71e38>
CR2: 0000000000000000
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.8.0-rc2-default+ (trenn@ett) (gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux) ) #6 SMP Fri Jan 11 10:52:17 CET 2013
Command line: root=/dev/disk/by-label/ROOT-BE2 resume=/dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-part8 nmi_watchdog=0 elevator=noop log_buf_len=4M printk.time=0 udev_timeout=180 cgroup_disable=memory console=tty0 console=ttyS0,115200n elevator=deadline sysrq=yes reset_devices irqpoll maxcpus=1  sysrq=7 debug ignore_loglevel memmap=exactmap memmap=560K@64K memmap=392628K@114688K elfcorehdr=507316K memmap=252K#3099760K
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000100-0x000000000009bfff] usable
BIOS-e820: [mem 0x0000000000100000-0x00000000bd2effff] usable
BIOS-e820: [mem 0x00000000bd2f0000-0x00000000bd31bfff] reserved
BIOS-e820: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
BIOS-e820: [mem 0x00000000bd35b000-0x00000000bfffffff] reserved
BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
BIOS-e820: [mem 0x00000000fe000000-0x00000000ffffffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x000000603fffffff] usable
debug: ignoring loglevel setting.
e820: last_pfn = 0x6040000 max_arch_pfn = 0x400000000
NX (Execute Disable) protection: active
e820: user-defined physical RAM map:
user: [mem 0x0000000000010000-0x000000000009bfff] usable
user: [mem 0x0000000007000000-0x000000001ef6cfff] usable
user: [mem 0x00000000bd2f0000-0x00000000bd31bfff] reserved
user: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
user: [mem 0x00000000bd35b000-0x00000000bfffffff] reserved
user: [mem 0x00000000e0000000-0x00000000efffffff] reserved
user: [mem 0x00000000fe000000-0x00000000ffffffff] reserved
SMBIOS 2.7 present.
DMI: Dell Inc. PowerEdge R720/0M1GCR, BIOS 0.3.35 12/15/2011
e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
e820: remove [mem 0x000a0000-0x000fffff] usable
No AGP bridge found
e820: last_pfn = 0x1ef6d max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-BFFFF uncachable
  C0000-CBFFF write-protect
  CC000-D7FFF write-back
  D8000-EBFFF uncachable
  EC000-FFFFF write-protect
MTRR variable ranges enabled:
  0 base 000000000000 mask 3FC000000000 write-back
  1 base 004000000000 mask 3FE000000000 write-back
  2 base 006000000000 mask 3FFFC0000000 write-back
  3 base 0000C0000000 mask 3FFFC0000000 uncachable
  4 disabled
  5 disabled
  6 disabled
  7 disabled
  8 disabled
  9 disabled
x86 PAT enabled: cpu 0, old 0x7010600070106, new 0x7010600070106
e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
found SMP MP-table at [mem 0x000fe710-0x000fe71f] mapped at [ffff8800000fe710]
initial memory mapped: [mem 0x00000000-0x1fffffff]
Base memory trampoline at [ffff880000096000] 96000 size 24576
Using GB pages for direct mapping
init_memory_mapping: [mem 0x00000000-0x1ef6cfff]
 [mem 0x00000000-0x1edfffff] page 2M
 [mem 0x1ee00000-0x1ef6cfff] page 4k
kernel direct mapping tables up to 0x1ef6cfff @ [mem 0x1ef6a000-0x1ef6cfff]
log_buf_len: 4194304
early log buf free: 258076(98%)
RAMDISK: [mem 0x1e9ac000-0x1ef5bfff]
ACPI: RSDP 00000000000f10d0 00024 (v02 DELL  )
ACPI: XSDT 00000000000f11d4 0009C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: FACP 00000000bd34111c 000F4 (v03 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: DSDT 00000000bd31c000 05FCD (v01 DELL   PE_SC3   00000001 INTL 20110211)
ACPI: FACS 00000000bd343000 00040
ACPI: APIC 00000000bd340478 0016A (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SPCR 00000000bd3405e4 00050 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: HPET 00000000bd340638 00038 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: DMAR 00000000bd340674 00158 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: MCFG 00000000bd340950 0003C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: WD__ 00000000bd340990 00134 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SLIC 00000000bd340ac8 00176 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: ERST 00000000bd322170 00270 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: HEST 00000000bd3223e0 0055C (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: BERT 00000000bd321fd0 00030 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: EINJ 00000000bd322000 00170 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SRAT 00000000bd340cf0 003C0 (v01 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: TCPA 00000000bd3410b4 00064 (v02 DELL   PE_SC3   00000001 DELL 00000001)
ACPI: SSDT 00000000bd344000 0AA14 (v01 INTEL  PPM RCM  80000001 INTL 20061109)
ACPI: Local APIC address 0xfee00000
SRAT: PXM 1 -> APIC 0x00 -> Node 0
SRAT: PXM 2 -> APIC 0x20 -> Node 1
SRAT: PXM 1 -> APIC 0x02 -> Node 0
SRAT: PXM 2 -> APIC 0x22 -> Node 1
SRAT: PXM 1 -> APIC 0x04 -> Node 0
SRAT: PXM 2 -> APIC 0x24 -> Node 1
SRAT: PXM 1 -> APIC 0x06 -> Node 0
SRAT: PXM 2 -> APIC 0x26 -> Node 1
SRAT: PXM 1 -> APIC 0x08 -> Node 0
SRAT: PXM 2 -> APIC 0x28 -> Node 1
SRAT: PXM 1 -> APIC 0x0a -> Node 0
SRAT: PXM 2 -> APIC 0x2a -> Node 1
SRAT: PXM 1 -> APIC 0x0c -> Node 0
SRAT: PXM 2 -> APIC 0x2c -> Node 1
SRAT: PXM 1 -> APIC 0x0e -> Node 0
SRAT: PXM 2 -> APIC 0x2e -> Node 1
SRAT: PXM 1 -> APIC 0x01 -> Node 0
SRAT: PXM 2 -> APIC 0x21 -> Node 1
SRAT: PXM 1 -> APIC 0x03 -> Node 0
SRAT: PXM 2 -> APIC 0x23 -> Node 1
SRAT: PXM 1 -> APIC 0x05 -> Node 0
SRAT: PXM 2 -> APIC 0x25 -> Node 1
SRAT: PXM 1 -> APIC 0x07 -> Node 0
SRAT: PXM 2 -> APIC 0x27 -> Node 1
SRAT: PXM 1 -> APIC 0x09 -> Node 0
SRAT: PXM 2 -> APIC 0x29 -> Node 1
SRAT: PXM 1 -> APIC 0x0b -> Node 0
SRAT: PXM 2 -> APIC 0x2b -> Node 1
SRAT: PXM 1 -> APIC 0x0d -> Node 0
SRAT: PXM 2 -> APIC 0x2d -> Node 1
SRAT: PXM 1 -> APIC 0x0f -> Node 0
SRAT: PXM 2 -> APIC 0x2f -> Node 1
SRAT: Node 0 PXM 1 [mem 0x00000000-0x303fffffff]
SRAT: Node 1 PXM 2 [mem 0x3040000000-0x603fffffff]
Initmem setup node 0 [mem 0x00000000-0x1ef6cfff]
  NODE_DATA [mem 0x1e598000-0x1e5abfff]
 [ffffea0000000000-ffffea00007fffff] PMD -> [ffff88001d400000-ffff88001dbfffff] on node 0
Zone ranges:
  DMA      [mem 0x00010000-0x00ffffff]
  DMA32    [mem 0x01000000-0xffffffff]
  Normal   empty
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x00010000-0x0009bfff]
  node   0: [mem 0x07000000-0x1ef6cfff]
On node 0 totalpages: 98297
  DMA zone: 3 pages used for memmap
  DMA zone: 6 pages reserved
  DMA zone: 131 pages, LIFO batch:0
  DMA32 zone: 1534 pages used for memmap
  DMA32 zone: 96623 pages, LIFO batch:31
pci 0000:01:00.0 save state
pci 0000:01:00.1 save state
pci 0000:01:00.2 save state
pci 0000:01:00.3 save state
pci 0000:02:00.0 save state
pci 0000:05:00.0 save state
pci 0000:48:00.0 save state
pci 0000:48:00.1 save state
pci 0000:44:00.0 save state
pci 0000:45:00.0 save state
pci 0000:46:00.0 save state
pci 0000:47:00.0 save state
pci 0000:00:01.0 reset
pci 0000:00:02.2 reset
pci 0000:00:03.2 reset
pci 0000:40:02.0 reset
pci 0000:42:05.0 reset
pci 0000:42:06.0 reset
pci 0000:42:08.0 reset
pci 0000:42:09.0 reset
pci 0000:01:00.0 restore state
pci 0000:01:00.1 restore state
pci 0000:01:00.2 restore state
pci 0000:01:00.3 restore state
pci 0000:02:00.0 restore state
pci 0000:05:00.0 restore state
pci 0000:48:00.0 restore state
pci 0000:48:00.1 restore state
pci 0000:44:00.0 restore state
pci 0000:45:00.0 restore state
pci 0000:46:00.0 restore state
pci 0000:47:00.0 restore state
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x20] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x22] enabled)
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x24] enabled)
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x08] lapic_id[0x26] enabled)
ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] enabled)
ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x28] enabled)
ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] enabled)
ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2a] enabled)
ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] enabled)
ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2c] enabled)
ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] enabled)
ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2e] enabled)
ACPI: LAPIC (acpi_id[0x11] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x12] lapic_id[0x21] enabled)
ACPI: LAPIC (acpi_id[0x13] lapic_id[0x03] enabled)
ACPI: LAPIC (acpi_id[0x14] lapic_id[0x23] enabled)
ACPI: LAPIC (acpi_id[0x15] lapic_id[0x05] enabled)
ACPI: LAPIC (acpi_id[0x16] lapic_id[0x25] enabled)
ACPI: LAPIC (acpi_id[0x17] lapic_id[0x07] enabled)
ACPI: LAPIC (acpi_id[0x18] lapic_id[0x27] enabled)
ACPI: LAPIC (acpi_id[0x19] lapic_id[0x09] enabled)
ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x29] enabled)
ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x0b] enabled)
ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x2b] enabled)
ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x0d] enabled)
ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x2d] enabled)
ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x0f] enabled)
ACPI: LAPIC (acpi_id[0x20] lapic_id[0x2f] enabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x01] address[0xfec3f000] gsi_base[32])
IOAPIC[1]: apic_id 1, version 32, address 0xfec3f000, GSI 32-55
ACPI: IOAPIC (id[0x02] address[0xfec7f000] gsi_base[64])
IOAPIC[2]: apic_id 2, version 32, address 0xfec7f000, GSI 64-87
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a701 base: 0xfed00000
smpboot: Allowing 32 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 104
PM: Registered nosave memory: 000000000009c000 - 0000000007000000
e820: [mem 0x1ef6d000-0xbd2effff] available for PCI devices
Booting paravirtualized kernel on bare hardware
setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:32 nr_node_ids:2
PERCPU: Embedded 27 pages/cpu @ffff88001e000000 s81728 r8192 d20672 u131072
pcpu-alloc: s81728 r8192 d20672 u131072 alloc=1*2097152
pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 
pcpu-alloc: [0] 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 96754
Policy zone: DMA32
Kernel command line: root=/dev/disk/by-label/ROOT-BE2 resume=/dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-part8 nmi_watchdog=0 elevator=noop log_buf_len=4M printk.time=0 udev_timeout=180 cgroup_disable=memory console=tty0 console=ttyS0,115200n elevator=deadline sysrq=yes reset_devices irqpoll maxcpus=1  sysrq=7 debug ignore_loglevel memmap=exactmap memmap=560K@64K memmap=392628K@114688K elfcorehdr=507316K memmap=252K#3099760K
Disabling memory control group subsystem
Misrouted IRQ fixup and polling support enabled
This may significantly impact system performance
PID hash table entries: 2048 (order: 2, 16384 bytes)
__ex_table already sorted, skipping sort
xsave: enabled xstate_bv 0x7, cntxt size 0x340
Checking aperture...
No AGP bridge found
Memory: 357760k/507316k available (5832k kernel code, 114128k absent, 35428k reserved, 5095k data, 1000k init)
Hierarchical RCU implementation.
	RCU dyntick-idle grace-period acceleration is enabled.
	RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=32.
NR_IRQS:33024 nr_irqs:2024 16
Extended CMOS year: 2000
Spurious LAPIC timer interrupt on cpu 0
do_IRQ: 0.231 No irq handler for vector (irq -1)
do_IRQ: 0.230 No irq handler for vector (irq -1)
do_IRQ: 0.229 No irq handler for vector (irq -1)
do_IRQ: 0.223 No irq handler for vector (irq -1)
do_IRQ: 0.199 No irq handler for vector (irq -1)
do_IRQ: 0.183 No irq handler for vector (irq -1)
do_IRQ: 0.182 No irq handler for vector (irq -1)
do_IRQ: 0.181 No irq handler for vector (irq -1)
do_IRQ: 0.176 No irq handler for vector (irq -1)
do_IRQ: 0.160 No irq handler for vector (irq -1)
Console: colour VGA+ 80x25
console [tty0] enabled
console [ttyS0] enabled
Enabling automatic NUMA balancing. Configure with numa_balancing= or sysctl
hpet clockevent registered
tsc: Fast TSC calibration using PIT
tsc: Detected 2699.986 MHz processor
Calibrating delay loop (skipped), value calculated using timer frequency.. 5399.97 BogoMIPS (lpj=10799944)
pid_max: default: 32768 minimum: 301
Security Framework initialized
AppArmor: AppArmor initialized
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 256
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
Initializing cgroup subsys blkio
Initializing cgroup subsys perf_event
Initializing cgroup subsys hugetlb
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 20 MCE banks
CPU0: Thermal LVT vector (0xfa) already installed
process: using mwait in idle threads
Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0
Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32
tlb_flushall_shift: 5
ACPI: Core revision 20121018
dmar: Host address width 46
dmar: DRHD base: 0x000000d0d00000 flags: 0x0
dmar: IOMMU 0: reg_base_addr d0d00000 ver 1:0 cap d2078c106f0462 ecap f020fe
dmar: DRHD base: 0x000000dc900000 flags: 0x1
dmar: IOMMU 1: reg_base_addr dc900000 ver 1:0 cap d2078c106f0462 ecap f020fe
dmar: RMRR base: 0x000000bf458000 end: 0x000000bf46ffff
dmar: RMRR base: 0x000000bf450000 end: 0x000000bf450fff
dmar: RMRR base: 0x000000bf452000 end: 0x000000bf452fff
dmar: ATSR flags: 0x0
IOAPIC id 2 under DRHD base  0xd0d00000 IOMMU 0
IOAPIC id 0 under DRHD base  0xdc900000 IOMMU 1
IOAPIC id 1 under DRHD base  0xdc900000 IOMMU 1
HPET id 0 under DRHD base 0xdc900000
------------[ cut here ]------------
WARNING: at drivers/iommu/intel_irq_remapping.c:542 intel_enable_irq_remapping+0x7d/0x26f()
Hardware name: PowerEdge R720
Your BIOS is broken and requested that x2apic be disabled
This will leave your machine vulnerable to irq-injection attacks
Use 'intremap=no_x2apic_optout' to override BIOS request
Modules linked in:
Pid: 1, comm: swapper/0 Not tainted 3.8.0-rc2-default+ #6
Call Trace:
 [<ffffffff81047e2a>] warn_slowpath_common+0x7a/0xb0
 [<ffffffff81047f01>] warn_slowpath_fmt+0x41/0x50
 [<ffffffff81afe84f>] intel_enable_irq_remapping+0x7d/0x26f
 [<ffffffff81afeb93>] irq_remapping_enable+0x20/0x22
 [<ffffffff81acf0eb>] enable_IR+0x5d/0x65
 [<ffffffff81acf3d7>] enable_IR_x2apic+0x95/0x247
 [<ffffffff81026099>] ? cpumask_next+0x19/0x20
 [<ffffffff8159b9b8>] ? set_cpu_sibling_map+0x405/0x422
 [<ffffffff81026831>] ? apic_write+0x11/0x20
 [<ffffffff81ad1f26>] default_setup_apic_routing+0x15/0x6e
 [<ffffffff81accfe6>] native_smp_prepare_cpus+0x137/0x234
 [<ffffffff81ac1c8e>] kernel_init_freeable+0xa2/0x1e1
 [<ffffffff815928b0>] ? rest_init+0x80/0x80
 [<ffffffff815928b9>] kernel_init+0x9/0xf0
 [<ffffffff815ae5bc>] ret_from_fork+0x7c/0xb0
 [<ffffffff815928b0>] ? rest_init+0x80/0x80
---[ end trace 3970bb530c07ade7 ]---
Enabled IRQ remapping in xapic mode
x2apic not enabled, IRQ remapping is in xapic mode
Switched APIC routing to physical flat.
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
smpboot: CPU0: Genuine Intel(R) CPU  @ 2.70GHz (fam: 06, model: 2d, stepping: 05)
TSC deadline timer enabled
Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, Intel PMU driver.
perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode
... version:                3
... bit width:              48
... generic registers:      4
... value mask:             0000ffffffffffff
... max period:             000000007fffffff
... fixed-purpose events:   3
... event mask:             000000070000000f
Brought up 1 CPUs
smpboot: Total of 1 processors activated (5399.97 BogoMIPS)
devtmpfs: initialized
RTC time: 12:21:09, date: 01/11/13
NET: Registered protocol family 16
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
PCI: Using configuration type 1 for base access

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Yinghai Lu]

On Fri, Jan 11, 2013 at 4:33 AM, Thomas Renninger <trenn@suse.de> wrote:
>> yes, we have other user for debug  like simulating user memmap for some
>> bugs.
>> current problem for exactmap is that we don't scan that at first.
>> attached patch could help that.
>
> Yep, this is what I would have come up as well or similar. I looked
> at it, but I had no time for doing it and trying out.
>
> You may want to add:
> Reviewed-by: Thomas Renninger <trenn@suse.de>
> if someone reposts.

ok, I will add wrap it up and add changelog and test it then post it
with my for-x86-boot.

>
>    Thomas
>
> -------------------
> x86 e820: only void usable memory areas in memmap=exactmap case
>
> All unusable (reserved, ACPI, ACPI NVS,...) areas have to be
> honored in kdump case.
> Othwerise ACPI parts will quickly run into trouble when trying
> to for example early_ioremap reserved areas which are not
> declared reserved in kdump kernel.
> mmconf area must also be a reserved mem region.
> ...
>
> Passing unusable memory via memmap= is a design flaw as
> this information is already (exactly for this purpose) passed
> via bootloader structure.
> In kdump case (when memmap=exactmap is passed), only void
> (do not use) usable memory regions from the passed e820 table
> and use memory areas defined via memmap=X@Y boot parameter instead.
> But do still use the "unusable" memory regions from the original e820
> table.
>
> Signed-off-by: Thomas Renninger <trenn@suse.de>
>
> ---
>  arch/x86/kernel/e820.c |   19 ++++++++++++++++++-
>  1 files changed, 18 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
> index dc0b9f0..ae2d657 100644
> --- a/arch/x86/kernel/e820.c
> +++ b/arch/x86/kernel/e820.c
> @@ -559,6 +559,19 @@ u64 __init e820_remove_range(u64 start, u64 size, unsigned old_type,
>         return real_removed_size;
>  }
>
> +static void __init e820_remove_range_type(u32 type)
> +{
> +       int i;
> +
> +       for (i = 0; i < e820.nr_map; i++) {
> +               struct e820entry *ei = &e820.map[i];
> +               if (ei->type == type) {
> +                       memset(ei, 0, sizeof(struct e820entry));
> +                       continue;
> +               }
> +       }
> +}
> +
>  void __init update_e820(void)
>  {
>         u32 nr_map;
> @@ -858,7 +871,11 @@ static int __init parse_memmap_one(char *p)
>                  */
>                 saved_max_pfn = e820_end_of_ram_pfn();
>  #endif
> -               e820.nr_map = 0;
> +               /*
> +                * Remove all usable memory (this is for kdump), usable
> +                * memory will be passed via memmap=X@Y parameter
> +                */
> +               e820_remove_range_type(E820_RAM);

We may need to keep exactmap intact.

but could add another one like exact_ram_map
or extend to have memmap=exactmap=ram or etc.

>                 userdef = 1;
>                 return 0;
>         }

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Thomas Renninger]

On Friday, January 11, 2013 08:16:52 AM Yinghai Lu wrote:
> On Fri, Jan 11, 2013 at 4:33 AM, Thomas Renninger <trenn@suse.de> wrote:
...
> > -               e820.nr_map = 0;
> > +               /*
> > +                * Remove all usable memory (this is for kdump), usable
> > +                * memory will be passed via memmap=X@Y parameter
> > +                */
> > +               e820_remove_range_type(E820_RAM);
> 
> We may need to keep exactmap intact.
Why?
Kexec/kdump should have been the only user?
If older/current kexec calls still add ACPI maps via memmap=X#Y,
they should already exist in the original e820 map and fall off or
get glued to one region if (wrongly) overlapping via sanitize_map.
 
> but could add another one like exact_ram_map
> or extend to have memmap=exactmap=ram or etc.

I would avoid that if anyhow possible because then you run into
kexec vs kernel version problems.

Maybe I should explicitly post (out of this thread) the patch to the
kexec list.
If nobody can come up with a strong reason, it should be ok?

   Thomas

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Yinghai Lu]

On Fri, Jan 11, 2013 at 10:24 AM, Thomas Renninger <trenn@suse.de> wrote:
>> We may need to keep exactmap intact.
> Why?
> Kexec/kdump should have been the only user?
> If older/current kexec calls still add ACPI maps via memmap=X#Y,
> they should already exist in the original e820 map and fall off or
> get glued to one region if (wrongly) overlapping via sanitize_map.

No, kexec/kdump is not the only user for memmap=exactmap.

Thanks

Yinghai

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[H. Peter Anvin]

On 01/11/2013 11:59 AM, Yinghai Lu wrote:
> On Fri, Jan 11, 2013 at 10:24 AM, Thomas Renninger <trenn@suse.de> wrote:
>>> We may need to keep exactmap intact.
>> Why?
>> Kexec/kdump should have been the only user?
>> If older/current kexec calls still add ACPI maps via memmap=X#Y,
>> they should already exist in the original e820 map and fall off or
>> get glued to one region if (wrongly) overlapping via sanitize_map.
> 
> No, kexec/kdump is not the only user for memmap=exactmap.
> 

Who is using it then, since you seem to know?

	-hpa

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Yinghai Lu]

On Fri, Jan 11, 2013 at 12:06 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> On 01/11/2013 11:59 AM, Yinghai Lu wrote:
>> On Fri, Jan 11, 2013 at 10:24 AM, Thomas Renninger <trenn@suse.de> wrote:
>>>> We may need to keep exactmap intact.
>>> Why?
>>> Kexec/kdump should have been the only user?
>>> If older/current kexec calls still add ACPI maps via memmap=X#Y,
>>> they should already exist in the original e820 map and fall off or
>>> get glued to one region if (wrongly) overlapping via sanitize_map.
>>
>> No, kexec/kdump is not the only user for memmap=exactmap.
>>
>
> Who is using it then, since you seem to know?

http://forums.gentoo.org/viewtopic-t-487476-highlight-proliant.html

http://forums.fedoraforum.org/archive/index.php/t-225347.html

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[H. Peter Anvin]

On 01/11/2013 01:09 PM, Yinghai Lu wrote:
> On Fri, Jan 11, 2013 at 12:06 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> On 01/11/2013 11:59 AM, Yinghai Lu wrote:
>>> On Fri, Jan 11, 2013 at 10:24 AM, Thomas Renninger <trenn@suse.de> wrote:
>>>>> We may need to keep exactmap intact.
>>>> Why?
>>>> Kexec/kdump should have been the only user?
>>>> If older/current kexec calls still add ACPI maps via memmap=X#Y,
>>>> they should already exist in the original e820 map and fall off or
>>>> get glued to one region if (wrongly) overlapping via sanitize_map.
>>>
>>> No, kexec/kdump is not the only user for memmap=exactmap.
>>>
>>
>> Who is using it then, since you seem to know?
> 
> http://forums.gentoo.org/viewtopic-t-487476-highlight-proliant.html
> 
> http://forums.fedoraforum.org/archive/index.php/t-225347.html
> 

Hm... both of those seem to be someone trying memmap=exactmap to hack
around a problem which really was elsewhere, with a different solution.

	-hpa

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Thomas Renninger]

On Friday, January 11, 2013 02:16:35 PM H. Peter Anvin wrote:
> On 01/11/2013 01:09 PM, Yinghai Lu wrote:
> > On Fri, Jan 11, 2013 at 12:06 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> >> On 01/11/2013 11:59 AM, Yinghai Lu wrote:
> >>> On Fri, Jan 11, 2013 at 10:24 AM, Thomas Renninger <trenn@suse.de> wrote:
> >>>>> We may need to keep exactmap intact.
> >>>> 
> >>>> Why?
> >>>> Kexec/kdump should have been the only user?
> >>>> If older/current kexec calls still add ACPI maps via memmap=X#Y,
> >>>> they should already exist in the original e820 map and fall off or
> >>>> get glued to one region if (wrongly) overlapping via sanitize_map.
> >>> 
> >>> No, kexec/kdump is not the only user for memmap=exactmap.
> >> 
> >> Who is using it then, since you seem to know?
> > 
> > http://forums.gentoo.org/viewtopic-t-487476-highlight-proliant.html
> > 
> > http://forums.fedoraforum.org/archive/index.php/t-225347.html
> 
> Hm... both of those seem to be someone trying memmap=exactmap to hack
> around a problem which really was elsewhere, with a different solution.

Ok, boot params can be counted as "public interface" to the kernel that should/must
not change.
Generally there are several flavors of these:
  1) Purely (low level) debug options
  2) Workarounds for broken HW
  3) Real interface that may make sense on productive systems and which
      applications may pick up

In this case we have a mixture of all.
Kexec/kdump would be the only one for 3. I expect.

IMO nobody should run memmap=exactmap on a productive machine.
These have a sever BIOS (or whereever) bugs and will jump from one
trap to the other trying to update the kernel and similar.
This applies for above 2 links.

What is confusing for developers is if they used memmap=exactmap
already to try a self made up e820 table and might get angry if he realizes
after some time that its usage changed silently

Still introducing another memmap=param would be very unfortunate because
of the kexec version (and work) dependency to get this fixed properly.

Hm, whatabout this:
Tell user that memmap=exactmap usage has changed in !kdump case.
This would cover the very rare cases you mentioned.

In kdump case passing an extra exactmap option was broken anyway.
No need to bore the user with an additional message there.

is_kdump_kernel() cannot be used because it's too early.
But the check is exactly the same (will elfcorehdr_addr be set via
the corresponding boot param).

Compile tested only:


-----------------------------
x86 e820: only void usable memory areas in memmap=exactmap case

All unusable (reserved, ACPI, ACPI NVS,...) areas have to be
honored in kdump case.
Othwerise ACPI parts will quickly run into trouble when trying
to for example early_ioremap reserved areas which are not
declared reserved in kdump kernel.
mmconf area must also be a reserved mem region.

Passing unusable memory via memmap= is a design flaw as
this information is already (exactly for this purpose) passed
via bootloader structure.
In kdump case (when memmap=exactmap is passed), only void
(do not use) usable memory regions from the passed e820 table
and use memory areas defined via memmap=X@Y boot parameter instead.
But do still use the "unusable" memory regions from the original e820
table.

Rename exactmap_parsed to memmap checked as voidmap needs the same checking.

Signed-off-by: Thomas Renninger <trenn@suse.de>

---
 Documentation/kernel-parameters.txt |   18 ++++++++++---
 arch/x86/kernel/e820.c              |   46 ++++++++++++++++++++++++++++++++--
 2 files changed, 57 insertions(+), 7 deletions(-)

diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 363e348..739b665 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -1510,10 +1510,20 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
 			per-device physically contiguous DMA buffers.
 
 	memmap=exactmap	[KNL,X86] Enable setting of an exact
-			E820 memory map, as specified by the user.
-			Such memmap=exactmap lines can be constructed based on
-			BIOS output or other requirements. See the memmap=nn@ss
-			option description.
+			E820 usable memory map, as specified by the user.
+			All unusable (reserved, ACPI, NVS,...) ranges from the
+			original e820 table are preserved.
+			But the usable memory regions from the original e820
+			table are removed.
+			This parameter is explicitly for kdump usage:
+			The memory the kdump kernel is allowed to use must
+			be passed via below memmap=nn[KMG]@ss[KMG] param.
+			All reserved regions the kernel may use for ioremapping
+			and similar are still considered.
+
+	memmap=voidmap  [KNL,X86] Do not use any e820 ranges from BIOS or
+			bootloader. Instead you have to pass regions via
+			below memmap= options.
 
 	memmap=nn[KMG]@ss[KMG]
 			[KNL] Force usage of a specific region of memory
diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
index dc0b9f0..4a3803a 100644
--- a/arch/x86/kernel/e820.c
+++ b/arch/x86/kernel/e820.c
@@ -559,6 +559,19 @@ u64 __init e820_remove_range(u64 start, u64 size, unsigned old_type,
 	return real_removed_size;
 }
 
+static void __init e820_remove_range_type(u32 type)
+{
+	int i;
+
+	for (i = 0; i < e820.nr_map; i++) {
+		struct e820entry *ei = &e820.map[i];
+		if (ei->type == type) {
+			memset(ei, 0, sizeof(struct e820entry));
+			continue;
+		}
+	}
+}
+
 void __init update_e820(void)
 {
 	u32 nr_map;
@@ -835,21 +848,32 @@ static int __init parse_memopt(char *p)
 }
 early_param("mem", parse_memopt);
 
-static bool __initdata exactmap_parsed;
+static bool __initdata memmap_checked;
 
 static int __init parse_memmap_one(char *p)
 {
 	char *oldp;
 	u64 start_at, mem_size;
+	char *cmdline = boot_command_line;
 
 	if (!p)
 		return -EINVAL;
 
 	if (!strncmp(p, "exactmap", 8)) {
-		if (exactmap_parsed)
+		if (memmap_checked)
 			return 0;
 
-		exactmap_parsed = true;
+		memmap_checked = true;
+		cmdline = strstr(cmdline, "elfcorehdr");
+		if (!cmdline)
+			/*
+			 * No kdump kernel, but exactmap used.
+			 * Tell user about exactmap changes.
+			 * Remove this after some kernel revisions.
+			 */
+			pr_info(
+		"memmap=exactmap changed, use voidmap for old behavior\n");
+
 #ifdef CONFIG_CRASH_DUMP
 		/*
 		 * If we are doing a crash dump, we still need to know
@@ -858,6 +882,22 @@ static int __init parse_memmap_one(char *p)
 		 */
 		saved_max_pfn = e820_end_of_ram_pfn();
 #endif
+		/*
+		 * Remove all usable memory (this is for kdump), usable
+		 * memory will be passed via memmap=X@Y parameter
+		 */
+		e820_remove_range_type(E820_RAM);
+		userdef = 1;
+		return 0;
+	} else if (!strncmp(p, "voidmap", 7)) {
+		if (memmap_checked)
+			return 0;
+
+		memmap_checked = true;
+
+#ifdef CONFIG_CRASH_DUMP
+		saved_max_pfn = e820_end_of_ram_pfn();
+#endif
 		e820.nr_map = 0;
 		userdef = 1;
 		return 0;

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Yinghai Lu]

On Sat, Jan 12, 2013 at 3:31 AM, Thomas Renninger <trenn@suse.de> wrote:
>         memmap=exactmap [KNL,X86] Enable setting of an exact
> -                       E820 memory map, as specified by the user.
> -                       Such memmap=exactmap lines can be constructed based on
> -                       BIOS output or other requirements. See the memmap=nn@ss
> -                       option description.
> +                       E820 usable memory map, as specified by the user.
> +                       All unusable (reserved, ACPI, NVS,...) ranges from the
> +                       original e820 table are preserved.
> +                       But the usable memory regions from the original e820
> +                       table are removed.
> +                       This parameter is explicitly for kdump usage:
> +                       The memory the kdump kernel is allowed to use must
> +                       be passed via below memmap=nn[KMG]@ss[KMG] param.
> +                       All reserved regions the kernel may use for ioremapping
> +                       and similar are still considered.
> +
> +       memmap=voidmap  [KNL,X86] Do not use any e820 ranges from BIOS or
> +                       bootloader. Instead you have to pass regions via
> +                       below memmap= options.

I would suggest to keep memmap=exactmap meaning not changed, and add
memmap=exactusablemap
instead.

kexec-tools could be updated to support exactusablemap with
kernelversion checking for kdump.

also we need to double check to make sure:
1. exactmap should override exactusablemap, even the out of order sequence.
2. when exactusablemap is used, not just remove old usable type range,
also need to remove overlapped range
with new usable range.

Thanks

Yinghai

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Thomas Renninger]

On Saturday, January 12, 2013 09:07:12 AM Yinghai Lu wrote:
> On Sat, Jan 12, 2013 at 3:31 AM, Thomas Renninger <trenn@suse.de> wrote:
> >         memmap=exactmap [KNL,X86] Enable setting of an exact
> > 
> > -                       E820 memory map, as specified by the user.
> > -                       Such memmap=exactmap lines can be constructed
> > based on -                       BIOS output or other requirements. See
> > the memmap=nn@ss -                       option description.
> > +                       E820 usable memory map, as specified by the user.
> > +                       All unusable (reserved, ACPI, NVS,...) ranges from
> > the +                       original e820 table are preserved.
> > +                       But the usable memory regions from the original
> > e820 +                       table are removed.
> > +                       This parameter is explicitly for kdump usage:
> > +                       The memory the kdump kernel is allowed to use must
> > +                       be passed via below memmap=nn[KMG]@ss[KMG] param.
> > +                       All reserved regions the kernel may use for
> > ioremapping +                       and similar are still considered.
> > +
> > +       memmap=voidmap  [KNL,X86] Do not use any e820 ranges from BIOS or
> > +                       bootloader. Instead you have to pass regions via
> > +                       below memmap= options.
> 
> I would suggest to keep memmap=exactmap meaning not changed, and add
> memmap=exactusablemap
> instead.
I disagree.
I would like to change memmap=exactmap behavior.

Why:
1)
This is a sever bug (for kdump/kexec). I could imagine quite a lot
kdump related bugs get silently solved by this fix.
I expect we agree that the change, however it looks like in the end, should
still get in in this kernel round?
With my approach, I would also suggest to spread this to stable kernels.
-> No need to update/patch kexec-tools, things will just work as they should.

2)
I would introduce 2 new memmap= options. However they look like, for example:
=void_usable_map
=void_orig_map
and deprecated exactmap= via
printk(KERN_INFO "exactmap usage changed and is deprecated\n");
but still fix it.
Latest kexec-tools will just use memmap=void_usable_map, old ones
are still fixed via stable kernel updates.


> kexec-tools could be updated to support exactusablemap with
> kernelversion checking for kdump.
No, please not. It will be a maintenance/compatibility issue that will remain
for years or ever in kdump and/or the kernel and it's not necessary.

> also we need to double check to make sure:
> 1. exactmap should override exactusablemap, even the out of order sequence.
So that one can override the whole map in kdump case (which was broken until
today)?
I agree. But in my case it would be:
=void_orig_map overrides =void_usable_map

> 2. when exactusablemap is used, not just remove old usable type range,
> also need to remove overlapped range
> with new usable range.
Why should this be necessary?
The e820 map passed by BIOS/bootloader should already be sanity checked
-> no overlaps.

Then usable ranges are removed and the memmap= defined are added and
sanity check is called again.
-> no overlaps.

Sanity checking prefers reserved/unusable memory ranges (in this case always 
using the original ones from BIOS) over usable ones and this is a good idea to 
do...

I guess it's up to further votes/comments/ideas and a final maintainer 
(kexec/x86?) decision?


    Thomas

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Yinghai Lu]

[-- Attachment #1: Type: text/plain, Size: 3628 bytes --]

On Sun, Jan 13, 2013 at 6:08 PM, Thomas Renninger <trenn@suse.de> wrote:
> On Saturday, January 12, 2013 09:07:12 AM Yinghai Lu wrote:
>> On Sat, Jan 12, 2013 at 3:31 AM, Thomas Renninger <trenn@suse.de> wrote:
>> >         memmap=exactmap [KNL,X86] Enable setting of an exact
>> >
>> > -                       E820 memory map, as specified by the user.
>> > -                       Such memmap=exactmap lines can be constructed
>> > based on -                       BIOS output or other requirements. See
>> > the memmap=nn@ss -                       option description.
>> > +                       E820 usable memory map, as specified by the user.
>> > +                       All unusable (reserved, ACPI, NVS,...) ranges from
>> > the +                       original e820 table are preserved.
>> > +                       But the usable memory regions from the original
>> > e820 +                       table are removed.
>> > +                       This parameter is explicitly for kdump usage:
>> > +                       The memory the kdump kernel is allowed to use must
>> > +                       be passed via below memmap=nn[KMG]@ss[KMG] param.
>> > +                       All reserved regions the kernel may use for
>> > ioremapping +                       and similar are still considered.
>> > +
>> > +       memmap=voidmap  [KNL,X86] Do not use any e820 ranges from BIOS or
>> > +                       bootloader. Instead you have to pass regions via
>> > +                       below memmap= options.
>>
>> I would suggest to keep memmap=exactmap meaning not changed, and add
>> memmap=exactusablemap
>> instead.
> I disagree.
> I would like to change memmap=exactmap behavior.
>
> Why:
> 1)
> This is a sever bug (for kdump/kexec). I could imagine quite a lot
> kdump related bugs get silently solved by this fix.
> I expect we agree that the change, however it looks like in the end, should
> still get in in this kernel round?
> With my approach, I would also suggest to spread this to stable kernels.
> -> No need to update/patch kexec-tools, things will just work as they should.
>
> 2)
> I would introduce 2 new memmap= options. However they look like, for example:
> =void_usable_map
> =void_orig_map
> and deprecated exactmap= via
> printk(KERN_INFO "exactmap usage changed and is deprecated\n");
> but still fix it.
> Latest kexec-tools will just use memmap=void_usable_map, old ones
> are still fixed via stable kernel updates.

everyone could understand it straightforward:
exactmap:  memmap will be specified, and it should be honored without
considering old any memmap.
exactusablemap: will make sure only old ram range get removed, and
specified usable ranges will become final usable
ranges in the final memmap. so we need to remove overlapping to old
reserved ranges.

aka: exact means EXACT ...

>
>
>> kexec-tools could be updated to support exactusablemap with
>> kernelversion checking for kdump.
> No, please not. It will be a maintenance/compatibility issue that will remain
> for years or ever in kdump and/or the kernel and it's not necessary.

I don't see there is any problem with it.

those just some kind of improvement without considering kdump.
because kdump/scripts already does good job to provide right exactmap
with usable and acpi reserved areas.
for mmconf, some system that range reserved in e820, and some have that in ACPI.
and those systems will have that mmconf enabled in kdumped kernel.

attached is what I like to have with exactusablemap, but maybe is not
needed, and we can just stay with exactmap...

ps: we don't need to add e820_remove_type...

Yinghai

[-- Attachment #2: e820_exactusablemap.patch --]
[-- Type: application/octet-stream, Size: 1819 bytes --]

---
 arch/x86/kernel/e820.c |   20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

Index: linux-2.6/arch/x86/kernel/e820.c
===================================================================
--- linux-2.6.orig/arch/x86/kernel/e820.c
+++ linux-2.6/arch/x86/kernel/e820.c
@@ -836,6 +836,7 @@ static int __init parse_memopt(char *p)
 early_param("mem", parse_memopt);
 
 static bool __initdata exactmap_parsed;
+static bool __initdata exactusablemap_parsed;
 
 static int __init parse_memmap_one(char *p)
 {
@@ -845,7 +846,7 @@ static int __init parse_memmap_one(char
 	if (!p)
 		return -EINVAL;
 
-	if (!strncmp(p, "exactmap", 8)) {
+	if (!strncmp(p, "exactmap", 8) || !strncmp(p, "exactusablemap", 14)) {
 		if (exactmap_parsed)
 			return 0;
 
@@ -858,6 +859,13 @@ static int __init parse_memmap_one(char
 		 */
 		saved_max_pfn = e820_end_of_ram_pfn();
 #endif
+		if (!strncmp(p, "exactusablemap", 14)) {
+			/* remove all old E820_RAM ranges */
+			e820_remove_range(0, ULLONG_MAX, E820_RAM, 1);
+			exactusablemap_parsed = true;
+			userdef = 1;
+			return 0;
+		}
 		e820.nr_map = 0;
 		userdef = 1;
 		return 0;
@@ -871,6 +879,11 @@ static int __init parse_memmap_one(char
 	userdef = 1;
 	if (*p == '@') {
 		start_at = memparse(p+1, &p);
+		if (exactusablemap_parsed) {
+			/* remove all range with other types */
+			e820_remove_range(start_at, mem_size,
+						 E820_RAM, 0);
+		}
 		e820_add_region(start_at, mem_size, E820_RAM);
 	} else if (*p == '#') {
 		start_at = memparse(p+1, &p);
@@ -890,6 +903,11 @@ static int __init parse_memmap_opt(char
 	p = strstr(p, "exactmap");
 	if (p)
 		parse_memmap_one("exactmap");
+	else {
+		p = strstr(boot_command_line, "exactusablemap");
+		if (p)
+			parse_memmap_one("exactusablemap");
+	}
 
 	while (str) {
 		char *k = strchr(str, ',');

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Thomas Renninger]

On Monday, January 14, 2013 03:43:46 AM Yinghai Lu wrote:
> On Sun, Jan 13, 2013 at 6:08 PM, Thomas Renninger <trenn@suse.de> wrote:
> > On Saturday, January 12, 2013 09:07:12 AM Yinghai Lu wrote:
...
> everyone could understand it straightforward:
> exactmap:  memmap will be specified, and it should be honored without
> considering old any memmap.
> exactusablemap: will make sure only old ram range get removed, and
> specified usable ranges will become final usable
> ranges in the final memmap. so we need to remove overlapping to old
> reserved ranges.
> 
> aka: exact means EXACT ...
The naming is not my point...
Anyway after a quick talk with Alexander Graf, I guess I won't have
much of a chance: rule is rule and a boot param is a public interface
which must not change just like that (deprecation phase, etc.).

...
 
> those just some kind of improvement without considering kdump.
> because kdump/scripts already does good job to provide right exactmap
> with usable and acpi reserved areas.
No it's conceptional wrong to provide the reserved areas via memmap
while the original ones are declared already via boot loader structures.

There are store ACPI NVS memory in suspend/resume workarounds (suspend does not
fit that much for kdump, but there may be more than this and mmconf).
The reserved areas in kdump kernel should be the same than with the
original e820 table to avoid any unforseen issues.
And kdump got them already passed and should use this info.

> for mmconf, some system that range reserved in e820, and some have that in ACPI.
> and those systems will have that mmconf enabled in kdumped kernel.

 
> attached is what I like to have with exactusablemap, but maybe is not
> needed, and we can just stay with exactmap...
> 
> ps: we don't need to add e820_remove_type...
I thought this tiny loop:
+       for (i = 0; i < e820.nr_map; i++) {
+               struct e820entry *ei = &e820.map[i];
+               if (ei->type == type) {
+                       memset(ei, 0, sizeof(struct e820entry));
+                       continue;
+               }
+       }
would be easier to evaluate what it's doing (cmp to.
e820_remove_range(0, ULLONG_MAX, E820_RAM, 1);)
But I do not have a strong opinion on that.

What is this for?:
@@ -871,6 +879,11 @@ static int __init parse_memmap_one(char
 	userdef = 1;
 	if (*p == '@') {
 		start_at = memparse(p+1, &p);
+		if (exactusablemap_parsed) {
+			/* remove all range with other types */
+			e820_remove_range(start_at, mem_size,
+						 E820_RAM, 0);
+		}
 		e820_add_region(start_at, mem_size, E820_RAM);
 	} else if (*p == '#') {
 		start_at = memparse(p+1, &p);


    Thomas

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Yinghai Lu]

On Mon, Jan 14, 2013 at 7:05 AM, Thomas Renninger <trenn@suse.de> wrote:
> What is this for?:
> @@ -871,6 +879,11 @@ static int __init parse_memmap_one(char
>         userdef = 1;
>         if (*p == '@') {
>                 start_at = memparse(p+1, &p);
> +               if (exactusablemap_parsed) {
> +                       /* remove all range with other types */
> +                       e820_remove_range(start_at, mem_size,
> +                                                E820_RAM, 0);
> +               }
>                 e820_add_region(start_at, mem_size, E820_RAM);
>         } else if (*p == '#') {
>                 start_at = memparse(p+1, &p);

remove all old renges before add E820_RAM, otherwise new add E820
ranges could be ignored.

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Thomas Renninger]

On Monday, January 14, 2013 11:04:36 AM Yinghai Lu wrote:
> On Mon, Jan 14, 2013 at 7:05 AM, Thomas Renninger <trenn@suse.de> wrote:
> > What is this for?:
> > @@ -871,6 +879,11 @@ static int __init parse_memmap_one(char
> > 
> >         userdef = 1;
> >         if (*p == '@') {
> >         
> >                 start_at = memparse(p+1, &p);
> > 
> > +               if (exactusablemap_parsed) {
> > +                       /* remove all range with other types */
> > +                       e820_remove_range(start_at, mem_size,
> > +                                                E820_RAM, 0);
> > +               }
> > 
> >                 e820_add_region(start_at, mem_size, E820_RAM);
> >         
> >         } else if (*p == '#') {
> >         
> >                 start_at = memparse(p+1, &p);
> 
> remove all old renges before add E820_RAM, otherwise new add E820
> ranges could be ignored.
But this is intended?
kexec must never request reserved memory to be used as ordinary E820_RAM
by the kdump kernel.
This also reverts what exactusablemap is all about:
Keep all reserved memory ranges of the original BIOS map.

Above would again wrongly remove the mmconf and other reserved regions
if kexec passes memmap=exactuseablemap,x@y

>From what I can see the patch looks fine, but above part should
simply be left out.

   Thomas

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Yinghai Lu]

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

On Mon, Jan 14, 2013 at 4:54 PM, Thomas Renninger <trenn@suse.de> wrote:
> On Monday, January 14, 2013 11:04:36 AM Yinghai Lu wrote:
>> On Mon, Jan 14, 2013 at 7:05 AM, Thomas Renninger <trenn@suse.de> wrote:
>> > What is this for?:
>> > @@ -871,6 +879,11 @@ static int __init parse_memmap_one(char
>> >
>> >         userdef = 1;
>> >         if (*p == '@') {
>> >
>> >                 start_at = memparse(p+1, &p);
>> >
>> > +               if (exactusablemap_parsed) {
>> > +                       /* remove all range with other types */
>> > +                       e820_remove_range(start_at, mem_size,
>> > +                                                E820_RAM, 0);
>> > +               }
>> >
>> >                 e820_add_region(start_at, mem_size, E820_RAM);
>> >
>> >         } else if (*p == '#') {
>> >
>> >                 start_at = memparse(p+1, &p);
>>
>> remove all old renges before add E820_RAM, otherwise new add E820
>> ranges could be ignored.
> But this is intended?
> kexec must never request reserved memory to be used as ordinary E820_RAM
> by the kdump kernel.
> This also reverts what exactusablemap is all about:
> Keep all reserved memory ranges of the original BIOS map.
>
> Above would again wrongly remove the mmconf and other reserved regions
> if kexec passes memmap=exactuseablemap,x@y
>
> From what I can see the patch looks fine, but above part should
> simply be left out.

then, I would like to rename it to resetusablemap instead.

like attached.

Thanks

Yinghai

[-- Attachment #2: e820_resetusablemap.patch --]
[-- Type: application/octet-stream, Size: 1161 bytes --]

---
 arch/x86/kernel/e820.c |   13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

Index: linux-2.6/arch/x86/kernel/e820.c
===================================================================
--- linux-2.6.orig/arch/x86/kernel/e820.c
+++ linux-2.6/arch/x86/kernel/e820.c
@@ -845,7 +845,7 @@ static int __init parse_memmap_one(char
 	if (!p)
 		return -EINVAL;
 
-	if (!strncmp(p, "exactmap", 8)) {
+	if (!strncmp(p, "exactmap", 8) || !strncmp(p, "resetusablemap", 14)) {
 		if (exactmap_parsed)
 			return 0;
 
@@ -858,7 +858,11 @@ static int __init parse_memmap_one(char
 		 */
 		saved_max_pfn = e820_end_of_ram_pfn();
 #endif
-		e820.nr_map = 0;
+		if (!strncmp(p, "resetusablemap", 14)) {
+			/* remove all old E820_RAM ranges */
+			e820_remove_range(0, ULLONG_MAX, E820_RAM, 1);
+		} else
+			e820.nr_map = 0;
 		userdef = 1;
 		return 0;
 	}
@@ -890,6 +894,11 @@ static int __init parse_memmap_opt(char
 	p = strstr(p, "exactmap");
 	if (p)
 		parse_memmap_one("exactmap");
+	else {
+		p = strstr(boot_command_line, "resetusablemap");
+		if (p)
+			parse_memmap_one("resetusablemap");
+	}
 
 	while (str) {
 		char *k = strchr(str, ',');

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Takao Indoh]

(2013/01/08 4:09), Thomas Renninger wrote:
> On Friday, December 21, 2012 08:19:05 AM Yinghai Lu wrote:
>> On Fri, Nov 30, 2012 at 7:49 AM, MUNEDA Takahiro
>>
>> <muneda.takahiro@jp.fujitsu.com> wrote:
>>> On Tue, 27 Nov 2012 09:42:20 +0900 (JST),
>>>
>>> Takao Indoh <indou.takao@jp.fujitsu.com> wrote:
>>>> These patches reset PCIe devices at boot time to address DMA problem on
>>>> kdump with iommu. When "reset_devices" is specified, a hot reset is
>>>> triggered on each PCIe root port and downstream port to reset its
>>>> downstream endpoint.
>>
>> ThomasR, Can you check if this one help your test case about interrupt ?
>
> Sorry for the long delay...
>
> First: I cannot reproduce this myself. I get one error like:
> DRHD: handling fault status reg 2
> INTR-REMAP: Request device [[01:00.0] fault index 33
> INTR-REMAP:[fault reason 34] Present field in the IRTE entry is clear
> when a dump is written and the dump completes successfully.
>
> The other report with a specific 10G network card is that they seem
> to get an irq storm and see about 80 per second of above messages
> in the kdump kernel until things are dead.
>
> I tried the provided patches first on 2.6.32, then I verfied with 3.8-rc2
> and in both cases the disk is not detected anymore in
> reset_devices (kexec'ed/kdump) case (but things work fine without these
> patches).

So the problem that the disk is not detected was caused by exactmap
problem you guys are discussing? Or still not detected even if exactmap
problem is fixed?

Thanks,
Takao Indoh

>
> Find the relevant serial output here:
> (starting when the sysrq c(rash) got triggered until
> the disk is not found anymore.)
> lspci -nn attached:
>
> RIP  [<ffffffff813b05b1>] sysrq_handle_crash+0x11/0x20
>   RSP <ffff885f64ee1e38>
> CR2: 0000000000000000
> Initializing cgroup subsys cpuset
> Initializing cgroup subsys cpu
> Linux version 3.8.0-rc2-default+ (trenn@ett) (gcc version 4.5.1 20101208 [gcc-4_5-branch revision 13
> Command line: root=/dev/disk/by-label/ROOT-BE2 resume=/dev/disk/by-id/scsi-36d4ae52076eef40017f5c96K
> e820: BIOS-provided physical RAM map:
> BIOS-e820: [mem 0x0000000000000100-0x000000000009bfff] usable
> BIOS-e820: [mem 0x0000000000100000-0x00000000bd2effff] usable
> BIOS-e820: [mem 0x00000000bd2f0000-0x00000000bd31bfff] reserved
> BIOS-e820: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
> BIOS-e820: [mem 0x00000000bd35b000-0x00000000bfffffff] reserved
> BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
> BIOS-e820: [mem 0x00000000fe000000-0x00000000ffffffff] reserved
> BIOS-e820: [mem 0x0000000100000000-0x000000603fffffff] usable
> debug: ignoring loglevel setting.
> e820: last_pfn = 0x6040000 max_arch_pfn = 0x400000000
> NX (Execute Disable) protection: active
> e820: user-defined physical RAM map:
> user: [mem 0x0000000000000000-0x000000000009ffff] usable
> user: [mem 0x00000000070a0000-0x000000001effafff] usable
> user: [mem 0x00000000bd31c000-0x00000000bd35afff] ACPI data
> SMBIOS 2.7 present.
> DMI: Dell Inc. PowerEdge R720/0M1GCR, BIOS 0.3.35 12/15/2011
> e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
> e820: remove [mem 0x000a0000-0x000fffff] usable
> No AGP bridge found
> e820: last_pfn = 0x1effb max_arch_pfn = 0x400000000
> MTRR default type: uncachable
> MTRR fixed ranges enabled:
>    00000-9FFFF write-back
>    A0000-BFFFF uncachable
>    C0000-CBFFF write-protect
>    CC000-D7FFF write-back
>    D8000-EBFFF uncachable
>    EC000-FFFFF write-protect
> MTRR variable ranges enabled:
>    0 base 000000000000 mask 3FC000000000 write-back
>    1 base 004000000000 mask 3FE000000000 write-back
>    2 base 006000000000 mask 3FFFC0000000 write-back
>    3 base 0000C0000000 mask 3FFFC0000000 uncachable
>    4 disabled
>    5 disabled
>    6 disabled
>    7 disabled
>    8 disabled
>    9 disabled
> x86 PAT enabled: cpu 0, old 0x7010600070106, new 0x7010600070106
> e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
> found SMP MP-table at [mem 0x000fe710-0x000fe71f] mapped at [ffff8800000fe710]
> initial memory mapped: [mem 0x00000000-0x1fffffff]
> Base memory trampoline at [ffff880000096000] 96000 size 24576
> Using GB pages for direct mapping
> init_memory_mapping: [mem 0x00000000-0x1effafff]
>   [mem 0x00000000-0x1edfffff] page 2M
>   [mem 0x1ee00000-0x1effafff] page 4k
> kernel direct mapping tables up to 0x1effafff @ [mem 0x1eff8000-0x1effafff]
> log_buf_len: 4194304
> early log buf free: 258384(98%)
> RAMDISK: [mem 0x1ea3f000-0x1efeefff]
> ACPI: RSDP 00000000000f10d0 00024 (v02 DELL  )
> ACPI: XSDT 00000000000f11d4 0009C (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: FACP 00000000bd34111c 000F4 (v03 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: DSDT 00000000bd31c000 05FCD (v01 DELL   PE_SC3   00000001 INTL 20110211)
> ACPI: FACS 00000000bd343000 00040
> ACPI: APIC 00000000bd340478 0016A (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: SPCR 00000000bd3405e4 00050 (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: HPET 00000000bd340638 00038 (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: DMAR 00000000bd340674 00158 (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: MCFG 00000000bd340950 0003C (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: WD__ 00000000bd340990 00134 (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: SLIC 00000000bd340ac8 00176 (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: ERST 00000000bd322170 00270 (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: HEST 00000000bd3223e0 0055C (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: BERT 00000000bd321fd0 00030 (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: EINJ 00000000bd322000 00170 (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: SRAT 00000000bd340cf0 003C0 (v01 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: TCPA 00000000bd3410b4 00064 (v02 DELL   PE_SC3   00000001 DELL 00000001)
> ACPI: SSDT 00000000bd344000 0AA14 (v01 INTEL  PPM RCM  80000001 INTL 20061109)
> ACPI: Local APIC address 0xfee00000
> SRAT: PXM 1 -> APIC 0x00 -> Node 0
> SRAT: PXM 2 -> APIC 0x20 -> Node 1
> SRAT: PXM 1 -> APIC 0x02 -> Node 0
> SRAT: PXM 2 -> APIC 0x22 -> Node 1
> SRAT: PXM 1 -> APIC 0x04 -> Node 0
> SRAT: PXM 2 -> APIC 0x24 -> Node 1
> SRAT: PXM 1 -> APIC 0x06 -> Node 0
> SRAT: PXM 2 -> APIC 0x26 -> Node 1
> SRAT: PXM 1 -> APIC 0x08 -> Node 0
> SRAT: PXM 2 -> APIC 0x28 -> Node 1
> SRAT: PXM 1 -> APIC 0x0a -> Node 0
> SRAT: PXM 2 -> APIC 0x2a -> Node 1
> SRAT: PXM 1 -> APIC 0x0c -> Node 0
> SRAT: PXM 2 -> APIC 0x2c -> Node 1
> SRAT: PXM 1 -> APIC 0x0e -> Node 0
> SRAT: PXM 2 -> APIC 0x2e -> Node 1
> SRAT: PXM 1 -> APIC 0x01 -> Node 0
> SRAT: PXM 2 -> APIC 0x21 -> Node 1
> SRAT: PXM 1 -> APIC 0x03 -> Node 0
> SRAT: PXM 2 -> APIC 0x23 -> Node 1
> SRAT: PXM 1 -> APIC 0x05 -> Node 0
> SRAT: PXM 2 -> APIC 0x25 -> Node 1
> SRAT: PXM 1 -> APIC 0x07 -> Node 0
> SRAT: PXM 2 -> APIC 0x27 -> Node 1
> SRAT: PXM 1 -> APIC 0x09 -> Node 0
> SRAT: PXM 2 -> APIC 0x29 -> Node 1
> SRAT: PXM 1 -> APIC 0x0b -> Node 0
> SRAT: PXM 2 -> APIC 0x2b -> Node 1
> SRAT: PXM 1 -> APIC 0x0d -> Node 0
> SRAT: PXM 2 -> APIC 0x2d -> Node 1
> SRAT: PXM 1 -> APIC 0x0f -> Node 0
> SRAT: PXM 2 -> APIC 0x2f -> Node 1
> SRAT: Node 0 PXM 1 [mem 0x00000000-0x303fffffff]
> SRAT: Node 1 PXM 2 [mem 0x3040000000-0x603fffffff]
> Initmem setup node 0 [mem 0x00000000-0x1effafff]
>    NODE_DATA [mem 0x1e62b000-0x1e63efff]
>   [ffffea0000000000-ffffea00007fffff] PMD -> [ffff88001d600000-ffff88001ddfffff] on node 0
> Zone ranges:
>    DMA      [mem 0x00010000-0x00ffffff]
>    DMA32    [mem 0x01000000-0xffffffff]
>    Normal   empty
> Movable zone start for each node
> Early memory node ranges
>    node   0: [mem 0x00010000-0x0009ffff]
>    node   0: [mem 0x070a0000-0x1effafff]
> On node 0 totalpages: 98283
>    DMA zone: 3 pages used for memmap
>    DMA zone: 10 pages reserved
>    DMA zone: 131 pages, LIFO batch:0
>    DMA32 zone: 1534 pages used for memmap
>    DMA32 zone: 96605 pages, LIFO batch:31
> pci 0000:01:00.0 save state
> pci 0000:01:00.1 save state
> pci 0000:01:00.2 save state
> pci 0000:01:00.3 save state
> pci 0000:02:00.0 save state
> pci 0000:05:00.0 save state
> pci 0000:48:00.0 save state
> pci 0000:48:00.1 save state
> pci 0000:44:00.0 save state
> pci 0000:45:00.0 save state
> pci 0000:46:00.0 save state
> pci 0000:47:00.0 save state
> pci 0000:00:01.0 reset
> pci 0000:00:02.2 reset
> pci 0000:00:03.2 reset
> pci 0000:40:02.0 reset
> pci 0000:42:05.0 reset
> pci 0000:42:06.0 reset
> pci 0000:42:08.0 reset
> pci 0000:42:09.0 reset
> pci 0000:01:00.0 restore state
> pci 0000:01:00.1 restore state
> pci 0000:01:00.2 restore state
> pci 0000:01:00.3 restore state
> pci 0000:02:00.0 restore state
> pci 0000:05:00.0 restore state
> pci 0000:48:00.0 restore state
> pci 0000:48:00.1 restore state
> pci 0000:44:00.0 restore state
> pci 0000:45:00.0 restore state
> pci 0000:46:00.0 restore state
> pci 0000:47:00.0 restore state
> ACPI: PM-Timer IO Port: 0x808
> ACPI: Local APIC address 0xfee00000
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x20] enabled)
> ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
> ACPI: LAPIC (acpi_id[0x04] lapic_id[0x22] enabled)
> ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
> ACPI: LAPIC (acpi_id[0x06] lapic_id[0x24] enabled)
> ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] enabled)
> ACPI: LAPIC (acpi_id[0x08] lapic_id[0x26] enabled)
> ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] enabled)
> ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x28] enabled)
> ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] enabled)
> ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2a] enabled)
> ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] enabled)
> ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2c] enabled)
> ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] enabled)
> ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2e] enabled)
> ACPI: LAPIC (acpi_id[0x11] lapic_id[0x01] enabled)
> ACPI: LAPIC (acpi_id[0x12] lapic_id[0x21] enabled)
> ACPI: LAPIC (acpi_id[0x13] lapic_id[0x03] enabled)
> ACPI: LAPIC (acpi_id[0x14] lapic_id[0x23] enabled)
> ACPI: LAPIC (acpi_id[0x15] lapic_id[0x05] enabled)
> ACPI: LAPIC (acpi_id[0x16] lapic_id[0x25] enabled)
> ACPI: LAPIC (acpi_id[0x17] lapic_id[0x07] enabled)
> ACPI: LAPIC (acpi_id[0x18] lapic_id[0x27] enabled)
> ACPI: LAPIC (acpi_id[0x19] lapic_id[0x09] enabled)
> ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x29] enabled)
> ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x0b] enabled)
> ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x2b] enabled)
> ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x0d] enabled)
> ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x2d] enabled)
> ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x0f] enabled)
> ACPI: LAPIC (acpi_id[0x20] lapic_id[0x2f] enabled)
> ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
> ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
> ACPI: IOAPIC (id[0x01] address[0xfec3f000] gsi_base[32])
> IOAPIC[1]: apic_id 1, version 32, address 0xfec3f000, GSI 32-55
> ACPI: IOAPIC (id[0x02] address[0xfec7f000] gsi_base[64])
> IOAPIC[2]: apic_id 2, version 32, address 0xfec7f000, GSI 64-87
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> ACPI: IRQ0 used by override.
> ACPI: IRQ2 used by override.
> ACPI: IRQ9 used by override.
> Using ACPI (MADT) for SMP configuration information
> ACPI: HPET id: 0x8086a701 base: 0xfed00000
> smpboot: Allowing 32 CPUs, 0 hotplug CPUs
> nr_irqs_gsi: 104
> PM: Registered nosave memory: 00000000000a0000 - 00000000070a0000
> e820: [mem 0x1effb000-0xbd31bfff] available for PCI devices
> Booting paravirtualized kernel on bare hardware
> setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:32 nr_node_ids:2
> PERCPU: Embedded 27 pages/cpu @ffff88001e000000 s81728 r8192 d20672 u131072
> pcpu-alloc: s81728 r8192 d20672 u131072 alloc=1*2097152
> pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
> pcpu-alloc: [0] 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
> Built 1 zonelists in Node order, mobility grouping on.  Total pages: 96736
> Policy zone: DMA32
> Kernel command line: root=/dev/disk/by-label/ROOT-BE2 resume=/dev/disk/by-id/scsi-36d4ae52076eef400K
> Disabling memory control group subsystem
> Misrouted IRQ fixup and polling support enabled
> This may significantly impact system performance
> PID hash table entries: 2048 (order: 2, 16384 bytes)
> __ex_table already sorted, skipping sort
> xsave: enabled xstate_bv 0x7, cntxt size 0x340
> Checking aperture...
> No AGP bridge found
> Memory: 357688k/507884k available (5832k kernel code, 114752k absent, 35444k reserved, 5095k data, )
> Hierarchical RCU implementation.
>          RCU dyntick-idle grace-period acceleration is enabled.
>          RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=32.
> NR_IRQS:33024 nr_irqs:2024 16
> Extended CMOS year: 2000
> Spurious LAPIC timer interrupt on cpu 0
> do_IRQ: 0.47 No irq handler for vector (irq -1)
> Console: colour VGA+ 80x25
> console [tty0] enabled
> console [ttyS0] enabled
> Enabling automatic NUMA balancing. Configure with numa_balancing= or sysctl
> hpet clockevent registered
> tsc: Fast TSC calibration using PIT
> tsc: Detected 2699.982 MHz processor
> Calibrating delay loop (skipped), value calculated using timer frequency.. 5399.96 BogoMIPS (lpj=10)
> pid_max: default: 32768 minimum: 301
> Security Framework initialized
> AppArmor: AppArmor initialized
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Mount-cache hash table entries: 256
> Initializing cgroup subsys cpuacct
> Initializing cgroup subsys memory
> Initializing cgroup subsys devices
> Initializing cgroup subsys freezer
> Initializing cgroup subsys net_cls
> Initializing cgroup subsys blkio
> Initializing cgroup subsys perf_event
> Initializing cgroup subsys hugetlb
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> mce: CPU supports 20 MCE banks
> CPU0: Thermal LVT vector (0xfa) already installed
> process: using mwait in idle threads
> Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0
> Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32
> tlb_flushall_shift: 5
> ACPI: Core revision 20121018
> dmar: Host address width 46
> dmar: DRHD base: 0x000000d0d00000 flags: 0x0
> dmar: IOMMU 0: reg_base_addr d0d00000 ver 1:0 cap d2078c106f0462 ecap f020fe
> dmar: DRHD base: 0x000000dc900000 flags: 0x1
> dmar: IOMMU 1: reg_base_addr dc900000 ver 1:0 cap d2078c106f0462 ecap f020fe
> dmar: RMRR base: 0x000000bf458000 end: 0x000000bf46ffff
> dmar: RMRR base: 0x000000bf450000 end: 0x000000bf450fff
> dmar: RMRR base: 0x000000bf452000 end: 0x000000bf452fff
> dmar: ATSR flags: 0x0
> IOAPIC id 2 under DRHD base  0xd0d00000 IOMMU 0
> IOAPIC id 0 under DRHD base  0xdc900000 IOMMU 1
> IOAPIC id 1 under DRHD base  0xdc900000 IOMMU 1
> HPET id 0 under DRHD base 0xdc900000
> ------------[ cut here ]------------
> WARNING: at drivers/iommu/intel_irq_remapping.c:542 intel_enable_irq_remapping+0x7d/0x26f()
> Hardware name: PowerEdge R720
> Your BIOS is broken and requested that x2apic be disabled
> This will leave your machine vulnerable to irq-injection attacks
> Use 'intremap=no_x2apic_optout' to override BIOS request
> Modules linked in:
> Pid: 1, comm: swapper/0 Not tainted 3.8.0-rc2-default+ #4
> Call Trace:
>   [<ffffffff81047e2a>] warn_slowpath_common+0x7a/0xb0
>   [<ffffffff81047f01>] warn_slowpath_fmt+0x41/0x50
>   [<ffffffff81afe7ac>] intel_enable_irq_remapping+0x7d/0x26f
>   [<ffffffff81afeaf0>] irq_remapping_enable+0x20/0x22
>   [<ffffffff81acf048>] enable_IR+0x5d/0x65
>   [<ffffffff81acf334>] enable_IR_x2apic+0x95/0x247
>   [<ffffffff81026099>] ? cpumask_next+0x19/0x20
>   [<ffffffff8159b9b8>] ? set_cpu_sibling_map+0x405/0x422
>   [<ffffffff81026831>] ? apic_write+0x11/0x20
>   [<ffffffff81ad1e83>] default_setup_apic_routing+0x15/0x6e
>   [<ffffffff81accf43>] native_smp_prepare_cpus+0x137/0x234
>   [<ffffffff81ac1c8e>] kernel_init_freeable+0xa2/0x1e1
>   [<ffffffff815928b0>] ? rest_init+0x80/0x80
>   [<ffffffff815928b9>] kernel_init+0x9/0xf0
>   [<ffffffff815ae5bc>] ret_from_fork+0x7c/0xb0
>   [<ffffffff815928b0>] ? rest_init+0x80/0x80
> ---[ end trace 5046c9e3737e7b93 ]---
> Enabled IRQ remapping in xapic mode
> x2apic not enabled, IRQ remapping is in xapic mode
> Switched APIC routing to physical flat.
> ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> smpboot: CPU0: Genuine Intel(R) CPU  @ 2.70GHz (fam: 06, model: 2d, stepping: 05)
> TSC deadline timer enabled
> Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, Intel PMU driver.
> perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode
> ... version:                3
> ... bit width:              48
> ... generic registers:      4
> ... value mask:             0000ffffffffffff
> ... max period:             000000007fffffff
> ... fixed-purpose events:   3
> ... event mask:             000000070000000f
> Brought up 1 CPUs
> smpboot: Total of 1 processors activated (5399.96 BogoMIPS)
> devtmpfs: initialized
> RTC time: 17:51:12, date: 01/07/13
> NET: Registered protocol family 16
> ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
> ACPI: bus type pci registered
> PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
> PCI: not using MMCONFIG
> PCI: Using configuration type 1 for base access
> PCI: Dell System detected, enabling pci=bfsort.
> bio: create slab <bio-0> at 0
> ACPI: Added _OSI(Module Device)
> ACPI: Added _OSI(Processor Device)
> ACPI: Added _OSI(3.0 _SCP Extensions)
> ACPI: Added _OSI(Processor Aggregator Device)
> ACPI: EC: Look up EC in DSDT
> [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
> ACPI: Interpreter enabled
> ACPI: (supports S0 S4 S5)
> ACPI: Using IOAPIC for interrupt routing
> PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
> PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
> PCI: MMCONFIG for 0000 [bus00-1f] at [mem 0xe0000000-0xe1ffffff] (base 0xe0000000) (size reduced!)
> ACPI: No dock devices found.
> HEST: Table parsing has been initialized.
> PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
> ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3d])
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> pci_root PNP0A08:00: Requesting ACPI _OSC control (0x15)
> pci_root PNP0A08:00: ACPI _OSC control (0x15) granted
> pci_root PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-1f] only partially covers the
> PCI host bridge to bus 0000:00
> pci_bus 0000:00: root bus resource [bus 00-3d]
> pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
> pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
> pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
> pci_bus 0000:00: root bus resource [io  0x0d00-0x1fff]
> pci_bus 0000:00: root bus resource [io  0x8000-0x9fff]
> pci_bus 0000:00: root bus resource [io  0xa000-0xbfff]
> pci_bus 0000:00: root bus resource [io  0xc000-0xdfff]
> pci_bus 0000:00: root bus resource [io  0xe000-0xffff]
> pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
> pci_bus 0000:00: root bus resource [mem 0xd4000000-0xdfffffff]
> pci_bus 0000:00: root bus resource [mem 0xfed10000-0xfed103ff]
> pci_bus 0000:00: root bus resource [mem 0xfed11000-0xfed113ff]
> pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff]
> pci 0000:00:00.0: [8086:3c00] type 00 class 0x060000
> pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:01.0: [8086:3c02] type 01 class 0x060400
> pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:02.0: [8086:3c04] type 01 class 0x060400
> pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:02.2: [8086:3c06] type 01 class 0x060400
> pci 0000:00:02.2: PME# supported from D0 D3hot D3cold
> pci 0000:00:03.0: [8086:3c08] type 01 class 0x060400
> pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:03.2: [8086:3c0a] type 01 class 0x060400
> pci 0000:00:03.2: PME# supported from D0 D3hot D3cold
> pci 0000:00:05.0: [8086:3c28] type 00 class 0x088000
> pci 0000:00:05.2: [8086:3c2a] type 00 class 0x088000
> pci 0000:00:11.0: [8086:1d3e] type 01 class 0x060400
> pci 0000:00:11.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:16.0: [8086:1d3a] type 00 class 0x078000
> pci 0000:00:16.0: reg 10: [mem 0xfed10000-0xfed1000f 64bit]
> pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:16.1: [8086:1d3b] type 00 class 0x078000
> pci 0000:00:16.1: reg 10: [mem 0xfed11000-0xfed1100f 64bit]
> pci 0000:00:16.1: PME# supported from D0 D3hot D3cold
> pci 0000:00:1a.0: [8086:1d2d] type 00 class 0x0c0320
> pci 0000:00:1a.0: reg 10: [mem 0xdc8fd000-0xdc8fd3ff]
> pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:1c.0: [8086:1d10] type 01 class 0x060400
> pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:1c.7: [8086:1d1e] type 01 class 0x060400
> pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
> pci 0000:00:1d.0: [8086:1d26] type 00 class 0x0c0320
> pci 0000:00:1d.0: reg 10: [mem 0xdc8fe000-0xdc8fe3ff]
> pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
> pci 0000:00:1f.0: [8086:1d41] type 00 class 0x060100
> pci 0000:00:1f.2: [8086:1d02] type 00 class 0x010601
> pci 0000:00:1f.2: reg 10: [io  0xcce8-0xccef]
> pci 0000:00:1f.2: reg 14: [io  0xccf8-0xccfb]
> pci 0000:00:1f.2: reg 18: [io  0xccf0-0xccf7]
> pci 0000:00:1f.2: reg 1c: [io  0xccfc-0xccff]
> pci 0000:00:1f.2: reg 20: [io  0xccc0-0xccdf]
> pci 0000:00:1f.2: reg 24: [mem 0xdc8ff000-0xdc8ff7ff]
> pci 0000:00:1f.2: PME# supported from D3hot
> pci 0000:01:00.0: [8086:1521] type 00 class 0x020000
> pci 0000:01:00.0: reg 10: [mem 0xd8b00000-0xd8bfffff]
> pci 0000:01:00.0: reg 18: [io  0xfc80-0xfc9f]
> pci 0000:01:00.0: reg 1c: [mem 0xd8ff0000-0xd8ff3fff]
> pci 0000:01:00.0: reg 30: [mem 0xd8000000-0xd807ffff pref]
> pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
> pci 0000:01:00.1: [8086:1521] type 00 class 0x020000
> pci 0000:01:00.1: reg 10: [mem 0xd8c00000-0xd8cfffff]
> pci 0000:01:00.1: reg 18: [io  0xfca0-0xfcbf]
> pci 0000:01:00.1: reg 1c: [mem 0xd8ff4000-0xd8ff7fff]
> pci 0000:01:00.1: reg 30: [mem 0xd8000000-0xd807ffff pref]
> pci 0000:01:00.1: PME# supported from D0 D3hot D3cold
> pci 0000:01:00.2: [8086:1521] type 00 class 0x020000
> pci 0000:01:00.2: reg 10: [mem 0xd8d00000-0xd8dfffff]
> pci 0000:01:00.2: reg 18: [io  0xfcc0-0xfcdf]
> pci 0000:01:00.2: reg 1c: [mem 0xd8ff8000-0xd8ffbfff]
> pci 0000:01:00.2: reg 30: [mem 0xd8000000-0xd807ffff pref]
> pci 0000:01:00.2: PME# supported from D0 D3hot D3cold
> pci 0000:01:00.3: [8086:1521] type 00 class 0x020000
> pci 0000:01:00.3: reg 10: [mem 0xd8e00000-0xd8efffff]
> pci 0000:01:00.3: reg 18: [io  0xfce0-0xfcff]
> pci 0000:01:00.3: reg 1c: [mem 0xd8ffc000-0xd8ffffff]
> pci 0000:01:00.3: reg 30: [mem 0xd8000000-0xd807ffff pref]
> pci 0000:01:00.3: PME# supported from D0 D3hot D3cold
> pci 0000:00:01.0: PCI bridge to [bus 01]
> pci 0000:00:01.0:   bridge window [io  0xf000-0xffff]
> pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xd8ffffff]
> pci 0000:00:01.0:   bridge window [mem 0xd5000000-0xd51fffff 64bit pref]
> pci 0000:00:02.0: PCI bridge to [bus 03]
> pci 0000:00:02.2: PCI bridge to [bus 02]
> pci 0000:00:02.2:   bridge window [io  0xe000-0xefff]
> pci 0000:00:02.2:   bridge window [mem 0xd9000000-0xd9ffffff]
> pci 0000:00:03.0: PCI bridge to [bus 04]
> pci 0000:05:00.0: [1000:0064] type 00 class 0x010700
> pci 0000:05:00.0: reg 10: [io  0xdc00-0xdcff]
> pci 0000:05:00.0: reg 14: [mem 0xdaffc000-0xdaffffff 64bit]
> pci 0000:05:00.0: reg 1c: [mem 0xdaf80000-0xdafbffff 64bit]
> pci 0000:05:00.0: reg 30: [mem 0xda000000-0xda07ffff pref]
> pci 0000:05:00.0: supports D1 D2
> pci 0000:00:03.2: PCI bridge to [bus 05]
> pci 0000:00:03.2:   bridge window [io  0xd000-0xdfff]
> pci 0000:00:03.2:   bridge window [mem 0xda000000-0xdaffffff]
> pci 0000:00:11.0: PCI bridge to [bus 06]
> pci 0000:00:1c.0: PCI bridge to [bus 07]
> pci 0000:08:00.0: [1912:0013] type 01 class 0x060400
> pci 0000:08:00.0: PME# supported from D0 D3hot D3cold
> pci 0000:00:1c.7: PCI bridge to [bus 08-0c]
> pci 0000:00:1c.7:   bridge window [mem 0xdb000000-0xdc7fffff]
> pci 0000:00:1c.7:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci 0000:09:00.0: [1912:0013] type 01 class 0x060400
> pci 0000:09:00.0: PME# supported from D0 D3hot D3cold
> pci 0000:09:01.0: [1912:0013] type 01 class 0x060400
> pci 0000:09:01.0: PME# supported from D0 D3hot D3cold
> pci 0000:08:00.0: PCI bridge to [bus 09-0c]
> pci 0000:08:00.0:   bridge window [mem 0xdb000000-0xdc7fffff]
> pci 0000:08:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci 0000:0a:00.0: [1912:0012] type 01 class 0x060400
> pci 0000:09:00.0: PCI bridge to [bus 0a-0b]
> pci 0000:09:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
> pci 0000:09:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci 0000:0b:00.0: [102b:0534] type 00 class 0x030000
> pci 0000:0b:00.0: reg 10: [mem 0xd4000000-0xd4ffffff pref]
> pci 0000:0b:00.0: reg 14: [mem 0xdbffc000-0xdbffffff]
> pci 0000:0b:00.0: reg 18: [mem 0xdb000000-0xdb7fffff]
> pci 0000:0a:00.0: PCI bridge to [bus 0b]
> pci 0000:0a:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
> pci 0000:0a:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci 0000:09:01.0: PCI bridge to [bus 0c]
> pci 0000:09:01.0:   bridge window [mem 0xdc700000-0xdc7fffff]
> pci 0000:00:1e.0: PCI bridge to [bus 0d] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [io  0x0000-0x03af] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [io  0x03e0-0x0cf7] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [io  0x03b0-0x03df] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [io  0x0d00-0x1fff] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [io  0x8000-0x9fff] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [io  0xa000-0xbfff] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [io  0xc000-0xdfff] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [io  0xe000-0xffff] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [mem 0xd4000000-0xdfffffff] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [mem 0xfed10000-0xfed103ff] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [mem 0xfed11000-0xfed113ff] (subtractive decode)
> pci 0000:00:1e.0:   bridge window [mem 0xfed40000-0xfed44fff] (subtractive decode)
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
> ACPI: Invalid Power Resource to register!
> ACPI: Invalid Power Resource to register!
> ACPI: Invalid Power Resource to register!
> ACPI: Invalid Power Resource to register!
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT]
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX5._PRT]
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6._PRT]
> ACPI: Invalid Power Resource to register!
> ACPI: Invalid Power Resource to register!
> ACPI: Invalid Power Resource to register!
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 40-7e])
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI1._PRT]
> pci_root PNP0A08:01: Requesting ACPI _OSC control (0x15)
> pci_root PNP0A08:01: ACPI _OSC control (0x15) granted
> pci_root PNP0A08:01: fail to add MMCONFIG information, can't access extended PCI configuration spac.
> PCI host bridge to bus 0000:40
> pci_bus 0000:40: root bus resource [bus 40-7e]
> pci_bus 0000:40: root bus resource [io  0x2000-0x3fff]
> pci_bus 0000:40: root bus resource [io  0x4000-0x5fff]
> pci_bus 0000:40: root bus resource [io  0x6000-0x7fff]
> pci_bus 0000:40: root bus resource [mem 0xcc000000-0xd3ffffff]
> pci 0000:40:01.0: [8086:3c02] type 01 class 0x060400
> pci 0000:40:01.0: PME# supported from D0 D3hot D3cold
> pci 0000:40:02.0: [8086:3c04] type 01 class 0x060400
> pci 0000:40:02.0: PME# supported from D0 D3hot D3cold
> pci 0000:40:03.0: [8086:3c08] type 01 class 0x060400
> pci 0000:40:03.0: PME# supported from D0 D3hot D3cold
> pci 0000:40:03.2: [8086:3c0a] type 01 class 0x060400
> pci 0000:40:03.2: PME# supported from D0 D3hot D3cold
> pci 0000:40:05.0: [8086:3c28] type 00 class 0x088000
> pci 0000:40:05.2: [8086:3c2a] type 00 class 0x088000
> pci 0000:41:00.0: [10b5:8624] type 01 class 0x060400
> pci 0000:41:00.0: reg 10: [mem 0xd0ce0000-0xd0cfffff]
> pci 0000:41:00.0: PME# supported from D0 D3hot D3cold
> pci 0000:40:01.0: PCI bridge to [bus 41-47]
> pci 0000:40:01.0:   bridge window [io  0x2000-0x3fff]
> pci 0000:40:01.0:   bridge window [mem 0xd0800000-0xd0cfffff]
> pci 0000:40:01.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
> pci 0000:42:04.0: [10b5:8624] type 01 class 0x060400
> pci 0000:42:04.0: PME# supported from D0 D3hot D3cold
> pci 0000:42:05.0: [10b5:8624] type 01 class 0x060400
> pci 0000:42:05.0: PME# supported from D0 D3hot D3cold
> pci 0000:42:06.0: [10b5:8624] type 01 class 0x060400
> pci 0000:42:06.0: PME# supported from D0 D3hot D3cold
> pci 0000:42:08.0: [10b5:8624] type 01 class 0x060400
> pci 0000:42:08.0: PME# supported from D0 D3hot D3cold
> pci 0000:42:09.0: [10b5:8624] type 01 class 0x060400
> pci 0000:42:09.0: PME# supported from D0 D3hot D3cold
> pci 0000:41:00.0: PCI bridge to [bus 42-47]
> pci 0000:41:00.0:   bridge window [io  0x2000-0x3fff]
> pci 0000:41:00.0:   bridge window [mem 0xd0800000-0xd0bfffff]
> pci 0000:41:00.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
> pci 0000:42:04.0: PCI bridge to [bus 43]
> pci 0000:44:00.0: [13a3:0037] type 00 class 0x108000
> pci 0000:44:00.0: reg 10: [mem 0xd08ff000-0xd08fffff 64bit]
> pci 0000:44:00.0: supports D1
> pci 0000:44:00.0: PME# supported from D0 D1 D3hot
> pci 0000:42:05.0: PCI bridge to [bus 44]
> pci 0000:42:05.0:   bridge window [io  0x2000-0x2fff]
> pci 0000:42:05.0:   bridge window [mem 0xd0800000-0xd08fffff]
> pci 0000:42:05.0:   bridge window [mem 0xcc200000-0xcc3fffff 64bit pref]
> pci 0000:45:00.0: [13a3:0037] type 00 class 0x108000
> pci 0000:45:00.0: reg 10: [mem 0xd09ff000-0xd09fffff 64bit]
> pci 0000:45:00.0: supports D1
> pci 0000:45:00.0: PME# supported from D0 D1 D3hot
> pci 0000:42:06.0: PCI bridge to [bus 45]
> pci 0000:42:06.0:   bridge window [mem 0xd0900000-0xd09fffff]
> pci 0000:46:00.0: [13a3:0037] type 00 class 0x108000
> pci 0000:46:00.0: reg 10: [mem 0xd0aff000-0xd0afffff 64bit]
> pci 0000:46:00.0: supports D1
> pci 0000:46:00.0: PME# supported from D0 D1 D3hot
> pci 0000:42:08.0: PCI bridge to [bus 46]
> pci 0000:42:08.0:   bridge window [mem 0xd0a00000-0xd0afffff]
> pci 0000:47:00.0: [13a3:0037] type 00 class 0x108000
> pci 0000:47:00.0: reg 10: [mem 0xd0bff000-0xd0bfffff 64bit]
> pci 0000:47:00.0: supports D1
> pci 0000:47:00.0: PME# supported from D0 D1 D3hot
> pci 0000:42:09.0: PCI bridge to [bus 47]
> pci 0000:42:09.0:   bridge window [io  0x3000-0x3fff]
> pci 0000:42:09.0:   bridge window [mem 0xd0b00000-0xd0bfffff]
> pci 0000:42:09.0:   bridge window [mem 0xcc400000-0xcc5fffff 64bit pref]
> pci 0000:48:00.0: [8086:10fb] type 00 class 0x020000
> pci 0000:48:00.0: reg 10: [mem 0xcc080000-0xcc0fffff 64bit pref]
> pci 0000:48:00.0: reg 18: [io  0x7cc0-0x7cdf]
> pci 0000:48:00.0: reg 20: [mem 0xcc1f8000-0xcc1fbfff 64bit pref]
> pci 0000:48:00.0: reg 30: [mem 0xd0000000-0xd007ffff pref]
> pci 0000:48:00.0: PME# supported from D0 D3hot
> pci 0000:48:00.1: [8086:10fb] type 00 class 0x020000
> pci 0000:48:00.1: reg 10: [mem 0xcc100000-0xcc17ffff 64bit pref]
> pci 0000:48:00.1: reg 18: [io  0x7ce0-0x7cff]
> pci 0000:48:00.1: reg 20: [mem 0xcc1fc000-0xcc1fffff 64bit pref]
> pci 0000:48:00.1: reg 30: [mem 0xd0000000-0xd007ffff pref]
> pci 0000:48:00.1: PME# supported from D0 D3hot
> pci 0000:40:02.0: PCI bridge to [bus 48]
> pci 0000:40:02.0:   bridge window [io  0x7000-0x7fff]
> pci 0000:40:02.0:   bridge window [mem 0xd0000000-0xd07fffff]
> pci 0000:40:02.0:   bridge window [mem 0xcc000000-0xcc1fffff 64bit pref]
> pci 0000:40:03.0: PCI bridge to [bus 49]
> pci 0000:40:03.2: PCI bridge to [bus 4a]
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXB._PRT]
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXC._PRT]
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXD._PRT]
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.PEXE._PRT]
> ACPI: Invalid Power Resource to register!
> ACPI: PCI Root Bridge [P0B1] (domain 0000 [bus 3f])
> pci_root PNP0A08:02: ACPI _OSC support notification failed, disabling PCIe ASPM
> pci_root PNP0A08:02: Unable to request _OSC control (_OSC support mask: 0x08)
> pci_root PNP0A08:02: fail to add MMCONFIG information, can't access extended PCI configuration spac.
> PCI host bridge to bus 0000:3f
> pci_bus 0000:3f: root bus resource [bus 3f]
> pci 0000:3f:08.0: [8086:3c80] type 00 class 0x088000
> pci 0000:3f:09.0: [8086:3c90] type 00 class 0x088000
> pci 0000:3f:0a.0: [8086:3cc0] type 00 class 0x088000
> pci 0000:3f:0a.1: [8086:3cc1] type 00 class 0x088000
> pci 0000:3f:0a.2: [8086:3cc2] type 00 class 0x088000
> pci 0000:3f:0a.3: [8086:3cd0] type 00 class 0x088000
> pci 0000:3f:0b.0: [8086:3ce0] type 00 class 0x088000
> pci 0000:3f:0b.3: [8086:3ce3] type 00 class 0x088000
> pci 0000:3f:0c.0: [8086:3ce8] type 00 class 0x088000
> pci 0000:3f:0c.1: [8086:3ce8] type 00 class 0x088000
> pci 0000:3f:0c.2: [8086:3ce8] type 00 class 0x088000
> pci 0000:3f:0c.3: [8086:3ce8] type 00 class 0x088000
> pci 0000:3f:0c.6: [8086:3cf4] type 00 class 0x088000
> pci 0000:3f:0c.7: [8086:3cf6] type 00 class 0x088000
> pci 0000:3f:0d.0: [8086:3ce8] type 00 class 0x088000
> pci 0000:3f:0d.1: [8086:3ce8] type 00 class 0x088000
> pci 0000:3f:0d.2: [8086:3ce8] type 00 class 0x088000
> pci 0000:3f:0d.3: [8086:3ce8] type 00 class 0x088000
> pci 0000:3f:0d.6: [8086:3cf5] type 00 class 0x088000
> pci 0000:3f:0e.0: [8086:3ca0] type 00 class 0x088000
> pci 0000:3f:0e.1: [8086:3c46] type 00 class 0x110100
> pci 0000:3f:0f.0: [8086:3ca8] type 00 class 0x088000
> pci 0000:3f:0f.1: [8086:3c71] type 00 class 0x088000
> pci 0000:3f:0f.2: [8086:3caa] type 00 class 0x088000
> pci 0000:3f:0f.3: [8086:3cab] type 00 class 0x088000
> pci 0000:3f:0f.4: [8086:3cac] type 00 class 0x088000
> pci 0000:3f:0f.5: [8086:3cad] type 00 class 0x088000
> pci 0000:3f:0f.6: [8086:3cae] type 00 class 0x088000
> pci 0000:3f:10.0: [8086:3cb0] type 00 class 0x088000
> pci 0000:3f:10.1: [8086:3cb1] type 00 class 0x088000
> pci 0000:3f:10.2: [8086:3cb2] type 00 class 0x088000
> pci 0000:3f:10.3: [8086:3cb3] type 00 class 0x088000
> pci 0000:3f:10.4: [8086:3cb4] type 00 class 0x088000
> pci 0000:3f:10.5: [8086:3cb5] type 00 class 0x088000
> pci 0000:3f:10.6: [8086:3cb6] type 00 class 0x088000
> pci 0000:3f:10.7: [8086:3cb7] type 00 class 0x088000
> pci 0000:3f:11.0: [8086:3cb8] type 00 class 0x088000
> pci 0000:3f:13.0: [8086:3ce4] type 00 class 0x088000
> pci 0000:3f:13.1: [8086:3c43] type 00 class 0x110100
> pci 0000:3f:13.4: [8086:3ce6] type 00 class 0x110100
> pci 0000:3f:13.5: [8086:3c44] type 00 class 0x110100
> pci 0000:3f:13.6: [8086:3c45] type 00 class 0x088000
> ACPI: Invalid Power Resource to register!
> ACPI _OSC control for PCIe not granted, disabling ASPM
> ACPI: PCI Interrupt Link [LK00] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
> ACPI: PCI Interrupt Link [LK01] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
> ACPI: PCI Interrupt Link [LK02] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
> ACPI: PCI Interrupt Link [LK03] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
> ACPI: PCI Interrupt Link [LK04] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
> ACPI: PCI Interrupt Link [LK05] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
> ACPI: PCI Interrupt Link [LK06] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
> ACPI: PCI Interrupt Link [LK07] (IRQs 3 4 5 6 7 11 14 15) *0, disabled.
> vgaarb: device added: PCI:0000:0b:00.0,decodes=io+mem,owns=io+mem,locks=none
> vgaarb: loaded
> vgaarb: bridge control possible 0000:0b:00.0
> SCSI subsystem initialized
> ACPI: bus type scsi registered
> libata version 3.00 loaded.
> PCI: Using ACPI for IRQ routing
> PCI: pci_cache_line_size set to 64 bytes
> e820: reserve RAM buffer [mem 0x1effb000-0x1fffffff]
> NetLabel: Initializing
> NetLabel:  domain hash size = 128
> NetLabel:  protocols = UNLABELED CIPSOv4
> NetLabel:  unlabeled traffic allowed by default
> hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
> hpet0: 8 comparators, 64-bit 14.318180 MHz counter
> Switching to clocksource hpet
> AppArmor: AppArmor Filesystem Enabled
> pnp: PnP ACPI init
> ACPI: bus type pnp registered
> pnp 00:00: [dma 4]
> pnp 00:00: Plug and Play ACPI device, IDs PNP0200 (active)
> pnp 00:01: Plug and Play ACPI device, IDs PNP0c04 (active)
> system 00:02: Plug and Play ACPI device, IDs PNP0c01 (active)
> pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
> pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)
> pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active)
> system 00:06: [io  0x0800-0x087f] has been reserved
> system 00:06: [io  0x0880-0x08ff] has been reserved
> system 00:06: [io  0x0900-0x091f] has been reserved
> system 00:06: [io  0x0920-0x0923] has been reserved
> system 00:06: [io  0x0924] has been reserved
> system 00:06: [io  0x0370-0x0377] has been reserved
> system 00:06: [io  0x0ca0-0x0ca7] has been reserved
> system 00:06: [io  0x0ca9-0x0cab] has been reserved
> system 00:06: [io  0x0cad-0x0caf] has been reserved
> system 00:06: [io  0x0cb0-0x0cbf] has been reserved
> system 00:06: Plug and Play ACPI device, IDs PNP0c01 (active)
> system 00:07: [io  0x0ca8] has been reserved
> system 00:07: [io  0x0cac] has been reserved
> system 00:07: Plug and Play ACPI device, IDs IPI0001 PNP0c01 (active)
> system 00:08: [mem 0xe0000000-0xe3efffff] has been reserved
> system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
> system 00:09: [mem 0xe4000000-0xe7ffffff] has been reserved
> system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
> system 00:0a: [mem 0xe3f00000-0xe3ffffff] has been reserved
> system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
> system 00:0b: [mem 0xdc900000-0xdc901fff] could not be reserved
> system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
> system 00:0c: [mem 0xd0d00000-0xd0d01fff] could not be reserved
> system 00:0c: Plug and Play ACPI device, IDs PNP0c02 (active)
> pnp: PnP ACPI: found 13 devices
> ACPI: ACPI bus type pnp unregistered
> pci 0000:01:00.1: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:]
> pci 0000:01:00.2: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:]
> pci 0000:01:00.3: address space collision: [mem 0xd8000000-0xd807ffff pref] conflicts with 0000:01:]
> pci 0000:48:00.1: address space collision: [mem 0xd0000000-0xd007ffff pref] conflicts with 0000:48:]
> pci 0000:01:00.1: BAR 6: assigned [mem 0xd5000000-0xd507ffff pref]
> pci 0000:01:00.2: BAR 6: assigned [mem 0xd5080000-0xd50fffff pref]
> pci 0000:01:00.3: BAR 6: assigned [mem 0xd5100000-0xd517ffff pref]
> pci 0000:00:01.0: PCI bridge to [bus 01]
> pci 0000:00:01.0:   bridge window [io  0xf000-0xffff]
> pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xd8ffffff]
> pci 0000:00:01.0:   bridge window [mem 0xd5000000-0xd51fffff 64bit pref]
> pci 0000:00:02.0: PCI bridge to [bus 03]
> pci 0000:00:02.2: PCI bridge to [bus 02]
> pci 0000:00:02.2:   bridge window [io  0xe000-0xefff]
> pci 0000:00:02.2:   bridge window [mem 0xd9000000-0xd9ffffff]
> pci 0000:00:03.0: PCI bridge to [bus 04]
> pci 0000:00:03.2: PCI bridge to [bus 05]
> pci 0000:00:03.2:   bridge window [io  0xd000-0xdfff]
> pci 0000:00:03.2:   bridge window [mem 0xda000000-0xdaffffff]
> pci 0000:00:11.0: PCI bridge to [bus 06]
> pci 0000:00:1c.0: PCI bridge to [bus 07]
> pci 0000:0a:00.0: PCI bridge to [bus 0b]
> pci 0000:0a:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
> pci 0000:0a:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci 0000:09:00.0: PCI bridge to [bus 0a-0b]
> pci 0000:09:00.0:   bridge window [mem 0xdb000000-0xdbffffff]
> pci 0000:09:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci 0000:09:01.0: PCI bridge to [bus 0c]
> pci 0000:09:01.0:   bridge window [mem 0xdc700000-0xdc7fffff]
> pci 0000:08:00.0: PCI bridge to [bus 09-0c]
> pci 0000:08:00.0:   bridge window [mem 0xdb000000-0xdc7fffff]
> pci 0000:08:00.0:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci 0000:00:1c.7: PCI bridge to [bus 08-0c]
> pci 0000:00:1c.7:   bridge window [mem 0xdb000000-0xdc7fffff]
> pci 0000:00:1c.7:   bridge window [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci 0000:00:1e.0: PCI bridge to [bus 0d]
> pci 0000:42:04.0: PCI bridge to [bus 43]
> pci 0000:42:05.0: PCI bridge to [bus 44]
> pci 0000:42:05.0:   bridge window [io  0x2000-0x2fff]
> pci 0000:42:05.0:   bridge window [mem 0xd0800000-0xd08fffff]
> pci 0000:42:05.0:   bridge window [mem 0xcc200000-0xcc3fffff 64bit pref]
> pci 0000:42:06.0: PCI bridge to [bus 45]
> pci 0000:42:06.0:   bridge window [mem 0xd0900000-0xd09fffff]
> pci 0000:42:08.0: PCI bridge to [bus 46]
> pci 0000:42:08.0:   bridge window [mem 0xd0a00000-0xd0afffff]
> pci 0000:42:09.0: PCI bridge to [bus 47]
> pci 0000:42:09.0:   bridge window [io  0x3000-0x3fff]
> pci 0000:42:09.0:   bridge window [mem 0xd0b00000-0xd0bfffff]
> pci 0000:42:09.0:   bridge window [mem 0xcc400000-0xcc5fffff 64bit pref]
> pci 0000:41:00.0: PCI bridge to [bus 42-47]
> pci 0000:41:00.0:   bridge window [io  0x2000-0x3fff]
> pci 0000:41:00.0:   bridge window [mem 0xd0800000-0xd0bfffff]
> pci 0000:41:00.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
> pci 0000:40:01.0: PCI bridge to [bus 41-47]
> pci 0000:40:01.0:   bridge window [io  0x2000-0x3fff]
> pci 0000:40:01.0:   bridge window [mem 0xd0800000-0xd0cfffff]
> pci 0000:40:01.0:   bridge window [mem 0xcc200000-0xcc5fffff 64bit pref]
> pci 0000:48:00.1: BAR 6: assigned [mem 0xcc000000-0xcc07ffff pref]
> pci 0000:40:02.0: PCI bridge to [bus 48]
> pci 0000:40:02.0:   bridge window [io  0x7000-0x7fff]
> pci 0000:40:02.0:   bridge window [mem 0xd0000000-0xd07fffff]
> pci 0000:40:02.0:   bridge window [mem 0xcc000000-0xcc1fffff 64bit pref]
> pci 0000:40:03.0: PCI bridge to [bus 49]
> pci 0000:40:03.2: PCI bridge to [bus 4a]
> pci 0000:00:1e.0: setting latency timer to 64
> pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
> pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
> pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
> pci_bus 0000:00: resource 7 [io  0x0d00-0x1fff]
> pci_bus 0000:00: resource 8 [io  0x8000-0x9fff]
> pci_bus 0000:00: resource 9 [io  0xa000-0xbfff]
> pci_bus 0000:00: resource 10 [io  0xc000-0xdfff]
> pci_bus 0000:00: resource 11 [io  0xe000-0xffff]
> pci_bus 0000:00: resource 12 [mem 0x000a0000-0x000bffff]
> pci_bus 0000:00: resource 13 [mem 0xd4000000-0xdfffffff]
> pci_bus 0000:00: resource 14 [mem 0xfed10000-0xfed103ff]
> pci_bus 0000:00: resource 15 [mem 0xfed11000-0xfed113ff]
> pci_bus 0000:00: resource 16 [mem 0xfed40000-0xfed44fff]
> pci_bus 0000:01: resource 0 [io  0xf000-0xffff]
> pci_bus 0000:01: resource 1 [mem 0xd8000000-0xd8ffffff]
> pci_bus 0000:01: resource 2 [mem 0xd5000000-0xd51fffff 64bit pref]
> pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
> pci_bus 0000:02: resource 1 [mem 0xd9000000-0xd9ffffff]
> pci_bus 0000:05: resource 0 [io  0xd000-0xdfff]
> pci_bus 0000:05: resource 1 [mem 0xda000000-0xdaffffff]
> pci_bus 0000:08: resource 1 [mem 0xdb000000-0xdc7fffff]
> pci_bus 0000:08: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci_bus 0000:09: resource 1 [mem 0xdb000000-0xdc7fffff]
> pci_bus 0000:09: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci_bus 0000:0a: resource 1 [mem 0xdb000000-0xdbffffff]
> pci_bus 0000:0a: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci_bus 0000:0b: resource 1 [mem 0xdb000000-0xdbffffff]
> pci_bus 0000:0b: resource 2 [mem 0xd4000000-0xd4ffffff 64bit pref]
> pci_bus 0000:0c: resource 1 [mem 0xdc700000-0xdc7fffff]
> pci_bus 0000:0d: resource 4 [io  0x0000-0x03af]
> pci_bus 0000:0d: resource 5 [io  0x03e0-0x0cf7]
> pci_bus 0000:0d: resource 6 [io  0x03b0-0x03df]
> pci_bus 0000:0d: resource 7 [io  0x0d00-0x1fff]
> pci_bus 0000:0d: resource 8 [io  0x8000-0x9fff]
> pci_bus 0000:0d: resource 9 [io  0xa000-0xbfff]
> pci_bus 0000:0d: resource 10 [io  0xc000-0xdfff]
> pci_bus 0000:0d: resource 11 [io  0xe000-0xffff]
> pci_bus 0000:0d: resource 12 [mem 0x000a0000-0x000bffff]
> pci_bus 0000:0d: resource 13 [mem 0xd4000000-0xdfffffff]
> pci_bus 0000:0d: resource 14 [mem 0xfed10000-0xfed103ff]
> pci_bus 0000:0d: resource 15 [mem 0xfed11000-0xfed113ff]
> pci_bus 0000:0d: resource 16 [mem 0xfed40000-0xfed44fff]
> pci_bus 0000:40: resource 4 [io  0x2000-0x3fff]
> pci_bus 0000:40: resource 5 [io  0x4000-0x5fff]
> pci_bus 0000:40: resource 6 [io  0x6000-0x7fff]
> pci_bus 0000:40: resource 7 [mem 0xcc000000-0xd3ffffff]
> pci_bus 0000:41: resource 0 [io  0x2000-0x3fff]
> pci_bus 0000:41: resource 1 [mem 0xd0800000-0xd0cfffff]
> pci_bus 0000:41: resource 2 [mem 0xcc200000-0xcc5fffff 64bit pref]
> pci_bus 0000:42: resource 0 [io  0x2000-0x3fff]
> pci_bus 0000:42: resource 1 [mem 0xd0800000-0xd0bfffff]
> pci_bus 0000:42: resource 2 [mem 0xcc200000-0xcc5fffff 64bit pref]
> pci_bus 0000:44: resource 0 [io  0x2000-0x2fff]
> pci_bus 0000:44: resource 1 [mem 0xd0800000-0xd08fffff]
> pci_bus 0000:44: resource 2 [mem 0xcc200000-0xcc3fffff 64bit pref]
> pci_bus 0000:45: resource 1 [mem 0xd0900000-0xd09fffff]
> pci_bus 0000:46: resource 1 [mem 0xd0a00000-0xd0afffff]
> pci_bus 0000:47: resource 0 [io  0x3000-0x3fff]
> pci_bus 0000:47: resource 1 [mem 0xd0b00000-0xd0bfffff]
> pci_bus 0000:47: resource 2 [mem 0xcc400000-0xcc5fffff 64bit pref]
> pci_bus 0000:48: resource 0 [io  0x7000-0x7fff]
> pci_bus 0000:48: resource 1 [mem 0xd0000000-0xd07fffff]
> pci_bus 0000:48: resource 2 [mem 0xcc000000-0xcc1fffff 64bit pref]
> NET: Registered protocol family 2
> TCP established hash table entries: 4096 (order: 4, 65536 bytes)
> TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
> TCP: Hash tables configured (established 4096 bind 4096)
> TCP: reno registered
> UDP hash table entries: 256 (order: 1, 8192 bytes)
> UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
> NET: Registered protocol family 1
> pci 0000:0b:00.0: Boot video device
> PCI: CLS 64 bytes, default 64
> Unpacking initramfs...
> Freeing initrd memory: 5824k freed
> audit: initializing netlink socket (disabled)
> type=2000 audit(1357581073.824:1): initialized
> HugeTLB registered 2 MB page size, pre-allocated 0 pages
> VFS: Disk quotas dquot_6.5.2
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> msgmni has been set to 709
> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
> io scheduler noop registered
> io scheduler deadline registered (default)
> io scheduler cfq registered
> pcieport 0000:00:01.0: irq 106 for MSI/MSI-X
> pcieport 0000:00:02.0: irq 107 for MSI/MSI-X
> pcieport 0000:00:02.2: irq 108 for MSI/MSI-X
> pcieport 0000:00:03.0: irq 109 for MSI/MSI-X
> pcieport 0000:00:03.2: irq 110 for MSI/MSI-X
> pcieport 0000:00:11.0: irq 111 for MSI/MSI-X
> pcieport 0000:00:1c.0: irq 112 for MSI/MSI-X
> pcieport 0000:00:1c.7: irq 113 for MSI/MSI-X
> pcieport 0000:40:01.0: irq 114 for MSI/MSI-X
> pcieport 0000:40:02.0: irq 115 for MSI/MSI-X
> pcieport 0000:40:03.0: irq 116 for MSI/MSI-X
> pcieport 0000:40:03.2: irq 117 for MSI/MSI-X
> pcieport 0000:42:05.0: irq 118 for MSI/MSI-X
> pcieport 0000:42:09.0: irq 119 for MSI/MSI-X
> pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
> pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
> pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
> pci 0000:01:00.2: Signaling PME through PCIe PME interrupt
> pci 0000:01:00.3: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
> pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
> pcieport 0000:00:02.2: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:00:02.2:pcie01: service driver pcie_pme loaded
> pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
> pcieport 0000:00:03.2: Signaling PME through PCIe PME interrupt
> pci 0000:05:00.0: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:00:03.2:pcie01: service driver pcie_pme loaded
> pcieport 0000:00:11.0: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:00:11.0:pcie01: service driver pcie_pme loaded
> pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
> pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
> pcieport 0000:08:00.0: Signaling PME through PCIe PME interrupt
> pcieport 0000:09:00.0: Signaling PME through PCIe PME interrupt
> pci 0000:0a:00.0: Signaling PME through PCIe PME interrupt
> pci 0000:0b:00.0: Signaling PME through PCIe PME interrupt
> pcieport 0000:09:01.0: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
> pcieport 0000:40:01.0: Signaling PME through PCIe PME interrupt
> pcieport 0000:41:00.0: Signaling PME through PCIe PME interrupt
> pcieport 0000:42:04.0: Signaling PME through PCIe PME interrupt
> pcieport 0000:42:05.0: Signaling PME through PCIe PME interrupt
> pci 0000:44:00.0: Signaling PME through PCIe PME interrupt
> pcieport 0000:42:06.0: Signaling PME through PCIe PME interrupt
> pci 0000:45:00.0: Signaling PME through PCIe PME interrupt
> pcieport 0000:42:08.0: Signaling PME through PCIe PME interrupt
> pci 0000:46:00.0: Signaling PME through PCIe PME interrupt
> pcieport 0000:42:09.0: Signaling PME through PCIe PME interrupt
> pci 0000:47:00.0: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:40:01.0:pcie01: service driver pcie_pme loaded
> pcieport 0000:40:02.0: Signaling PME through PCIe PME interrupt
> pci 0000:48:00.0: Signaling PME through PCIe PME interrupt
> pci 0000:48:00.1: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:40:02.0:pcie01: service driver pcie_pme loaded
> pcieport 0000:40:03.0: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:40:03.0:pcie01: service driver pcie_pme loaded
> pcieport 0000:40:03.2: Signaling PME through PCIe PME interrupt
> pcie_pme 0000:40:03.2:pcie01: service driver pcie_pme loaded
> intel_idle: MWAIT substates: 0x21120
> intel_idle: v0.4 model 0x2D
> intel_idle: lapic_timer_reliable_states 0xffffffff
> ERST: Error Record Serialization Table (ERST) support is initialized.
> GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
> Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled
> 00:04: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> Non-volatile memory driver v1.3
> Linux agpgart interface v0.103
> ahci 0000:00:1f.2: version 3.0
> ahci 0000:00:1f.2: irq 120 for MSI/MSI-X
> ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
> ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ems apst
> ahci 0000:00:1f.2: setting latency timer to 64
> scsi0 : ahci
> scsi1 : ahci
> scsi2 : ahci
> scsi3 : ahci
> scsi4 : ahci
> scsi5 : ahci
> ata1: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff100 irq 120
> ata2: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff180 irq 120
> ata3: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff200 irq 120
> ata4: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff280 irq 120
> ata5: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff300 irq 120
> ata6: SATA max UDMA/133 abar m2048@0xdc8ff000 port 0xdc8ff380 irq 120
> libphy: Fixed MDIO Bus: probed
> i8042: PNP: No PS/2 controller found. Probing ports directly.
> i8042: No controller found
> tsc: Refined TSC clocksource calibration: 2699.999 MHz
> Switching to clocksource tsc
> mousedev: PS/2 mouse device common for all mice
> rtc_cmos 00:03: RTC can wake from S4
> rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
> rtc0: alarms up to one day, y3k, 242 bytes nvram, hpet irqs
> cpuidle: using governor ladder
> cpuidle: using governor menu
> ledtrig-cpu: registered to indicate activity on CPUs
> EFI Variables Facility v0.08 2004-May-17
> TCP: cubic registered
> NET: Registered protocol family 10
> Key type dns_resolver registered
> PM: Checking hibernation image partition /dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-par8
> ata6: SATA link down (SStatus 0 SControl 300)
> ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata4: SATA link down (SStatus 0 SControl 300)
> ata1: SATA link down (SStatus 0 SControl 300)
> ata2: SATA link down (SStatus 0 SControl 300)
> ata3: SATA link down (SStatus 0 SControl 300)
> ata5.00: ATAPI: TEAC DVD-ROM DV-28SW, R.2A, max UDMA/100
> ata5.00: configured for UDMA/100
> scsi 4:0:0:0: CD-ROM            TEAC     DVD-ROM DV-28SW  R.2A PQ: 0 ANSI: 5
> PM: Hibernation image not present or could not be loaded.
> registered taskstats version 1
>    Magic number: 13:635:895
> rtc_cmos 00:03: setting system clock to 2013-01-07 17:51:18 UTC (1357581078)
> Freeing unused kernel memory: 1000k freed
> Write protecting the kernel read-only data: 10240k
> Freeing unused kernel memory: 300k freed
> Freeing unused kernel memory: 1500k freed
> doing fast boot
> SysRq : Changing Loglevel
> Loglevel set to 7
> megasas: 06.504.01.00-rc1 Mon. Oct. 1 17:00:00 PDT 2012
> FATAL: Module ahci not found.
> teradata-kdump: Skipping mpt2sas
> BIOS EDD facility v0.16 2004-Jun-25, 2 devices found
> FATAL: Module jbd not found.
> FATAL: Module ext3 not found.
> Creating device nodes with udev
> udevd (180): /proc/180/oom_adj is deprecated, please use /proc/180/oom_score_adj instead.
> udevd version 128 started
> mount: devpts already mounted or /dev/pts busy
> mount: according to mtab, devpts is already mounted on /dev/pts
> Boot logging started on /dev/ttyS0(/dev/console) at Mon Jan  7 12:51:19 2013
> Waiting for device /dev/disk/by-label/ROOT-BE2 to appear: ...............
>
> ....................................................................................................
> Want me to fall back to /dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-part3? (Y/n)
> Waiting for device /dev/disk/by-id/scsi-36d4ae52076eef40017f5c9690b9c848e-part3 to appear: ........h
> $
> $
>

Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case

[Thomas Renninger]

On Tuesday, January 15, 2013 05:45:43 AM Yinghai Lu wrote:
> On Mon, Jan 14, 2013 at 4:54 PM, Thomas Renninger <trenn@suse.de> wrote:
...
> > From what I can see the patch looks fine, but above part should
> > simply be left out.
> 
> then, I would like to rename it to resetusablemap instead.
> 
> like attached.

I tried this one out on linux-x86-tip tree on the mm2 branch
This one already had your patch:
x86, mm: Let "memmap=" take more entries one time
and I additionally added:
x86 e820: Check for exactmap appearance when parsing first memmap option
and the one you posted one mail earlier:
x86 e820: Introduce memmap=resetusablemap for kdump usage

I just re-posted your 2 patches also adding some kernel-parameter
documention, subject:
[PATCH 0/2] Only parse exactmap once, introduce memmap=resetusablemap

I adjusted kexec tools to identify the kernel version from the kernel
it loads.
I posted these patches separately, subject (google should find it
pretty soon):
[PATCH 0/3] Make use of new memmap= kernel parameter syntax

for those who are interested in these to:
  - make use of comma separated memmap= option
    Let "memmap=" take more entries one time
  - Do not pass unusable (ACPI or whatever reserved mem) via memmap=x#y
  - Do use memmap=resetusablemap instead of memmap=exactmap
in case the kernel to load is of version 3.9 or newer.
Otherwise there is no change.

Unfortunately I cannot see a proper way to backport this.
The only way may be to:
  - In the backported kernel inverse the condition to prefer resetusablemap
    over exactmap
  - In kexec pass both to older kernels: memmap=exactmap memmap=resetusablemap
    and all the ACPI reservation memmap= params


I tried this on a somewhat quicker booting machine with quite some more
memmap= params passed by kexec. I reset the machine hard when it started
kdump:
Copying data                       : [ 20 %]
as I expect that if it comes that far, things work. In both cases the
kernel was dumped:

kexec using new resetusablemap syntax (with kexec debug enabled):
===================================
./build/sbin/kexec -d -p /boot/vmlinuz-3.7.0-rc6-default+ --append="root=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part6 console=tty0 
console=ttyS0,57600 sysrq_always_enabled panic=100 ignore_loglevel resume=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part2 apic=verbose debug 
vga=normal elevator=deadline sysrq=yes reset_devices irqpoll maxcpus=1  " --initrd=/boot/initrd-3.7.0-rc6-default+-kdump...

Kernel release: 3.7.0-rc6-d in long format: 0x30700
...
root=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part6 console=tty0 console=ttyS0,57600 sysrq_always_enabled panic=100 ignore_loglevel 
resume=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part2 apic=verbose debug vga=normal elevator=deadline sysrq=yes reset_devices irqpoll maxcpus=1   
memmap=resetusablemap,559K@64K,261560K@638976K elfcorehdr=900536K
...
===================================

important parts of crash kernel log with new syntax:
===================================
[48023.711213] RIP  [<ffffffff812f368d>] sysrq_handle_crash+0xd/0x20
[48023.724765]  RSP <ffff88042411fe90>
[48023.732539] CR2: 0000000000000000
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.7.0-rc6-default+ (trenn@ett) (gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux) ) #2 SMP Tue Jan 22 01:43:26 
CET 2013
[    0.000000] Command line: root=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part6 console=tty0 console=ttyS0,57600 sysrq_always_enabled panic=100 
ignore_loglevel resume=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part2 apic=verbose debug vga=normal elevator=deadline sysrq=yes reset_devices 
irqpoll maxcpus=1   memmap=resetusablemap,559K@64K,261560K@638976K elfcorehdr=900536K
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000100-0x000000000009bbff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009bc00-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000b93dafff] usable
[    0.000000] BIOS-e820: [mem 0x00000000b93db000-0x00000000b9454fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000b9455000-0x00000000bb155fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bb156000-0x00000000bb166fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bb167000-0x00000000bb3d7fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bb3d8000-0x00000000bb6d8fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bb6d9000-0x00000000bd9fcfff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bd9fd000-0x00000000bdbfcfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bdbfd000-0x00000000bdcdcfff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bdcdd000-0x00000000bdde6fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bdde7000-0x00000000bde8ffff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bde90000-0x00000000bde90fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000bde91000-0x00000000bdf07fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bdf08000-0x00000000bdf08fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000bdf09000-0x00000000bdf0afff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bdf0b000-0x00000000bdf0bfff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000bdf0c000-0x00000000bdf0cfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bdf0d000-0x00000000bdf23fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000bdf24000-0x00000000bdfb0fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bdfb1000-0x00000000bdffffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000be000000-0x00000000cfffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed19000-0x00000000fed19fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ffa20000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000083fffffff] usable
[    0.000000] debug: ignoring loglevel setting.
[    0.000000] e820: last_pfn = 0x840000 max_arch_pfn = 0x400000000
[    0.000000] e820: remove [mem 0x00000000-0xfffffffffffffffe] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] e820: user-defined physical RAM map:
[    0.000000] user: [mem 0x0000000000010000-0x000000000009bbff] usable
[    0.000000] user: [mem 0x000000000009bc00-0x000000000009ffff] reserved
[    0.000000] user: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[    0.000000] user: [mem 0x0000000027000000-0x0000000036f6dfff] usable
[    0.000000] user: [mem 0x00000000b93db000-0x00000000b9454fff] ACPI data
[    0.000000] user: [mem 0x00000000bb156000-0x00000000bb166fff] reserved
[    0.000000] user: [mem 0x00000000bb3d8000-0x00000000bb6d8fff] ACPI NVS
[    0.000000] user: [mem 0x00000000bd9fd000-0x00000000bdbfcfff] ACPI NVS
[    0.000000] user: [mem 0x00000000bdcdd000-0x00000000bdde6fff] reserved
[    0.000000] user: [mem 0x00000000bdde7000-0x00000000bde8ffff] ACPI NVS
[    0.000000] user: [mem 0x00000000bde90000-0x00000000bde90fff] ACPI data
[    0.000000] user: [mem 0x00000000bde91000-0x00000000bdf07fff] ACPI NVS
[    0.000000] user: [mem 0x00000000bdf08000-0x00000000bdf08fff] ACPI data
[    0.000000] user: [mem 0x00000000bdf09000-0x00000000bdf0afff] ACPI NVS
[    0.000000] user: [mem 0x00000000bdf0b000-0x00000000bdf0bfff] ACPI data
[    0.000000] user: [mem 0x00000000bdf0c000-0x00000000bdf0cfff] ACPI NVS
[    0.000000] user: [mem 0x00000000bdf0d000-0x00000000bdf23fff] ACPI data
[    0.000000] user: [mem 0x00000000bdf24000-0x00000000bdfb0fff] ACPI NVS
[    0.000000] user: [mem 0x00000000be000000-0x00000000cfffffff] reserved
[    0.000000] user: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] user: [mem 0x00000000fed19000-0x00000000fed19fff] reserved
[    0.000000] user: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] user: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] user: [mem 0x00000000ffa20000-0x00000000ffffffff] reserved
[    0.000000] DMI 2.6 present.
...
[    2.370015] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xc0000000-0xcfffffff] (base 0xc0000000)
[    2.390823] PCI: MMCONFIG at [mem 0xc0000000-0xcfffffff] reserved in E820

===================================
===================================

kexec using old exactmap syntax (with kexec debug enabled):
===================================
./build/sbin/kexec -d -p /boot/vmlinuz-3.7.0-rc6-default+ --append="root=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part6 console=tty0 
console=ttyS0,57600 sysrq_always_enabled panic=100 ignore_loglevel resume=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part2 apic=verbose debug 
vga=normal elevator=deadline sysrq=yes reset_devices irqpoll maxcpus=1  " --initrd=/boot/initrd-3.7.0-rc6-default+-kdump

...
root=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part6 console=tty0 console=ttyS0,57600 sysrq_always_enabled panic=100 igno
re_loglevel resume=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part2 apic=verbose debug vga=normal elevator=deadline sysrq=
yes reset_devices irqpoll maxcpus=1   memmap=exactmap memmap=559K@64K memmap=261560K@638976K elfcorehdr=900536K memmap=488K#3034988K memma
p=3076K#3067744K memmap=2048K#3106804K memmap=676K#3110812K memmap=4K#3111488K memmap=476K#3111492K memmap=4K#3111968K memmap=8K#3111972K 
memmap=4K#3111980K memmap=4K#3111984K memmap=92K#3111988K memmap=564K#3112080K
===================================

important parts of crash kernel log with old syntax
(compare unnecessary memmap=x#y additions and the
resulting broken e820 user defined map):
===================================
[  856.564790] RIP  [<ffffffff812f368d>] sysrq_handle_crash+0xd/0x20
[  856.578345]  RSP <ffff880424197e90>
[  856.586124] CR2: 0000000000000000
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.7.0-rc6-default+ (trenn@ett) (gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux) ) #2 SMP Tue Jan 22 01:43:26 
CET 2013
[    0.000000] Command line: root=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part6 console=tty0 console=ttyS0,57600 sysrq_always_enabled panic=100 
ignore_loglevel resume=/dev/disk/by-id/ata-Hitachi_HDS721016CLA382_JPAB40HM2KUK6B-part2 apic=verbose debug vga=normal elevator=deadline sysrq=yes reset_devices 
irqpoll maxcpus=1   memmap=exactmap memmap=559K@64K memmap=261560K@638976K elfcorehdr=900536K memmap=488K#3034988K memmap=3076K#3067744K memmap=2048K#3106804K 
memmap=676K#3110812K memmap=4K#3111488K memmap=476K#3111492K memmap=4K#3111968K memmap=8K#3111972K memmap=4K#3111980K memmap=4K#3111984K memmap=92K#3111988K 
memmap=564K#3112080K
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000100-0x000000000009bbff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009bc00-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000b93dafff] usable
[    0.000000] BIOS-e820: [mem 0x00000000b93db000-0x00000000b9454fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000b9455000-0x00000000bb155fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bb156000-0x00000000bb166fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bb167000-0x00000000bb3d7fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bb3d8000-0x00000000bb6d8fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bb6d9000-0x00000000bd9fcfff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bd9fd000-0x00000000bdbfcfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bdbfd000-0x00000000bdcdcfff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bdcdd000-0x00000000bdde6fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bdde7000-0x00000000bde8ffff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bde90000-0x00000000bde90fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000bde91000-0x00000000bdf07fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bdf08000-0x00000000bdf08fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000bdf09000-0x00000000bdf0afff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bdf0b000-0x00000000bdf0bfff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000bdf0c000-0x00000000bdf0cfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bdf0d000-0x00000000bdf23fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000bdf24000-0x00000000bdfb0fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bdfb1000-0x00000000bdffffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000be000000-0x00000000cfffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed19000-0x00000000fed19fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ffa20000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000083fffffff] usable
[    0.000000] debug: ignoring loglevel setting.
[    0.000000] e820: last_pfn = 0x840000 max_arch_pfn = 0x400000000
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] e820: user-defined physical RAM map:
[    0.000000] user: [mem 0x0000000000010000-0x000000000009bbff] usable
[    0.000000] user: [mem 0x0000000027000000-0x0000000036f6dfff] usable
[    0.000000] user: [mem 0x00000000b93db000-0x00000000b9454fff] ACPI data
[    0.000000] user: [mem 0x00000000bb3d8000-0x00000000bb6d8fff] ACPI data
[    0.000000] user: [mem 0x00000000bd9fd000-0x00000000bdbfcfff] ACPI data
[    0.000000] user: [mem 0x00000000bdde7000-0x00000000bdfb0fff] ACPI data
[    0.000000] DMI 2.6 present.
...
[    2.264005] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xc0000000-0xcfffffff] (base 0xc0000000)
[    2.284811] PCI: not using MMCONFIG
===================================

     Thomas

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Thomas Renninger]

On Monday, January 21, 2013 10:11:04 AM Takao Indoh wrote:
> (2013/01/08 4:09), Thomas Renninger wrote:
...
> > I tried the provided patches first on 2.6.32, then I verfied with 3.8-rc2
> > and in both cases the disk is not detected anymore in
> > reset_devices (kexec'ed/kdump) case (but things work fine without these
> > patches).
> 
> So the problem that the disk is not detected was caused by exactmap
> problem you guys are discussing? Or still not detected even if exactmap
> problem is fixed?
This problem is related to the 5 PCI resetting patches.
Dumping worked with a 2.6.32 and a 3.8-rc2 kernel, adding the PCI resetting
patches broke both. I first tried 2.6.32 and verified with 3.8-rc2 to make sure
I didn't mess up the backport adjustings of the patches to 2.6.32.

Unfortunately this Dell platform takes really long to boot.
I can give it the one or other test, but please do not bomb me with patches.

For info:
About the interrupt remapping error interrupt storm in kdump case I tried to 
reproduce on this machine, but never could: The guys who saw that also cannot 
reproduce this anymore.

Two ideas I had about this:
  - As said already, (also) try to catch the error case and try to reset the
    the device in AER/Specific iterrupt remapping error interrupt caught.
  - Have a look at coreboot, these guys should know how to initialize the PCI
    subsystem from scratch and might have some well tested PCI resetting
    code in place already (no idea, just a thought).

    Thomas

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Takao Indoh]

(2013/01/23 9:47), Thomas Renninger wrote:
> On Monday, January 21, 2013 10:11:04 AM Takao Indoh wrote:
>> (2013/01/08 4:09), Thomas Renninger wrote:
> ...
>>> I tried the provided patches first on 2.6.32, then I verfied with 3.8-rc2
>>> and in both cases the disk is not detected anymore in
>>> reset_devices (kexec'ed/kdump) case (but things work fine without these
>>> patches).
>>
>> So the problem that the disk is not detected was caused by exactmap
>> problem you guys are discussing? Or still not detected even if exactmap
>> problem is fixed?
> This problem is related to the 5 PCI resetting patches.
> Dumping worked with a 2.6.32 and a 3.8-rc2 kernel, adding the PCI resetting
> patches broke both. I first tried 2.6.32 and verified with 3.8-rc2 to make sure
> I didn't mess up the backport adjustings of the patches to 2.6.32.

If you have a chance please try again the patches with the latest
firmware. I met another problem on megaraid_sas disk when I tested the
patches and it did not occur after updated its firmware to the latest
one.
  
> Unfortunately this Dell platform takes really long to boot.
> I can give it the one or other test, but please do not bomb me with patches.
>
> For info:
> About the interrupt remapping error interrupt storm in kdump case I tried to
> reproduce on this machine, but never could: The guys who saw that also cannot
> reproduce this anymore.
>
> Two ideas I had about this:
>    - As said already, (also) try to catch the error case and try to reset the
>      the device in AER/Specific iterrupt remapping error interrupt caught.
>    - Have a look at coreboot, these guys should know how to initialize the PCI
>      subsystem from scratch and might have some well tested PCI resetting
>      code in place already (no idea, just a thought).

Ok, at first I'll take a look at AER code to check how it resets devices
on PCIe error.

Thanks,
Takao Indoh

>
>      Thomas
>
>

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Thomas Renninger]

On Thursday, January 24, 2013 09:23:14 AM Takao Indoh wrote:
> (2013/01/23 9:47), Thomas Renninger wrote:
> > On Monday, January 21, 2013 10:11:04 AM Takao Indoh wrote:
> >> (2013/01/08 4:09), Thomas Renninger wrote:
> > ...
> > 
> >>> I tried the provided patches first on 2.6.32, then I verfied with
> >>> 3.8-rc2
> >>> and in both cases the disk is not detected anymore in
> >>> reset_devices (kexec'ed/kdump) case (but things work fine without these
> >>> patches).
> >> 
> >> So the problem that the disk is not detected was caused by exactmap
> >> problem you guys are discussing? Or still not detected even if exactmap
> >> problem is fixed?
> > 
> > This problem is related to the 5 PCI resetting patches.
> > Dumping worked with a 2.6.32 and a 3.8-rc2 kernel, adding the PCI
> > resetting
> > patches broke both. I first tried 2.6.32 and verified with 3.8-rc2 to make
> > sure I didn't mess up the backport adjustings of the patches to 2.6.32.
> If you have a chance please try again the patches with the latest
> firmware.
Not sure I can update the firmware as this is a reference platform used exactly
like this in production.

I also cannot see how this could help.

   Thomas

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Takao Indoh]

(2013/01/29 10:14), Thomas Renninger wrote:
> On Thursday, January 24, 2013 09:23:14 AM Takao Indoh wrote:
>> (2013/01/23 9:47), Thomas Renninger wrote:
>>> On Monday, January 21, 2013 10:11:04 AM Takao Indoh wrote:
>>>> (2013/01/08 4:09), Thomas Renninger wrote:
>>> ...
>>>
>>>>> I tried the provided patches first on 2.6.32, then I verfied with
>>>>> 3.8-rc2
>>>>> and in both cases the disk is not detected anymore in
>>>>> reset_devices (kexec'ed/kdump) case (but things work fine without these
>>>>> patches).
>>>>
>>>> So the problem that the disk is not detected was caused by exactmap
>>>> problem you guys are discussing? Or still not detected even if exactmap
>>>> problem is fixed?
>>>
>>> This problem is related to the 5 PCI resetting patches.
>>> Dumping worked with a 2.6.32 and a 3.8-rc2 kernel, adding the PCI
>>> resetting
>>> patches broke both. I first tried 2.6.32 and verified with 3.8-rc2 to make
>>> sure I didn't mess up the backport adjustings of the patches to 2.6.32.
>> If you have a chance please try again the patches with the latest
>> firmware.
> Not sure I can update the firmware as this is a reference platform used exactly
> like this in production.

Anyway it seems that resetting device makes the disks disappear from
your system. I'm wondering if this reset mechanism should be disabled by
default and be enabled by boot parameter like
reset_devices_on_dmar_fault to prevent a regression like your case.

Thanks,
Takao Indoh

>
> I also cannot see how this could help.
>
>     Thomas
>
>

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Takao Indoh]

(2013/01/23 9:47), Thomas Renninger wrote:
> On Monday, January 21, 2013 10:11:04 AM Takao Indoh wrote:
>> (2013/01/08 4:09), Thomas Renninger wrote:
> ...
>>> I tried the provided patches first on 2.6.32, then I verfied with 3.8-rc2
>>> and in both cases the disk is not detected anymore in
>>> reset_devices (kexec'ed/kdump) case (but things work fine without these
>>> patches).
>>
>> So the problem that the disk is not detected was caused by exactmap
>> problem you guys are discussing? Or still not detected even if exactmap
>> problem is fixed?
> This problem is related to the 5 PCI resetting patches.
> Dumping worked with a 2.6.32 and a 3.8-rc2 kernel, adding the PCI resetting
> patches broke both. I first tried 2.6.32 and verified with 3.8-rc2 to make sure
> I didn't mess up the backport adjustings of the patches to 2.6.32.
>
> Unfortunately this Dell platform takes really long to boot.
> I can give it the one or other test, but please do not bomb me with patches.
>
> For info:
> About the interrupt remapping error interrupt storm in kdump case I tried to
> reproduce on this machine, but never could: The guys who saw that also cannot
> reproduce this anymore.
>
> Two ideas I had about this:
>    - As said already, (also) try to catch the error case and try to reset the
>      the device in AER/Specific iterrupt remapping error interrupt caught.

I tried this idea but it did not work on megaraid_sas.

I made a experimental patch so that devices are reset when DMAR error is
detected on it. What happened is that:
1) megaraid_sas module is loaded.
2) DMAR error is detected during the driver initialization.
3) Reset device
4) kdump fails because the disk is not found.

When I tested patches which reset all devices in early boot time, the
disk was recognized correctly, so it seems that device reset during its
driver loading does something wrong. I think we need reset device at
least before its driver is loaded.

Thanks,
Takao Indoh


>    - Have a look at coreboot, these guys should know how to initialize the PCI
>      subsystem from scratch and might have some well tested PCI resetting
>      code in place already (no idea, just a thought).
>
>      Thomas
>
>

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Don Dutile]

On 03/03/2013 07:56 PM, Takao Indoh wrote:
> (2013/01/23 9:47), Thomas Renninger wrote:
>> On Monday, January 21, 2013 10:11:04 AM Takao Indoh wrote:
>>> (2013/01/08 4:09), Thomas Renninger wrote:
>> ...
>>>> I tried the provided patches first on 2.6.32, then I verfied with 3.8-rc2
>>>> and in both cases the disk is not detected anymore in
>>>> reset_devices (kexec'ed/kdump) case (but things work fine without these
>>>> patches).
>>>
>>> So the problem that the disk is not detected was caused by exactmap
>>> problem you guys are discussing? Or still not detected even if exactmap
>>> problem is fixed?
>> This problem is related to the 5 PCI resetting patches.
>> Dumping worked with a 2.6.32 and a 3.8-rc2 kernel, adding the PCI resetting
>> patches broke both. I first tried 2.6.32 and verified with 3.8-rc2 to make sure
>> I didn't mess up the backport adjustings of the patches to 2.6.32.
>>
>> Unfortunately this Dell platform takes really long to boot.
>> I can give it the one or other test, but please do not bomb me with patches.
>>
>> For info:
>> About the interrupt remapping error interrupt storm in kdump case I tried to
>> reproduce on this machine, but never could: The guys who saw that also cannot
>> reproduce this anymore.
>>
>> Two ideas I had about this:
>>     - As said already, (also) try to catch the error case and try to reset the
>>       the device in AER/Specific iterrupt remapping error interrupt caught.
>
> I tried this idea but it did not work on megaraid_sas.
>
> I made a experimental patch so that devices are reset when DMAR error is
> detected on it. What happened is that:
> 1) megaraid_sas module is loaded.
> 2) DMAR error is detected during the driver initialization.
This driver does something bad that IOMMU code isn't designed for,
or handle correctly -- it starts with one dma-mask, does an IOMMU mapping,
changes its dma-mask, and that moves it into another domain that's not
valid for the first mask.... and does occassional access with original mask.
I have it on my to-do list to dig into the driver more to see if that
sequence can be changed/fixed.

> 3) Reset device
> 4) kdump fails because the disk is not found.
>
> When I tested patches which reset all devices in early boot time, the
> disk was recognized correctly, so it seems that device reset during its
> driver loading does something wrong. I think we need reset device at
driver rest, or master-enable turned off ?

> least before its driver is loaded.
>
> Thanks,
> Takao Indoh
>
>
>>     - Have a look at coreboot, these guys should know how to initialize the PCI
>>       subsystem from scratch and might have some well tested PCI resetting
>>       code in place already (no idea, just a thought).
>>
>>       Thomas
>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump with iommu

[Takao Indoh]

(2013/03/05 7:00), Don Dutile wrote:
> On 03/03/2013 07:56 PM, Takao Indoh wrote:
>> (2013/01/23 9:47), Thomas Renninger wrote:
>>> On Monday, January 21, 2013 10:11:04 AM Takao Indoh wrote:
>>>> (2013/01/08 4:09), Thomas Renninger wrote:
>>> ...
>>>>> I tried the provided patches first on 2.6.32, then I verfied with 3.8-rc2
>>>>> and in both cases the disk is not detected anymore in
>>>>> reset_devices (kexec'ed/kdump) case (but things work fine without these
>>>>> patches).
>>>>
>>>> So the problem that the disk is not detected was caused by exactmap
>>>> problem you guys are discussing? Or still not detected even if exactmap
>>>> problem is fixed?
>>> This problem is related to the 5 PCI resetting patches.
>>> Dumping worked with a 2.6.32 and a 3.8-rc2 kernel, adding the PCI resetting
>>> patches broke both. I first tried 2.6.32 and verified with 3.8-rc2 to make sure
>>> I didn't mess up the backport adjustings of the patches to 2.6.32.
>>>
>>> Unfortunately this Dell platform takes really long to boot.
>>> I can give it the one or other test, but please do not bomb me with patches.
>>>
>>> For info:
>>> About the interrupt remapping error interrupt storm in kdump case I tried to
>>> reproduce on this machine, but never could: The guys who saw that also cannot
>>> reproduce this anymore.
>>>
>>> Two ideas I had about this:
>>>     - As said already, (also) try to catch the error case and try to reset the
>>>       the device in AER/Specific iterrupt remapping error interrupt caught.
>>
>> I tried this idea but it did not work on megaraid_sas.
>>
>> I made a experimental patch so that devices are reset when DMAR error is
>> detected on it. What happened is that:
>> 1) megaraid_sas module is loaded.
>> 2) DMAR error is detected during the driver initialization.
> This driver does something bad that IOMMU code isn't designed for,
> or handle correctly -- it starts with one dma-mask, does an IOMMU mapping,
> changes its dma-mask, and that moves it into another domain that's not
> valid for the first mask.... and does occassional access with original mask.
> I have it on my to-do list to dig into the driver more to see if that
> sequence can be changed/fixed.
>
>> 3) Reset device
>> 4) kdump fails because the disk is not found.
>>
>> When I tested patches which reset all devices in early boot time, the
>> disk was recognized correctly, so it seems that device reset during its
>> driver loading does something wrong. I think we need reset device at
> driver rest, or master-enable turned off ?

I have another patch to turn off busmaster bit in early quirk, but after
driver loading DMAR error is still detected as follows. This may be
driver problem as you said above.

Loading mptscsih.koigb: Intel(R) Gigabit Ethernet Network Driver - version 4.1.2-k
  module
Loadingigb: Copyright (c) 2007-2012 Intel Corporation.
  scsi_transport_dmar: DRHD: handling fault status reg 102
dmar: DMAR:[DMA Write] Request device [01:00.0] fault addr ffe16000
DMAR:[fault reason 01] Present bit in root entry is clear
Uhhuh. NMI received for unknown reason 2c on CPU 0.
Do you have a strange power saving mode enabled?
Dazed and confused, but trying to continue
fc.ko module
Loigb 0000:01:00.0: irq 76 for MSI/MSI-X
ading dm-log.ko igb 0000:01:00.0: irq 77 for MSI/MSI-X
module
Loading igb 0000:01:00.0: irq 78 for MSI/MSI-X
nf_conntrack_ipv6.ko module
Loading vhost_net.ko module
Loading igb.ko module
igb 0000:01:00.0: DCA enabled
igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection
igb 0000:01:00.0: eth0: (PCIe:2.5Gb/s:Width x2) c8:0a:a9:9d:fa:52
igb 0000:01:00.0: eth0: PBA No: 323131-030
igb 0000:01:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
dmar: DRHD: handling fault status reg 202
dmar: DMAR:[DMA Write] Request device [01:00.1] fault addr ffee9000
DMAR:[fault reason 01] Present bit in root entry is clear
igb 0000:01:00.1: irq 79 for MSI/MSI-X
igb 0000:01:00.1: irq 80 for MSI/MSI-X
igb 0000:01:00.1: irq 81 for MSI/MSI-X
(snip)

Thanks,
Takao Indoh

  
>> least before its driver is loaded.
>>
>> Thanks,
>> Takao Indoh
>>
>>
>>>     - Have a look at coreboot, these guys should know how to initialize the PCI
>>>       subsystem from scratch and might have some well tested PCI resetting
>>>       code in place already (no idea, just a thought).
>>>
>>>       Thomas
>>>
>>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>