search for: 0x100000

...dule$ /platform/i86pc/$ISADIR/boot_archive # ------------------------------------------------------------ grub boot for xen crashes with the error message: Error 16: Inconsistent filesystem structure GRUB uses fixed memory locations for MOS, DNODE, ZFS_SCRATCH... MOS is at memory location 0x100000. DNODE is at memory location 0x140000. ZFS_SCRATCH is at memory location 0x180000. Standard Solaris kernel /platform/i86pc/kernel/amd64/unix loads at 0x400000, 0x800000 and 0xC00000, and /platform/i86pc/amd64/boot_archive is loaded at 0xd5d000 - all after grub''s MOS / DNODE / ZFS_SCRATCH...

...le /initrd.img-2.6.16.33-xen savedefault boot When I try to boot, though, I get as far as the xen kernel trying to load, and then grub spits this out, and the machine reboots: root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen-3.0.4-1.gz [Multiboot-elf, <0x100000:0x9a878:0x5a788>, shtab=0x1f5078, entry=0x100000] module /vmlinuz-2.6.16.33-xen root=/dev/sda2 ro console=ttyS1,115200 noreboot sync_console [Multiboot-module @ 0x1f6000, 0x52afa0 bytes] module /initrd.img-2.6.16.33-xen [Multiboot-module @ 0x721000, 0x4b6000 bytes] Is there anythin...

...- a/binutils/bfd/elf64-x86-64.c +++ b/binutils/bfd/elf64-x86-64.c @@ -3630,7 +3630,8 @@ static const struct bfd_elf_special_section #define TARGET_LITTLE_NAME "elf64-x86-64" #define ELF_ARCH bfd_arch_i386 #define ELF_MACHINE_CODE EM_X86_64 -#define ELF_MAXPAGESIZE 0x100000 +#define ELF_MAXPAGESIZE 0x200000 +#define ELF_MINPAGESIZE 0x1000 #define elf_backend_can_gc_sections 1 #define elf_backend_can_refcount 1 When building klibc with new binutils, I get: $ readelf -l usr/klibc/libc.so Elf file type is...

...d = new_value; +} + /* Initializes the buffer structure. */ void @@ -30,6 +38,7 @@ buffer->alloc = len; buffer->offset = 0; buffer->end = 0; + buffer->unlimited = 0; } /* Frees any memory used for the buffer. */ @@ -78,7 +87,7 @@ u_int newlen; void *p; - if (len > 0x100000) + if (!buffer->unlimited && len > 0x100000) fatal("buffer_append_space: len %u not supported", len); /* If the buffer is empty, start using it from the beginning. */ @@ -107,7 +116,7 @@ /* Increase the size of the buffer and retry. */ newlen = buffer->alloc...

http://bugs.freedesktop.org/show_bug.cgi?id=14941 Summary: ioremap leak in DRM Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

...build and install PAE-disabled kernel (for dom0), but I can''t find the way to turn off PAE i XEN micro-kernel. Is there any manner to change XEN micro-kernel in 3.1.0 version to be PAE-disabled ? I get folowing messages, when booting xen kernel: (XEN) Xen kernel: 32-bit, PAE, lsb, paddr 0x100000 -> 0x664000 (XEN) Dom0 kernel: 32-bit, lsb (XEN) Mismatch between Xen and DOM0 kernel (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Could not set up DOM0 guest OS (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... -- Pozd...

...gt; #3 0xb73aa5d8 in lucene_index_build_more (index=0x8b24130, uid=4403, part_idx=0, > data=0x8b38f08 "1: kernel: i7core_edac 0000:00:14.0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)\n 1: kernel: pci 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing "..., size=8188, > hdr_name=0x0) at lucene-wrapper.cc:582 > namesize = <optimized out> > dest = 0x915f5d0 L"1: kernel: i7core_edac 0000:00:14 0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)\n 1: kernel: pci 0000:00:1...

...nfo->nr_vcpus > 1) || hvm_info->apic_mode ) { --- a/tools/firmware/hvmloader/rombios.c +++ b/tools/firmware/hvmloader/rombios.c @@ -127,6 +127,8 @@ static void rombios_load(const struct bi uint32_t bioshigh; struct rombios_info *info; + BUILD_BUG_ON(sizeof(rombios) > 0x100000 - ROMBIOS_PHYSICAL_ADDRESS); + memcpy((void *)config->bios_address, config->image, config->image_size); @@ -206,8 +208,6 @@ static void rombios_create_smbios_tables SMBIOS_PHYSICAL_END); } -//BUILD_BUG_ON(sizeof(rombios) > (0x00100000U - ROMBIOS_PHYSICAL_A...

...xen/marax.cfg libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: base group enabled libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: freq group enabled libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: time_ref_count group enabled xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0xbad04 xc: detail: elf_parse_binary: memory: 0x100000 -> 0x1bad04 xc: detail: VIRTUAL MEMORY ARRANGEMENT: xc: detail: Loader: 0000000000100000->00000000001bad04 xc: detail: Modules: 0000000000000000->0000000000000000 xc: detail: TOTAL: 0000000000000000->000000007f0000...

