On Sun, 2009-10-11 at 20:00 +0200, Bastian Blank wrote: > On Sun, Oct 11, 2009 at 06:33:54PM +0100, Ben Hutchings wrote: > > > (XEN) eax: 00000000 ebx: 00000001 ecx: 00000000 edx: ed447f90 > > > (XEN) esi: 00000002 edi: 00000002 ebp: 00000000 esp: ed447f84 > > > (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 > > In order to track this down, we will need to see a Linux 'oops' or 'BUG' > > message, not this very limited dump from Xen. > > There won't be any. This is obviously a crash in early startup. Even the > ebp register is unset and edx still points on the stack where probably > the startup info is located. If the kernel doesn't even start, I wonder how it can 'crash daily'. Maximilian, please explain. 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