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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 7 Jan 2013 12:16:42 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Thomas Renninger <trenn@...e.de>
Cc:	MUNEDA Takahiro <muneda.takahiro@...fujitsu.com>,
	Takao Indoh <indou.takao@...fujitsu.com>,
	linux-pci@...r.kernel.org, x86@...nel.org,
	linux-kernel@...r.kernel.org, andi@...stfloor.org,
	tokunaga.keiich@...fujitsu.com, kexec@...ts.infradead.org,
	hbabu@...ibm.com, mingo@...hat.com, ddutile@...hat.com,
	vgoyal@...hat.com, ishii.hironobu@...fujitsu.com, hpa@...or.com,
	bhelgaas@...gle.com, tglx@...utronix.de, khalid@...ehiking.org
Subject: Re: [PATCH v7 0/5] Reset PCIe devices to address DMA problem on kdump
 with iommu

On Mon, Jan 7, 2013 at 11:09 AM, Thomas Renninger <trenn@...e.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/