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

Re: [Xen-users] 2.6.28.7 domU oops: invalid opcode 0000


  • To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
  • From: Sven Köhler <sven.koehler@xxxxxxxxx>
  • Date: Thu, 12 Mar 2009 11:56:06 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 12 Mar 2009 03:54:54 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type; b=mkcr7bIr5l5tHrWpcCI7u4GoEFQs562Lf7Ra52w7ynhPXwSFijtlY0YOKvEZpEHXGz PvlpQsRw0ND+ZnTmrEyjtGu6wbQIsNjFrZ8uvneqYUdZCNydmb83myZJ+43Gx4lY/Ozn bgQ5CM4uUo9dC2Ggp43qGFnkEPyCjWg19047c=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Fajar A. Nugraha schrieb:
> On Thu, Mar 12, 2009 at 6:05 AM, Sven Köhler <sven.koehler@xxxxxxxxx> wrote:
>> Hi,
>>
>> below is the output of the kernel just before it goes down and crashes. I
>> have to use "xm destroy" to kill it.
>>
>> I have tried the enable/disable the "Optimize for Size" setting in the
>> kernel. I hopes that it's some kind of compiler bug because of the "invalid
>> opcode" thing. But actually I don't a clue what this might be caused by.
>>
>> Do you have any idea?
> 
> Is it x86 or x86_64 domU kernel? Do you have NX disabled in your BIOS?

I don't know. But the bug is fixed in 2.6.29-rc7.

Also see Jeremy's post on the devel list.

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.