search for: 0xfc000000

Hi This patch correct on usb keyboard acces on number when enter via Ctrl + Alt + F12 on vt after Xorg running.Without this patch when enter on vt vas unable to use numbers from NumLock an only numbers from main keyboard. nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x046f00a3 nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46) nouveau [ DEVICE][0000:01:00.0] Family : NV40 nouveau [

Hi This patch correct on usb keyboard acces on number when enter via Ctrl + Alt + F12 on vt after Xorg running.Without this patch when enter on vt vas unable to use numbers from NumLock an only numbers from main keyboard. nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x046f00a3 nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46) nouveau [ DEVICE][0000:01:00.0] Family : NV40 nouveau [

...000180:0000e43d:00000000:00000001 >total_memory : 1023 >free_memory : 62 >xen_major : 3 >xen_minor : 0 >xen_extra : -unstable >xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 >platform_params : virt_start=0xfc000000 >xen_changeset : Tue Apr 25 18:22:11 2006 +0100 9744:1ad06bd6832d >cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) >cc_compile_by : build >cc_compile_domain : katana-technology.com >cc_compile_date : Wed Apr 26 00:10:30 EDT 2006 &gt...

...m32/gpllib/cpuid.c index fa21204..f33e895 100644 --- a/com32/gpllib/cpuid.c +++ b/com32/gpllib/cpuid.c @@ -232,8 +232,10 @@ void generic_identify(struct cpuinfo_x86 *c) } break; case X86_VENDOR_INTEL: - cpuid(0x4, &eax, &ebx, &ecx, &edx); - c->x86_num_cores = ((eax & 0xfc000000) >> 26) + 1; + if (c->cpuid_level >= 0x00000004) { + cpuid(0x4, &eax, &ebx, &ecx, &edx); + c->x86_num_cores = ((eax & 0xfc000000) >> 26) + 1; + } break; default: c->x86_num_cores = 1;

...febfbff:20000000:00000000:00000180:0000e43d:00000000:00000001 total_memory : 1023 free_memory : 62 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 platform_params : virt_start=0xfc000000 xen_changeset : Tue Apr 25 18:22:11 2006 +0100 9744:1ad06bd6832d cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) cc_compile_by : build cc_compile_domain : katana-technology.com cc_compile_date : Wed Apr 26 00:10:30 EDT 2006 [root@tst122 ~]# xm lis...

...wpi0@pci0:3:0:0: class=0x028000 card=0x10518086 chip=0x42228086 rev=0x02 hdr=0x0 0 vendor = 'Intel Corporation' device = 'PRO/Wireless 3945ABG [Golan] Network Connection' class = network Detected as: wpi0: <Intel(R) PRO/Wireless 3945ABG> mem 0xfc000000-0xfc000fff irq 17 at device 0.0 on pci3 According to man page is an unknown error uploading the firmware. I've thought about licensing issues with the firmware. Man page doesn't say anything about legal framework, so i think it's not needed but still i tried adding to loader.conf: leg...

.../kernel: Preloaded elf module "agp.ko" at 0xc06b9280. Apr 14 09:32:26 chapel-hill /kernel: Preloaded elf module "nvidia.ko" at 0xc06b931c. Apr 14 09:32:26 chapel-hill /kernel: pci1: <PCI bus> on pcib1 Apr 14 09:32:26 chapel-hill /kernel: nvidia0: <RIVA TNT2> mem 0xfc000000-0xfdffffff,0xf5000000-0xf5ffffff irq 11 at device 0.0 on pci1 Apr 14 09:32:26 chapel-hill /kernel: sio0: <3COM PCI FaxModem> port 0x1428-0x142f irq 11 at device 14.0 on pci0 Apr 14 09:32:26 chapel-hill /kernel: sio0: moving to sio2 Apr 14 09:32:26 chapel-hill /kernel: sio2: type 16550A Apr...

