From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from lemon.ertos.nicta.com.au ([203.143.174.143]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1W3H7r-00015c-Sf for kexec@lists.infradead.org; Wed, 15 Jan 2014 03:26:44 +0000 Date: Wed, 15 Jan 2014 13:25:49 +1000 Message-ID: <84k3e2lyde.wl%peter.chubb@nicta.com.au> From: Peter Chubb MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Subject: kexec-tools and multiboot breakage List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=twosheds.infradead.org@lists.infradead.org To: horms@verge.net.au Cc: kexec@lists.infradead.org Hi Simon, When you get a moment, please check out http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735360 Quick summary: If your kernel is configured to protect the first few pages of physical memory, then low memory doesn't start at location 0 --- so when scanning the memory ranges from /proc/iomem, the code in kexec/arch/i386/kexec-multiboot-x86.c never fills in mem_lower. I think it's safe to assume that if a memory segment starts at 64k or lower, it can be extended to location 0 because of the kernel protection on a PC99-style architecture. Peter C -- Dr Peter Chubb peter.chubb AT nicta.com.au http://www.ssrg.nicta.com.au Software Systems Research Group/NICTA _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec