search for: fbffffff

Hello We are seeing the following lines in our /var/log/kern file. and I am wondering why IO window is disabled for those pci bridges and if it is necessary to enable them. Nov 1 15:19:18 Song kernel: IO window: disabled. Nov 1 15:19:18 Song kernel: MEM window: f4000000-f7ffffff Nov 1 15:19:18 Song kernel: PREFETCH window: disabled. Nov 1 15:19:18 Song kernel: PCI: Bridge: 0000:07:00.0 Nov

...-PCI Bridge [10b5:8112] (rev aa) (prog-if 00 [Normal > decode]) > Flags: bus master, 66MHz, medium devsel, latency 66 > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > I/O behind bridge: 0000f000-0000ffff > Memory behind bridge: f5e00000-fbffffff > Prefetchable memory behind bridge: d5d00000-f5dfffff > Capabilities: [40] Power Management version 2 > Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ > Capabilities: [60] Express PCI/PCI-X to PCI-Express Bridge, MSI 00 > > 01:00.0 VGA...

...; HPAs. If that's remotely true, and we're not forcing an identity > > mapping of this HPA range into the GPA, does the vmd controller driver > > impose a TRA function on these MMIO addresses in the guest? > > This is the guest with the guest addresses: > f8000000-fbffffff : 0000:00:07.0 > f8000000-fbffffff : VMD MEMBAR1 > > f8000000-f83fffff : PCI Bus 10000:01 > f8000000-f800ffff : > 10000:01:00.0 > f8010000-f8013fff : 10000:01:00.0 > f801000 > 0-f8013fff : nvme > f8400000-f87fffff : PCI Bus 10000...

...FETCH window: disabled. PCI: Bridge: 0000:00:06.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:00:07.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:04:00.0 IO window: disabled. MEM window: f8000000-fbffffff PREFETCH window: disabled. PCI: Bridge: 0000:00:1c.0 IO window: disabled. MEM window: f8000000-fbffffff PREFETCH window: disabled. PCI: Bridge: 0000:00:1e.0 IO window: e000-efff MEM window: fc100000-fc2fffff PREFETCH window: d0000000-d7ffffff GSI 16 sharing vector 0xA9 and IRQ 16 ACPI...