...14: [mem 0x8000a010-0x8000a01f 64bit] pci 0000:00:14.1: reg 10: [io 0x0000-0x0007] pci 0000:00:14.1: reg 14: [io 0x0000-0x0003] pci 0000:00:14.1: reg 18: [io 0x0000-0x0007] pci 0000:00:14.1: reg 1c: [io 0x0000-0x0003] pci 0000:00:14.1: reg 20: [io 0xff00-0xff0f] pci 0000:01:05.0: reg 10: [mem 0xfc000000-0xfdffffff 64bit pref] pci 0000:01:05.0: reg 18: [mem 0xfe9f0000-0xfe9fffff 64bit] pci 0000:01:05.0: reg 20: [io 0xc000-0xc0ff] pci 0000:01:05.0: reg 24: [mem 0xfe800000-0xfe8fffff] pci 0000:01:05.0: supports D1 D2 pci 0000:00:01.0: PCI bridge to [bus 01-01] pci 0000:00:01.0: bridge window [io...

...180d..bbf2993 100644 --- a/tools/firmware/hvmloader/config.h +++ b/tools/firmware/hvmloader/config.h @@ -53,6 +53,8 @@ extern struct bios_config ovmf_config; /* MMIO hole: Hardcoded defaults, which can be dynamically expanded. */ #define PCI_MEM_START 0xf0000000 #define PCI_MEM_END 0xfc000000 +#define PCI_MIN_BIG_BAR_SIZE 0x20000000 + extern unsigned long pci_mem_start, pci_mem_end; diff --git a/tools/firmware/hvmloader/pci.c b/tools/firmware/hvmloader/pci.c index fd56e50..0500db5 100644 --- a/tools/firmware/hvmloader/pci.c +++ b/tools/firmware/hvmloader/pci.c @@ -36,19 +3...

I was using my computer normally when suddenly my btrfs volume became read-only. This is on Chris'' for-linus branch (latest commit cb77fcd88) Here''s the relevant excerpt from dmesg [ 50.877500] r8169 0000:01:00.0: eth1: link up [ 50.880296] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 60.959215] eth1: no IPv6 routers present [ 1904.463247] atkbd serio0: Unknown key

Hi there, I am new to Xen. Just began trying it out from day-before. I have a CentOS 4.4 install on my hda6 partition. And I have a openSUSE 10.2 install on my hda8 partition. For openSUSE 10.2, I chose the Xen options while installing, and so I have the xen kernels too installed. For CentOS 4.4, I downloaded the Xen 3.0.2 source and compiled from there. (I followed the instructions at this

...tid=0x0004c400 nid=0x19 runnable "GC task thread#23 (ParallelGC)" prio=10 tid=0x0004d400 nid=0x1a runnable "VM Periodic Task Thread" prio=10 tid=0x002bd800 nid=0x22 waiting on condition JNI global references: 944 Heap PSYoungGen total 39424K, used 8967K [0xf9400000, 0xfc000000, 0xfc000000) eden space 33792K, 9% used [0xf9400000,0xf97424e8,0xfb500000) from space 5632K, 99% used [0xfb500000,0xfba7f8b0,0xfba80000) to space 5632K, 0% used [0xfba80000,0xfba80000,0xfc000000) PSOldGen total 90112K, used 5181K [0xf3c00000, 0xf9400000, 0xf9400000) object...

We created a 64bit SLES11 SP1 guest, and then used a script to change memory (using mem-set command) periodically (in 1 second): set 1G, set 2G, set 1G, set 2G, and so on. After a few minutes, we encountered QEMU exit due to SIGBUS error. Below is the call trace captured by gdb: The call trace: Program received signal SIGBUS, Bus error. 0x00007f94f74773d7 in memcpy () from /lib64/libc.so.6 (gdb)

...: afe9fbff:00100000:00000000:00000040:00000180 total_memory : 2038 free_memory : 0 xen_major : 3 xen_minor : 0 xen_extra : .4-1 xen_caps : xen-3.0-x86_32 xen_pagesize : 4096 platform_params : virt_start=0xfc000000 xen_changeset : unavailable cc_compiler : Configured with: /var/pisi/gcc-4.2.0-14/work/gcc-4.2-20070102/c cc_compile_by : root cc_compile_domain : cc_compile_date : Wed Jan 10 03:22:58 EET 2007 xend_config_format : 3 # cat /etc/xen/pardus name = &qu...

...: 1156 hw_caps : 0383fbff:c1c3fbff:00000000:00000020 memory : 511 free_memory : 221 xen_major : 3 xen_minor : 0 xen_extra : -devel xen_caps : xen_3.0_x86_32 xen_params : virt_start=0xfc000000 xen_changeset : Sun Nov 6 18:50:33 2005 +0100 7628:270469d40f02 cc_compiler : gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8) cc_compile_by : root cc_compile_domain : (none) cc_compile_date : Mon Nov 7 09:37:18 CET 2005 # xm dmesg Xen vers...

