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

Bug#535941: linux-image-2.6.26-2-xen-686: domU crashes daily



On Mon, 2009-07-06 at 10:08 +0200, Maximilian Mill wrote:
> Package: linux-image-2.6.26-2-xen-686
> Version: 2.6.26-17
> Severity: grave
> Justification: renders package unusable
> 
> domU crashes randomly... 
> 
> I have annother Lenny Xen-Hostsystem with 2.6.18-6-xen-686 dom0-kernel
> (from etch) and everything works perfect. Both systems won't work with 2.6.26-2-xen-686.
> 
> 
> xm dmesg:
> (XEN) domain_crash_sync called from entry.S (ff188600)
> (XEN) Domain 6 (vcpu#2) crashed on cpu#2:
> (XEN) ----[ Xen-3.2-1  x86_32p  debug=n  Not tainted ]----
> (XEN) CPU:    2
> (XEN) EIP:    0061:[<c01013a7>]
> (XEN) EFLAGS: 00000246   CONTEXT: guest
> (XEN) eax: 00000000   ebx: 00000001   ecx: 00000000   edx: ed447f90
> (XEN) esi: 00000002   edi: 00000002   ebp: 00000000   esp: ed447f84
> (XEN) cr0: 8005003b   cr4: 000026f0   cr3: 001b4ca0   cr2: b7ee59e0
> (XEN) ds: 007b   es: 007b   fs: 00d8   gs: 0000   ss: 0069   cs: 0061
> (XEN) Guest stack trace from esp=ed447f84:
> (XEN)    c0105f52 ffffffff 00000002 c0848f4e 00008225 00000000 00000000 ffffffff
> (XEN)    c01028ab c0102810 00000000 00000000 00000000 00000000 00000000 00000000
> (XEN)    00000000 00000000 00000000 00000000 00000000 00000000 000000d8 00000000
> (XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000
> (XEN) mm.c:645:d13 Non-privileged (13) attempt to map I/O space 0025b0a8
> (XEN) mm.c:3493:d13 ptwr_emulate: fixing up invalid PAE PTE 000000025b0a8025
> (XEN) mm.c:645:d14 Non-privileged (14) attempt to map I/O space 002734a8
> (XEN) mm.c:3493:d14 ptwr_emulate: fixing up invalid PAE PTE 00000002734a8025
[...]

In order to track this down, we will need to see a Linux 'oops' or 'BUG'
message, not this very limited dump from Xen.

Ben.

-- 
Ben Hutchings
DNRC Motto:  I can please only one person per day.
Today is not your day.  Tomorrow isn't looking good either.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: