bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Very strange Xen domU crash


From: Thomas Schwinge
Subject: Re: Very strange Xen domU crash
Date: Mon, 15 Dec 2008 16:18:27 +0100
User-agent: Mutt/1.5.11

Hello!

On Fri, Dec 12, 2008 at 02:09:59AM +0100, I wrote:
> On Fri, Dec 12, 2008 at 02:04:20AM +0100, Samuel Thibault wrote:
> > Thomas Schwinge, le Fri 12 Dec 2008 01:58:18 +0100, a écrit :
> > > This may be triggered by network traffic, but that is very vague, of
> > > course.  Any idea?
> > 
> > No idea.  Nothing in xm dmesg?
> 
> Oh, didn't know I was to look there.  Indeed:
> 
>     [...]
>     (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 96kB init memory.
>     (XEN) domain_crash_sync called from entry.S (ff1888be)
>     (XEN) Domain 4 (vcpu#0) crashed on cpu#0:
>     (XEN) ----[ Xen-3.2-1  x86_32p  debug=n  Not tainted ]----
>     (XEN) CPU:    0
>     (XEN) EIP:    0009:[<00000000>]
>     (XEN) EFLAGS: 00010212   CONTEXT: guest
>     (XEN) eax: 057df918   ebx: ffffffff   ecx: 06fa0000   edx: 057df918
>     (XEN) esi: ffffffff   edi: 21524110   ebp: ffffffff   esp: 00000000
>     (XEN) cr0: 8005003b   cr4: 000006f0   cr3: 48cd4000   cr2: c0000000
>     (XEN) ds: 0011   es: 0011   fs: 001f   gs: 0011   ss: 0011   cs: 0009
>     (XEN) Guest stack trace from esp=00000000:
>     (XEN)   Stack empty.
>     (XEN) domain_crash_sync called from entry.S (ff1888be)
>     (XEN) Domain 5 (vcpu#0) crashed on cpu#0:
>     (XEN) ----[ Xen-3.2-1  x86_32p  debug=n  Not tainted ]----
>     (XEN) CPU:    0
>     (XEN) EIP:    0009:[<00042af0>]
>     (XEN) EFLAGS: 00010216   CONTEXT: guest
>     (XEN) eax: 0587b000   ebx: 656a626f   ecx: 06fe0000   edx: 0587b000
>     (XEN) esi: 6c206f6e   edi: 20736168   ebp: 20656c69   esp: 66207463
>     (XEN) cr0: 8005003b   cr4: 000006f0   cr3: 48ce4000   cr2: 0909a010
>     (XEN) ds: 0011   es: 0011   fs: 001f   gs: 0011   ss: 0011   cs: 0009
>     (XEN) Guest stack trace from esp=66207463:
>     (XEN)   Fault while accessing guest memory.
>     (XEN) domain_crash_sync called from entry.S (ff1888be)
>     (XEN) Domain 9 (vcpu#0) crashed on cpu#0:
>     (XEN) ----[ Xen-3.2-1  x86_32p  debug=n  Not tainted ]----
>     (XEN) CPU:    0
>     (XEN) EIP:    0009:[<00000000>]
>     (XEN) EFLAGS: 00010212   CONTEXT: guest
>     (XEN) eax: 0574e9c0   ebx: 00000000   ecx: 06fb0000   edx: 0574e9c0
>     (XEN) esi: 00000000   edi: 00000000   ebp: 00000000   esp: 00000000
>     (XEN) cr0: 8005003b   cr4: 000006f0   cr3: 4fcd5000   cr2: c0000000
>     (XEN) ds: 0011   es: 0011   fs: 001f   gs: 0011   ss: 0011   cs: 0009
>     (XEN) Guest stack trace from esp=00000000:
>     (XEN)   Stack empty.

And another one:

    (XEN) domain_crash_sync called from entry.S (ff1888be)
    (XEN) Domain 11 (vcpu#0) crashed on cpu#0:
    (XEN) ----[ Xen-3.2-1  x86_32p  debug=n  Not tainted ]----
    (XEN) CPU:    0
    (XEN) EIP:    0009:[<06fe0008>]
    (XEN) EFLAGS: 00010202   CONTEXT: guest
    (XEN) eax: 0590c238   ebx: c703ff2c   ecx: 06fd0000   edx: 0590c238
    (XEN) esi: 00007ff0   edi: 00000000   ebp: 0703ff48   esp: 0703ff10
    (XEN) cr0: 8005003b   cr4: 000006f0   cr3: 481f6000   cr2: c0000000
    (XEN) ds: 0011   es: 0011   fs: 001f   gs: 0011   ss: 0011   cs: 0009
    (XEN) Guest stack trace from esp=0703ff10:
    (XEN)   Fault while accessing guest memory.


Regards,
 Thomas

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]