...nt: (XEN) HVM1:  - REP INSB across page boundaries ... passed (XEN) HVM1:  - GS base MSRs and SWAPGS ... passed (XEN) HVM1: Passed 2 of 2 tests (XEN) HVM1: Writing SMBIOS tables ... (XEN) HVM1: Loading ROMBIOS ... (XEN) HVM1: 9628 bytes of ROMBIOS high-memory extensions: (XEN) HVM1:   Relocating to 0xfc000000-0xfc00259c ... done (XEN) HVM1: Creating MP tables ... (XEN) HVM1: Loading Cirrus VGABIOS ... (XEN) HVM1: Loading PCI Option ROM ... (XEN) HVM1:  - Manufacturer: http://etherboot.org (XEN) HVM1:  - Product name: gPXE [root@localhost bug-report-20110217180212]# (XEN) HVM1: Loading ACPI ... (XEN) HVM...

Hey, Are there any known issues with the Intel''s integrated HD graphics 4000? I just bought a new laptop and have tried everything I can think of to get Xen to load. After choosing Xen in GRUB, it just boots to a black screen. There is no error message , no dmesg output, nothing. I have no idea what is causing this problem. I''ve gotten Xen to install with no problems on another

...LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23 ACPI: IOAPIC (id[0x03] address[0xfc000000] gsi_base[24]) IOAPIC[1]: apic_id 3, version 17, address 0xfc000000, GSI 24-27 ACPI: IOAPIC (id[0x04] address[0xfc001000] gsi_base[28]) IOAPIC[2]: apic_id 4, version 17, address 0xfc001000, GSI 28-31 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) ACPI: IRQ0 used by override. ACPI: IRQ2...

...LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23 ACPI: IOAPIC (id[0x03] address[0xfc000000] gsi_base[24]) IOAPIC[1]: apic_id 3, version 17, address 0xfc000000, GSI 24-27 ACPI: IOAPIC (id[0x04] address[0xfc001000] gsi_base[28]) IOAPIC[2]: apic_id 4, version 17, address 0xfc001000, GSI 28-31 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) ACPI: IRQ0 used by override. ACPI: IRQ2...

...] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] [ 0.157865] pci_root PNP0A03:00: host bridge window [mem 0x000d0000-0x000dffff] [ 0.157963] pci_root PNP0A03:00: host bridge window [mem 0xc0000000-0xf7ffffff] [ 0.158063] pci_root PNP0A03:00: host bridge window [mem 0xfc000000-0xfebfffff] [ 0.158162] pci_root PNP0A03:00: host bridge window [mem 0xfec10000-0xfecfffff] [ 0.158262] pci_root PNP0A03:00: host bridge window [mem 0xfed1c000-0xfed1ffff] [ 0.158361] pci_root PNP0A03:00: host bridge window [mem 0xfed90000-0xfed9ffff] [ 0.158460] pci_root PNP0A03:00:...