...gt; ------------------------------ -------------------------------------------------------------------- Booting ''Xen 3.3.2-rc5 / Debian GNU/Linux, Kernel 2.6.18.8-xen'' root (hda0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/xen-3.3.2-rc5.gz [Multiboot-elf,<0x100000:0xfd6b0:0x77950>,shtab=0x275078,entry=0 module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 [Multiboot-module @ 0x276000,0x5419c0 bytes] module /boot/initrd.img-2.6.18.8-xen Error 15: File not found press any key to continue ... -------------------------------------------------...

...gt; ------------------------------ -------------------------------------------------------------------- Booting ''Xen 3.3.2-rc5 / Debian GNU/Linux, Kernel 2.6.18.8-xen'' root (hda0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/xen-3.3.2-rc5.gz [Multiboot-elf,<0x100000:0xfd6b0:0x77950>,shtab=0x275078,entry=0 module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 [Multiboot-module @ 0x276000,0x5419c0 bytes] module /boot/initrd.img-2.6.18.8-xen Error 15: File not found press any key to continue ... -------------------------------------------------...

...gt; ------------------------------ -------------------------------------------------------------------- Booting ''Xen 3.3.2-rc5 / Debian GNU/Linux, Kernel 2.6.18.8-xen'' root (hda0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/xen-3.3.2-rc5.gz [Multiboot-elf,<0x100000:0xfd6b0:0x77950>,shtab=0x275078,entry=0 module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 [Multiboot-module @ 0x276000,0x5419c0 bytes] module /boot/initrd.img-2.6.18.8-xen Error 15: File not found press any key to continue ... -------------------------------------------------...

...his architecture # 2 MB - normal binaries start at 4 MB # -# Recent binutils use max-page-size=0x200000 by default, which pushes +# binutils now uses max-page-size=0x200000 by default, which pushes # klibc.so data over the 4 MB mark, overlapping the executable. -# Revert to the old max-page-size=0x100000 value. -KLIBCSHAREDFLAGS = -Ttext 0x00200200 -z max-page-size=0x100000 +# The old default was max-page-size=0x100000, but that also results +# in a broken layout with binutils 2.30. Since there's no +# architectural page size betwen 4 KB and 2MB, set it to 4 KB. +KLIBCSHAREDFLAGS = -Tt...

Hello, As it is known, Syslinux loads COM32 modules to 0x101000 (the PM IDT is at 0x100000). Unfortunately, in my project this area of memory is already occupied by another program that I need to preserve for a while (specifically, until Syslinux's COM32 module boots up the OS kernel). In other words, I need to load and execute COM32 modules from other than 0x101000 area of memory (f...

...his architecture # 2 MB - normal binaries start at 4 MB # -# Recent binutils use max-page-size=0x200000 by default, which pushes +# binutils now uses max-page-size=0x200000 by default, which pushes # klibc.so data over the 4 MB mark, overlapping the executable. -# Revert to the old max-page-size=0x100000 value. -KLIBCSHAREDFLAGS = -Ttext 0x00200200 -z max-page-size=0x100000 +# The old default was max-page-size=0x100000, but that also results +# in a broken layout with binutils 2.30. Since there's no +# architectural page size betwen 4 KB and 2MB, set it to 4 KB. +KLIBCSHAREDFLAGS = -Tt...

...at boot_params.hdr.code32_start field is probably either invalid (bad reloc or something else causing the bootloader to >calculate the wrong address) or valid but the thing it thinks it is pointing to wasn't loaded (missing PT_LOAD etc.). boot_params.hdr.code32_start field is valid :) It is 0x100000, like expected (btw thanks for those links on info how kernel boots, they were pretty useful). I checked it is valid using trace: void go_to_protected_mode(void) { if (boot_params.hdr.code32_start == 0x100000) puts("go_to_protected_mode 1\n"); else puts("go_to_protected_mode 2\n...

...ytes ;; can_extents) exit 0 ;; extents) echo "0 32K zero" echo "32K 32K hole,zero" echo "64K 983040 " ;; *) exit 2 ;; esac EOF [...] 2019-04-01 11:49:40.818357 connection=1 Extents id=2 offset=0x0 count=0x100000 req_one=1 ... 2019-04-01 11:49:40.819848 connection=1 ...Extents id=2 extents=[{ offset=0x0, length=0x8000, hole=0, zero=1 }, { offset=0x8000, length=0x8000, hole=1, zero=1 }, { offset=0x10000, length=0xf0000, hole=0, zero=0 }] return=0 Updates commit ed868b00f192cd72e91265e4fcdf3c3fbe8b7613. T...

...#39; qemu-io -r -f raw -c 'r -P 11 2M 1M' 'nbd+unix://?socket=log.sock' +# The log should have been appended, preserving our marker. +grep '# My log' log.log # The log should show a write on connection 1, and read on connection 2. grep 'connection=1 Write id=1 offset=0x100000 count=0x200000 ' log.log grep 'connection=2 Read id=1 offset=0x200000 count=0x100000 ' log.log -- 2.17.2

16396:055d98aa2dd0 almost works but not quite. LDFLAGS_DIRECT means we end up with: gld -melf_i386 -nostdlib -N -Ttext 0x100000 -o hvmloader.tmp hvmloader.o mp_tables.o util.o smbios.o 32bitbios_support.o acpi/acpi.a Specifying a linker script and asking for -nostdlib is obviously contradictory. Removing $(LDFLAGS_DIRECT) fixes the problem. regards john _______________________________________________ Xen-devel mailing li...

...xl: detail: libxl_dom.c:238:hvm_set_viridian_features: base group enabled > libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: freq group enabled > libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: time_ref_count > group enabled > xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0xbad04 > xc: detail: elf_parse_binary: memory: 0x100000 -> 0x1bad04 > xc: detail: VIRTUAL MEMORY ARRANGEMENT: > xc: detail: Loader: 0000000000100000->00000000001bad04 > xc: detail: Modules: 0000000000000000->0000000000000000 > xc: detail: TOTAL: 0000000000...