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
