On 26/09/2011 15:02, Konrad Rzeszutek Wilk wrote:
> On Fri, Sep 23, 2011 at 03:42:55PM +0100, Anthony Wright wrote:
>> On 23/09/2011 14:29, Konrad Rzeszutek Wilk wrote:
>>> On Fri, Sep 23, 2011 at 11:29:31AM +0100, Anthony Wright wrote:
>>>> 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.
>>>>
>>> Um, you might want to include 'loglevel=9 console=hvc0 initcall_debug' on
>>> your Linux line
>>> so the output from Linux kernel gets intermingled with the Xen.
>>>
>>>> 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.
>> I ran with 'console_to_ring conring_size=65536' on the xen command line
>> & 'debug loglevel=9 console=hvc0 initcall_debug' on the kernel command line.
> For the fun of it, can you twiddle with dom0_mem=512MB just to see what
> transpires?
I booted with dom0_mem=512MB on the xen command line (without the other
debug parameters), and got the mm.c & traps.c message as before.
> Nothing really jumps at me in regards to what could be at fault here. Is the
> .config
> based on some distro? Or is it a distro's config?
The .config is fairly home grown, but I've had a number of substantially
different kernel configs and they all consistantly produce this error on
this particular machine, but not on any other machines (aparts from the
traps on the old Dell). This is the same machine that we had problems
with the USB access (I've seen the problem once since, but can't
reliably reproduce it). The system seems to work ok, but I worry when I
see errors messages!!
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home