Date: Tue, 31 Mar 2015 09:06:49 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= <roger.pau@citrix.com> To: <araujo@FreeBSD.org> Cc: freebsd-xen <freebsd-xen@freebsd.org> Subject: Re: Unable to load multiboot kernel. Message-ID: <551A4789.6070508@citrix.com> In-Reply-To: <CAOfEmZjOd7_dPxo40mykJ6MAdqf1OBPqmhOt%2BjQpPfNPL47Q%2BQ@mail.gmail.com> References: <CAOfEmZgT9nyJfEe5Z39qT9OSWkAa9RVY4xs0b4CjqN=3JJUU1A@mail.gmail.com> <55196D2F.8040203@citrix.com> <CAOfEmZh9ypr6qM4RqmxAZvghmOtUR=uoAHkWjMCOzeNmuZJTOg@mail.gmail.com> <551985BB.6050706@citrix.com> <CAOfEmZjOd7_dPxo40mykJ6MAdqf1OBPqmhOt%2BjQpPfNPL47Q%2BQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Hello, El 31/03/15 a les 5.26, Marcelo Araujo ha escrit: > Hi Roger, > > Yes, seems my BIOS is not correctly reporting the extended memory size. > The value that I got from my box is: > > bios_extmem: 0xff00000 memtop_copyin: 0x10000000 memtop: 0x10000000 > > I did check my BIOS if there is any suspicious options that may mess up > with the memory, but I didn't find nothing. I will check if there is any > new BIOS version. > > Do you have any other idea? Can you boot a bare metal kernel with boot_verbose="YES" and copy the memory map reported by FreeBSD when booting? There's also a recent change to biosmem.c which touched extended memory detection, r279222. Could you try to revert that commit and see if it makes any difference? Roger.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?551A4789.6070508>