From: Anthony Wright <anthony@overnetdata.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Getting mm.c errors from xl dmesg on certain hardware
Date: Fri, 23 Sep 2011 11:29:31 +0100 [thread overview]
Message-ID: <4E7C5F8B.6050509@overnetdata.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1450 bytes --]
Konrad Rzeszutek Wilk wrote:
>> (XEN) mm.c:907:d0 Error getting mfn 3a09c (pfn 55555555) from L1 entry 000000003a09c023 for l1e_owner=0, pg_owner=0
>> (XEN) mm.c:907:d0 Error getting mfn 3a09d (pfn 55555555) from L1 entry 000000003a09d023 for l1e_owner=0, pg_owner=0
>> (XEN) mm.c:907:d0 Error getting mfn 3a09e (pfn 55555555) from L1 entry 000000003a09e023 for l1e_owner=0, pg_owner=0
>> (XEN) mm.c:907:d0 Error getting mfn 3a09f (pfn 55555555) from L1 entry 000000003a09f023 for l1e_owner=0, pg_owner=0
>> (XEN) traps.c:2388:d0 Domain attempted WRMSR c0010004 from 0x0000ab23d6d622da to 0x000000000000abcd.
> Do they show up during bootup? As in do you see those _when_ you launch your guests?
> To figure out this particular issue you should try using 'console_to_ring' (so that
> dom0 output and Xen output are mingled togehter) and also post this under a new subject
> to not confuse this email thread.
The messages show up during the initial dom0 boot, before any domUs are
loaded. I've attached a second xl dmesg log which is similar to the
first, but the numbers in the error messages are different.
The messages are hardware dependant as I don't get them on another
system with different hardware configuration but with identical software.
The motherboard is a ASUS M2N68 AM PLUS, with 4GB of RAM. If I remove
one of the sticks of ram to take it down to 2GB, the mm.c errors are no
longer displayed, but I still get the traps.c message.
[-- Attachment #1.2: Type: text/html, Size: 2141 bytes --]
[-- Attachment #2: mm-errors-xl-dmesg.log --]
[-- Type: text/plain, Size: 4361 bytes --]
__ __ _ _ _ _
\ \/ /___ _ __ | || | / | / |
\ // _ \ '_ \ | || |_ | | | |
/ \ __/ | | | |__ _|| |_| |
/_/\_\___|_| |_| |_|(_)_(_)_|
(XEN) Xen version 4.1.1 (@[unknown]) (gcc version 4.4.3 (GCC) ) Wed Sep 21 08:25:36 GMT 2011
(XEN) Latest ChangeSet: unavailable
(XEN) Bootloader: GNU GRUB 0.97
(XEN) Command line: console_to_ring
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN) EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN) Found 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009b400 (usable)
(XEN) 000000000009b400 - 00000000000a0000 (reserved)
(XEN) 00000000000e2000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000aff90000 (usable)
(XEN) 00000000aff90000 - 00000000aff9e000 (ACPI data)
(XEN) 00000000aff9e000 - 00000000affe0000 (ACPI NVS)
(XEN) 00000000affe0000 - 00000000affee000 (reserved)
(XEN) 00000000afff0000 - 00000000b0000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fee00000 - 00000000fef00000 (reserved)
(XEN) 00000000fff00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000140000000 (usable)
(XEN) System RAM: 3839MB (3931308kB)
(XEN) ACPI: RSDP 000FB5D0, 0014 (r0 ACPIAM)
(XEN) ACPI: RSDT AFF90000, 0038 (r1 032210 RSDT1037 20100322 MSFT 97)
(XEN) ACPI: FACP AFF90200, 0084 (r2 032210 FACP1037 20100322 MSFT 97)
(XEN) ACPI: DSDT AFF90460, 7307 (r1 A1270 A1270000 0 INTL 20060113)
(XEN) ACPI: FACS AFF9E000, 0040
(XEN) ACPI: APIC AFF90390, 0090 (r1 032210 APIC1037 20100322 MSFT 97)
(XEN) ACPI: MCFG AFF90420, 003C (r1 032210 OEMMCFG 20100322 MSFT 97)
(XEN) ACPI: OEMB AFF9E040, 0071 (r1 032210 OEMB1037 20100322 MSFT 97)
(XEN) ACPI: HPET AFF97770, 0038 (r1 032210 OEMHPET0 20100322 MSFT 97)
(XEN) Xen heap: 9MB (9788kB)
(XEN) Domain heap initialised
(XEN) Processor #0 0:6 APIC version 16
(XEN) Processor #1 0:6 APIC version 16
(XEN) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Table is not found!
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3013.763 MHz processor.
(XEN) AMD-Vi: IOMMU not found!
(XEN) I/O virtualisation disabled
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) Platform timer is 25.000MHz HPET
(XEN) Allocated console ring of 16 KiB.
(XEN) CPU0: AMD SVM Extension is disabled in BIOS.
(XEN) SVM: failed to initialise.
(XEN) Brought up 2 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 32-bit, PAE, lsb
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x1000000 -> 0x1b38000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000138000000->000000013c000000 (920701 pages to be allocated)
(XEN) Init. ramdisk: 000000013f6ef000->000000013ffffca4
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c1000000->c1b38000
(XEN) Init. ramdisk: c1b38000->c2448ca4
(XEN) Phys-Mach map: c2449000->c27de638
(XEN) Start info: c27df000->c27df47c
(XEN) Page tables: c27e0000->c27fb000
(XEN) Boot stack: c27fb000->c27fc000
(XEN) TOTAL: c0000000->c2c00000
(XEN) ENTRY ADDRESS: c173e000
(XEN) Dom0 has maximum 2 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) Freed 188kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
(XEN) mm.c:907:d0 Error getting mfn 3809c (pfn b602c) from L1 entry 000000003809c023 for l1e_owner=0, pg_owner=0
(XEN) mm.c:907:d0 Error getting mfn 3809d (pfn b602d) from L1 entry 000000003809d023 for l1e_owner=0, pg_owner=0
(XEN) mm.c:907:d0 Error getting mfn 3809e (pfn b602e) from L1 entry 000000003809e023 for l1e_owner=0, pg_owner=0
(XEN) mm.c:907:d0 Error getting mfn 3809f (pfn b602f) from L1 entry 000000003809f023 for l1e_owner=0, pg_owner=0
(XEN) traps.c:2388:d0 Domain attempted WRMSR c0010004 from 0x00009b27fe9726ca to 0x000000000000abcd.
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2011-09-23 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 10:29 Anthony Wright [this message]
2011-09-23 10:46 ` Getting mm.c errors from xl dmesg on certain hardware Jan Beulich
2011-09-23 13:29 ` Konrad Rzeszutek Wilk
2011-09-23 14:42 ` Anthony Wright
2011-09-26 14:02 ` Konrad Rzeszutek Wilk
2011-09-26 15:00 ` Anthony Wright
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E7C5F8B.6050509@overnetdata.com \
--to=anthony@overnetdata.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.