Sven Köhler
2007-May-02 19:51 UTC
[Xen-devel] [BUG?] Non-privileged (1) attempt to map I/O space 000000f0
Hi,
i''m getting this error after i upgraded to xen 3.0.4-1.
It seems, that it doesn''t harm anything.
Anyway: for any domU i start, i get this in "xm dmesg":
(XEN) mm.c:566:d1 Non-privileged (1) attempt to map I/O space 000000f0
(XEN) mm.c:566:d2 Non-privileged (2) attempt to map I/O space 000000f0
(XEN) mm.c:566:d3 Non-privileged (3) attempt to map I/O space 000000f0
(XEN) mm.c:566:d4 Non-privileged (4) attempt to map I/O space 000000f0
(XEN) mm.c:566:d5 Non-privileged (5) attempt to map I/O space 000000f0
DomU-kernel ist 2.6.16.33 (xen-sources-2.6.16.33 on gentoo)
(the gentoo package is vanilla kernel + xen patches applied)
Here''s complete "xm dmesg":
__ __ _____ ___ _ _ _
\ \/ /___ _ __ |___ / / _ \| || | / |
\ // _ \ ''_ \ |_ \| | | | || |_ __| |
/ \ __/ | | | ___) | |_| |__ _|__| |
/_/\_\___|_| |_| |____(_)___(_) |_| |_|
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0.4-1 (root@dnsalias.com) (gcc-Version 4.1.1 (Gentoo
4.1.1-r3)) Wed May 2 19:31:45 CEST 2007
Latest ChangeSet: unavailable
(XEN) Command line: /boot/xen-3.gz dom0_mem=128M
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009f000 (usable)
(XEN) 000000000009f000 - 00000000000a0000 (reserved)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000003fef0000 (usable)
(XEN) 000000003fef0000 - 000000003fef3000 (ACPI NVS)
(XEN) 000000003fef3000 - 000000003ff00000 (ACPI data)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) System RAM: 1022MB (1047100kB)
(XEN) ACPI: RSDP (v000 VIAK8T ) @
0x00000000000f8dc0
(XEN) ACPI: RSDT (v001 VIAK8T AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x000000003fef3040
(XEN) ACPI: FADT (v001 VIAK8T AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x000000003fef30c0
(XEN) ACPI: SRAT (v001 AMD HAMMER 0x00000001 AMD 0x00000001) @
0x000000003fef8340
(XEN) ACPI: MADT (v001 VIAK8T AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x000000003fef8100
(XEN) ACPI: DSDT (v001 VIAK8T AWRDACPI 0x00001000 MSFT 0x0100000e) @
0x0000000000000000
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000003fef0000
(XEN) Domain heap initialised: DMA width 30 bits
(XEN) Xen heap: 14MB (14348kB)
(XEN) found SMP MP-table at 000f4f60
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:15 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2399.777 MHz processor.
(XEN) CPU0: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 512K (64 bytes/line)
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: AMD Athlon(tm) 64 Processor 3800+ stepping 02
(XEN) Mapping cpu 0 to node 255
(XEN) Total of 1 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 1 CPUs
(XEN) Machine check exception polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000001f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 000000003f000000->000000003f800000 (30720 pages to
be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80100000->ffffffff8048e304
(XEN) Init. ramdisk: ffffffff8048f000->ffffffff8048f000
(XEN) Phys-Mach map: ffffffff8048f000->ffffffff804cf000
(XEN) Start info: ffffffff804cf000->ffffffff804cf49c
(XEN) Page tables: ffffffff804d0000->ffffffff804d7000
(XEN) Boot stack: ffffffff804d7000->ffffffff804d8000
(XEN) TOTAL: ffffffff80000000->ffffffff80800000
(XEN) ENTRY ADDRESS: ffffffff80100000
(XEN) Dom0 has maximum 1 VCPUs
(XEN) Scrubbing Free RAM: ........done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen).
(XEN) mm.c:566:d1 Non-privileged (1) attempt to map I/O space 000000f0
(XEN) mm.c:566:d2 Non-privileged (2) attempt to map I/O space 000000f0
(XEN) mm.c:566:d3 Non-privileged (3) attempt to map I/O space 000000f0
(XEN) mm.c:566:d4 Non-privileged (4) attempt to map I/O space 000000f0
(XEN) mm.c:566:d5 Non-privileged (5) attempt to map I/O space 000000f0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Jan Beulich
2007-May-03 07:48 UTC
Re: [Xen-devel] [BUG?] Non-privileged (1) attempt to map I/O space 000000f0
>>> Sven Köhler <skoehler@upb.de> 02.05.07 21:51 >>> >i''m getting this error after i upgraded to xen 3.0.4-1. >It seems, that it doesn''t harm anything. > >Anyway: for any domU i start, i get this in "xm dmesg": >(XEN) mm.c:566:d1 Non-privileged (1) attempt to map I/O space000000f0>(XEN) mm.c:566:d2 Non-privileged (2) attempt to map I/O space000000f0>(XEN) mm.c:566:d3 Non-privileged (3) attempt to map I/O space000000f0>(XEN) mm.c:566:d4 Non-privileged (4) attempt to map I/O space000000f0>(XEN) mm.c:566:d5 Non-privileged (5) attempt to map I/O space000000f0 This is generally being caused by tools like hwinfo that try to map BIOS space (which is meaningless in DomU-s; only Dom0 is allowed to see the real BIOS space). Having looked at it quite a while back I thinks there''s nothing reasonable we can do at the Xen or kernel side, it''s the offending tool that needs fixing if this message is considered a problem. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel