All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sven Köhler" <sven.koehler@gmail.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com, Stable Kernel <stable@kernel.org>,
	Jens Axboe <jens.axboe@oracle.com>
Subject: Re: 2.6.28.7 domU crashes
Date: Thu, 12 Mar 2009 11:56:58 +0100	[thread overview]
Message-ID: <49B8EA7A.4090209@gmail.com> (raw)
In-Reply-To: <49B8577E.40705@goop.org>


[-- Attachment #1.1: Type: text/plain, Size: 665 bytes --]

Jeremy Fitzhardinge schrieb:
> Sven Köhler 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?
>>
>> The crash is very reproducable.
> 
> Looks like the crash fixed by the change below
> (c7241227f61ca6606a7fa3555391360d92bd8d9b in linux-2.6.git)

I have tested 2.6.29-rc7. It works stable for me.


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

      reply	other threads:[~2009-03-12 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11 22:47 2.6.28.7 domU crashes Sven Köhler
2009-03-12  0:29 ` Jeremy Fitzhardinge
2009-03-12 10:56   ` Sven Köhler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49B8EA7A.4090209@gmail.com \
    --to=sven.koehler@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=jeremy@goop.org \
    --cc=stable@kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.