search for: e820

...slinux 1.08 memdisk 1.08 grub 0.93 lilo 21.4.4 The DOS images: FreeDOS 1.1.32a boot disk IBM LanAID (PCDOS) boot disk IBM PCDOS 7.1 boot disk Windows 95 boot disk Windows 98 boot disk The output I get for the different DOS images is as follows: * FreeDOS: (what I have on the screen!): e820: 000000001ff80000 0000000000080000 2 e820: 00000000ff800000 0000000000400000 2 e820: 00000000ffc00000 0000000000400000 2 Ramdisk at 0x1fdf0000, length 0x00168000 command line: initrd=freedos.img BOOT_IMAGE=memdisk.zi Disk is floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1494 bytes, allo...

Forcibly enabling the MMCFG space on AMD Fam10 CPUs cannot be expected to work since with the firmware not being aware of the address range used it cannot possibly reserve the space in E820 or ACPI resources. Hence we need to manually insert the range into the E820 table, and enable the range only when the insertion actually works without conflict. Further, the actual enabling of the space is done from identify_cpu(), which means that acpi_mmcfg_init() muts be called after that funct...

Two more observations: (adding to my previous below email) 1) Centos 5.6 also showing the same ACPI errors as in CentOS 5.5 2)BIOS-E820 map has a difference in the first line: (0000000000010000 instead of 0000000000000000) ================================ - Centos-5.3 BIOS-E820 memory map is: BIOS-e820: 0000000000000000 - 000000000009e000 (usable) BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e00...

...e console and ceases to respond and must be power cycled. Updating the firmware didn't help. There didn't appear to be any similar issues on the mailing list unless I missed them. Wondering if this has been observed before and whether or not there is an existing resolution or workaround? e820: 00000000000e0000 0000000000020000 2 e820: 0000000000100000 000000005a6a1000 1 e820: 000000005a7a1000 0000000000e40000 2 e820: 000000005b5e1000 000000001db1e000 1 e820: 00000000790ff000 0000000000100000 2 e820: 00000000791ff000 0000000002400000 4 e820: 000000007b5ff000 0000000000200000 3 e820: 0000...

