From: "Marc - A. Dahlhaus" <mad@wol.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: bderzhavets@yahoo.com, Xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
M A Young <m.a.young@durham.ac.uk>
Subject: Re: Fw: Re: Problems with load the most recent 2.6.29-rc6 & Xen unstable on ASUS P5K Premium
Date: Wed, 04 Mar 2009 01:11:57 +0100 [thread overview]
Message-ID: <49ADC74D.1020900@wol.de> (raw)
In-Reply-To: <49ADA893.8010400@goop.org>
Jeremy Fitzhardinge schrieb:
> M A Young wrote:
>> On Tue, 3 Mar 2009, M A Young wrote:
>>
>>> If you need another reference point a kernel I build from
>>> xen/dom0/hackery as of 25th Feb works.
>>
>> Or more precisely up to and including changeset
>> 55d8085671863fe4ee6a17b7814bd38180a44e1d
>> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=55d8085671863fe4ee6a17b7814bd38180a44e1d
>>
>
> Thanks. I make the breakage a bit more recent than that. The current
> pushed xen/dom0/hackery boots for me now.
>
> J
Crashes for me on x86_32 with the same symptoms as in my last tests.
even the backtraces are quite the same as the ones posted before.
I'll try an x86_64 build tomorrow...
Marc
next prev parent reply other threads:[~2009-03-04 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 18:05 Fw: Re: Problems with load the most recent 2.6.29-rc6 & Xen unstable on ASUS P5K Premium Boris Derzhavets
2009-03-03 18:57 ` Jeremy Fitzhardinge
2009-03-03 19:13 ` Marc - A. Dahlhaus
2009-03-03 20:08 ` M A Young
2009-03-03 20:20 ` M A Young
2009-03-03 22:00 ` Jeremy Fitzhardinge
2009-03-04 0:11 ` Marc - A. Dahlhaus [this message]
2009-03-04 0:41 ` Jeremy Fitzhardinge
2009-03-04 11:37 ` Boris Derzhavets
2009-03-04 12:51 ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
2009-03-04 15:55 ` Boris Derzhavets
2009-03-05 1:51 ` 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=49ADC74D.1020900@wol.de \
--to=mad@wol.de \
--cc=Ian.Campbell@citrix.com \
--cc=bderzhavets@yahoo.com \
--cc=jeremy@goop.org \
--cc=m.a.young@durham.ac.uk \
--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.