...12 x1 Lane PCI Express-to-PCI Bridge [10b5:8112] (rev aa) (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, medium devsel, latency 66 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000f000-0000ffff Memory behind bridge: f5e00000-fbffffff Prefetchable memory behind bridge: d5d00000-f5dfffff Capabilities: [40] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [60] Express PCI/PCI-X to PCI-Express Bridge, MSI 00 01:00.0 VGA compatible controller [0300]:...

...UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 66, Cache Line Size: 32 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000f000-0000ffff Memory behind bridge: f5e00000-fbffffff Prefetchable memory behind bridge: d5d00000-f5dfffff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmr...

...ort- <TAbort- <MAbort- >SERR- <PERR- INTx- >> Latency: 66, Cache Line Size: 32 bytes >> >> Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 >> I/O behind bridge: 0000f000-0000ffff >> Memory behind bridge: f5e00000-fbffffff >> Prefetchable memory behind bridge: d5d00000-f5dfffff >> Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- >> BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B- >>...

...VSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 66, Cache Line Size: 32 bytes > > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > I/O behind bridge: 0000f000-0000ffff > Memory behind bridge: f5e00000-fbffffff > Prefetchable memory behind bridge: d5d00000-f5dfffff > Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- > BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B- > PriDiscTmr-...

...ort- <TAbort- <MAbort- >SERR- <PERR- INTx- >> Latency: 66, Cache Line Size: 32 bytes >> >> Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 >> I/O behind bridge: 0000f000-0000ffff >> Memory behind bridge: f5e00000-fbffffff >> Prefetchable memory behind bridge: d5d00000-f5dfffff >> Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- >> BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B- >>...

...;MAbort- >SERR- <PERR- INTx- >>> Latency: 66, Cache Line Size: 32 bytes >>> >>> Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 >>> I/O behind bridge: 0000f000-0000ffff >>> Memory behind bridge: f5e00000-fbffffff >>> Prefetchable memory behind bridge: d5d00000-f5dfffff >>> Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- >>> BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B- >>...

Hi, we are currently working on getting windows working on your xen servers. but we are facing a severe problem where dom0 and all domus hang for 1-5 seconds from time to time. we think it is probably because of disk i/o, because top sometimes says 100% wa (waiting on io) during the hang. dom0 has cpu 0 for exclusive use and the windows vms use cpu 1 to 7. should we give dom0 more than once

...;MAbort- >SERR- <PERR- INTx- >>> Latency: 66, Cache Line Size: 32 bytes >>> >>> Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 >>> I/O behind bridge: 0000f000-0000ffff >>> Memory behind bridge: f5e00000-fbffffff >>> Prefetchable memory behind bridge: d5d00000-f5dfffff >>> Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- >>> BridgeCtl: Parity+ SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B- >>...

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20060904/6ca2ff93/signature-0001.pgp

...RAM 00100000-0028fdc1 : Kernel code 0028fdc2-0032e31f : Kernel data 3ef2fc00-3ef2ffff : ACPI Non-volatile Storage 3ef30000-3ef3ffff : ACPI Tables 3ef40000-3efeffff : ACPI Non-volatile Storage 3eff0000-3effffff : reserved 3f000000-3f0003ff : 0000:00:1f.1 f0000000-f7ffffff : 0000:00:02.0 f8000000-fbffffff : 0000:00:00.0 fe00f000-fe00ffff : 0000:01:00.0 fecf0000-fecf0fff : reserved fed20000-fed9ffff : reserved ff8fe000-ff8fefff : 0000:01:08.0 ff8fe000-ff8fefff : e100 ffa7f400-ffa7f4ff : 0000:00:1f.5 ffa7f400-ffa7f4ff : Intel ICH5 - Controller ffa7f800-ffa7f9ff : 0000:00:1f.5 ffa7f800-ffa7f9ff :...

...sabled. PCI: Bridge: 0000:00:1c.4 IO window: d000-dfff MEM window: fb500000-fb5fffff PREFETCH window: disabled. PCI: Bridge: 0000:00:1c.5 IO window: e000-efff MEM window: fb600000-fb6fffff PREFETCH window: disabled. PCI: Bridge: 0000:00:1e.0 IO window: disabled. MEM window: fb700000-fbffffff PREFETCH window 0x00000000fa000000-0x00000000faffffff GSI 16 sharing vector 0x98 and IRQ 16 ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 16 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:00:03.0 to 64 ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI 16 (level, low) -> IRQ 16...

...01 [Subtractive decode]) Flags: bus master, 66MHz, medium devsel, latency 64 Bus: primary=00, secondary=04, subordinate=05, sec-latency=64 I/O behind bridge: 0000e000-0000efff Memory behind bridge: feb00000-febfffff Prefetchable memory behind bridge: f0000000-fbffffff 00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller (prog-if 10 [OHCI]) Subsystem: Biostar Microtech Int''l Corp Device 3700 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18 Memory at fe6f9000 (32-bit, non-prefetchable) [size=4K...

...tplug CPUs [ 0.000000] nr_irqs_gsi: 64 [ 0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff] [ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff] [ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff] [ 0.000000] e820: [mem 0x3f800000-0xfbffffff] available for PCI devices [ 0.000000] Booting paravirtualized kernel on Xen HVM [ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 14 pages/cpu @f2c27000 s35264 r0 d22080 u57344 [ 0.000000] pcpu-alloc: s35264 r0 d22080 u57344 a...

Hi All, I followed the instructions here at http://bderzhavets.wordpress.com/2009/06/10/setup-fedora-11-pv-domu-at-xen-3-4-1-dom0-kernel-2-6-30-rc6-tip-on-top-of-fedora-11/ However, when I do a "make menuconfig", I cannot see any XEN related configuration options. What am I missing? Thank you. Mr. Teo En Ming Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)