I have a 12GB 64-bit Linux HVM guest (CentOS 5.5). When I look at the e820 map in the guest, I see the following: BIOS-provided physical RAM map: BIOS-e820: 0000000000010000 - 000000000009e000 (usable) BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 00000000f0000000 (usa...

...oot Feature Tool 2.08 (free download from http://www.hitachigst.com/hdd/support/download.htm) from a pen drive via memdisk. QEMU can boot the pen drive all right, my ThinkPad can't: Loading ftool208.img.........................ready. MEMDISK 3.53 2007-11-17 Copyright 2001-2007 H. Peter Anvin e820: 0000000000000000 000000000009f000 1 e820: 000000000009f000 0000000000001000 2 e820: 00000000000dc000 0000000000024000 2 e820: 0000000000100000 000000001f5e0000 1 e820: 000000001f6e0000 0000000000017000 3 e820: 000000001f6f7000 0000000000002000 4 e820: 000000001f700000 0000000000800000 2 e820: 0000...

...------------------------------------------------------ so old bootloader that it doesn't support commandline?! Linux version 2.6.7-1.667 (bhcompile at dolly.build.redhat.com) (gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Tue Nov 2 14:50:10 EST 2004 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f800 (usable) BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000001fff0000 (usable) BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS) BIOS-e820: 0000000...

E820 definitions copied from IntelFrameworkModulePkg/Csm/ LegacyBiosDxe/LegacyBiosInterface.h. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Wei Liu <wei.liu2@citrix.com> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com> --- OvmfPkg/Include/IndustryStandard/E8...

Hello, I'm extremely new to Linux and am working on creating a PXE server/menu with PXELINUX and Microsoft DHCP/TFTP. I've gotten it to work great with the exception of one box: the IBM SurePOS 532. If I specify a boot image in my DEFAULT file, it works fine. However when I try to use MENU.C32, it gets stuck at "Trying to Load: pxelinux.cfg/default." Based on TFTP logs, it

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB

...the firmware didn't help. > > There didn't appear to be any similar issues on the mailing list unless I > > missed them. > > > > Wondering if this has been observed before and whether or not there is an > > existing resolution or workaround? > > > > e820: 00000000000e0000 0000000000020000 2 > > e820: 0000000000100000 000000005a6a1000 1 > > e820: 000000005a7a1000 0000000000e40000 2 > > e820: 000000005b5e1000 000000001db1e000 1 > > e820: 00000000790ff000 0000000000100000 2 > > e820: 00000000791ff000 0000000002400000 4 &g...

I'm seeing this on a HP Blade and i'm not sure why this is happning since the nature of the issue is so wierd. I compiled mboot.c with a DEBUG defined in the mboot.c file. In the funciton init_mmap(), it prints the e820 map and on the HP blade this map values come out to be totally random. Some weird numbers which dont make any sense at all. However, if i add a while(1); or a exit(1); at the end of init_mmap() function, I magically see the values of the e820 printed correctly! its very weird why this may happen,...

...kmsg started. Aug 16 15:34:40 linux96 kernel: Linux version 2.6.9-34.ELsmp (bhcompile@hs20-bc1-7.build.redhat.com) (gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)) #1 SMP Fri Feb 24 16:54:53 EST 2006 Aug 16 15:34:40 linux96 kernel: BIOS-provided physical RAM map: Aug 16 15:34:40 linux96 kernel: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) Aug 16 15:34:40 linux96 kernel: BIOS-e820: 0000000000100000 - 00000000dffc0000 (usable) Aug 16 15:34:40 linux96 kernel: BIOS-e820: 00000000dffc0000 - 00000000dffcfc00 (ACPI data) Aug 16 15:34:40 linux96 kernel: BIOS-e820: 00000000dffcfc00 - 00000000d...

The changeset ''12803:df5fa63490f4da7b65c56087a68783dbcb7944f8'' added a new hypercall XENMEM_set_memory_map for specifying the e820 mapping. There was a small bug in the userspace side of this change though - the e820 mapping was specified based on the ''memory_static_min'' domain info parameter which means the memory map size is clamped to the value ''memory'' config option. What we actually wa...

...LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Distributor ID: CentOS Description: CentOS release 6.3 (Final) Release: 6.3 Codename: Final Below is an excerpt from dmesg BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009e800 (usable) BIOS-e820: 000000000009e800 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000020000000 (usable) BIOS-e820: 0000000020000000 - 0000000020200000 (reserved) BIOS-e820: 0000000...

My system is hanging up when attempting to boot a bootable floppy disk image Does the following info tell any story as to what's happening? Thanks. LABEL dosdiskimage KERNEL memdisk APPEND keeppxe initrd=dos.img floppy Loading dos.img ............. Ready. MEMDISK 3.11 2005-09-02 e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 2 e820: 00000000000e0000 0000000000020000 2 e820: 0000000000100000 0000000009ef0000 1 e820: 0000000009ff0000 0000000000008000 3 e820: 0000000009ff8000 0000000000008000 4 e820: 00000000fff80000 0000000000080000 2 Ramdisk at...

Use reserve_early rather than e820 reservations for Xen start info and mfn->pfn table, so that the memory use is a bit more self-documenting. Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> --- arch/x86/xen/setup.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/x86/x...

...ne tell me why thi is and a solution to this?? My Debian version is "Linux asterisk 2.6.12.3 #1 Mon Aug 1 19:33:51 WAT 2005 i686 GNU/Linux" The server is currently routing calls from SIP internal users through an E1 card (TE410) OUTPUT FROM dmesg command 00000000009dc00 (usable) BIOS-e820: 000000000009dc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000007fee0000 (usable) BIOS-e820: 000000007fee0000 - 000000007fee3000 (ACPI NVS) BIOS-e820: 000000007fee3000 - 000000007fef0000 (ACPI data) BIOS-e820: 0000...

...must be power cycled. Updating the firmware didn't help. > There didn't appear to be any similar issues on the mailing list unless I > missed them. > > Wondering if this has been observed before and whether or not there is an > existing resolution or workaround? > > e820: 00000000000e0000 0000000000020000 2 > e820: 0000000000100000 000000005a6a1000 1 > e820: 000000005a7a1000 0000000000e40000 2 > e820: 000000005b5e1000 000000001db1e000 1 > e820: 00000000790ff000 0000000000100000 2 > e820: 00000000791ff000 0000000002400000 4 > e820: 000000007b5ff000...

...; Here is the complete MEMDISK output from the failing > machine. This is a > > Toshiba Satellite Pro 4600 laptop. > > > > Loading memdisk.... > > Loading e100b.imz.......... > > Ready. > > MEMDISK 2.07 2.07-pre5 Copyright 2001-2003 H. Peter Anvin > > E820: 0000000000000000 000000000009fc00 1 > > E820: 000000000009fc00 0000000000000400 2 > > E820: 00000000000e0000 000000000000e800 2 > > E820: 00000000000ee800 0000000000000600 2 > > E820: 00000000000eee00 0000000000000200 4 > > E820: 00000000000ef000 0000000000001000 2 &g...