From: Killian De Volder <killian.de.volder@scarlet.be>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Crashing DomU
Date: Wed, 11 Nov 2009 19:03:22 +0100 [thread overview]
Message-ID: <4AFAFC6A.609@scarlet.be> (raw)
In-Reply-To: <4AFAFC0F.5050007@scarlet.be>
[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]
I tried this version:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.32-rc6.tar.bz2
And several other, i played some with the settings i changed, but cannot
reproduce.
(And I don't really have a lot of time left to look for this.)
Must be some sort of weird "your not suppose to do this" kind of bugs
and/or weird combination.
My config probably wasn't sane.
If anyone feels like tracking down a low priority bug (since it's
probably something weird), have fun :p
>
>
>> On Wed, Nov 11, 2009 at 04:04:51PM +0100, Killian De Volder wrote:
>>
>>> I'm not entirely certain, if you wish i could seek out the option.
>>>
>>
>> Please do.
>>
>> Earlier you mention that the kernel you built is Vanilla 2.6.31.6 - where
>> did you get it from? What git branch is it from?
>>
>> Thanks.
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 1850 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-11-11 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 21:56 Crashing DomU Killian De Volder
2009-11-11 8:08 ` Killian De Volder
2009-11-11 9:29 ` Pasi Kärkkäinen
2009-11-11 15:04 ` Killian De Volder
2009-11-11 15:30 ` Konrad Rzeszutek Wilk
[not found] ` <4AFAFC0F.5050007@scarlet.be>
2009-11-11 18:03 ` Killian De Volder [this message]
2009-11-11 18:11 ` Konrad Rzeszutek Wilk
2009-11-11 21:49 ` Jeremy Fitzhardinge
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=4AFAFC6A.609@scarlet.be \
--to=killian.de.volder@scarlet.be \
--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.