xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: Masaki Kanno <kanno.masaki@jp.fujitsu.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Domain-0 kernel boot failure withxen-unstableandlinux-2.6.18-xen
Date: Thu, 14 Jan 2010 09:05:32 +0000	[thread overview]
Message-ID: <4B4EEC6C0200007800029E50@vpn.id2.novell.com> (raw)
In-Reply-To: <2FCA94E163BE9Akanno.masaki@jp.fujitsu.com>

You forgot to tell us in what way the boot fails.

Jan

>>> Masaki Kanno <kanno.masaki@jp.fujitsu.com> 14.01.10 07:18 >>>
Thu, 14 Jan 2010 14:45:07 +0900, Masaki Kanno wrote:

>Thu, 14 Jan 2010 11:57:20 +0900, Masaki Kanno wrote:
>
>>Thu, 14 Jan 2010 10:51:45 +0900, Masaki Kanno wrote:
>>
>>>Hi,
>>>
>>>I have encountered a problem with xen-unstable and linux-2.6.18-xen.
>>>The problem is that Domain-0 kernel is not booted.  I'm pinpointing 
>>>a changeset causing the problem.
>>>
>>>xen-unstable   linux-2.6.18-xen   result
>>>cs:20597       cs:959             success
>>>cs:20654       cs:962             success
>>>cs:20702       cs:967             success
>  cs:20704       cs:967             success
   cs:20705       cs:967             failure
>  cs:20710       cs:967             failure
>> cs:20714       cs:969             failure
>> cs:20729       cs:970             failure
>>>cs:20744       cs:970             failure
>>>cs:20779       cs:981             failure

The problem occurs by xen-unstable changeset 20705.
I can pinpoint the changeset causing the problem, but I cannot find out 
a bug in the changeset...

Best regards,
 Kan



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

  reply	other threads:[~2010-01-14  9:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14  1:51 Domain-0 kernel boot failure with xen-unstable and linux-2.6.18-xen Masaki Kanno
2010-01-14  2:57 ` Domain-0 kernel boot failure with xen-unstable andlinux-2.6.18-xen Masaki Kanno
2010-01-14  5:45   ` Domain-0 kernel boot failure with xen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-14  6:18     ` Domain-0 kernel boot failure withxen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-14  9:05       ` Jan Beulich [this message]
2010-01-14 11:07         ` Domain-0 kernel boot failurewithxen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-14 11:26           ` Keir Fraser
2010-01-14 11:42             ` Domain-0 kernel bootfailurewithxen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-15 12:35               ` Domain-0 kernelbootfailurewithxen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-14  9:31       ` Domain-0 kernel boot failure withxen-unstableandlinux-2.6.18-xen Keir Fraser
2010-01-14 11:33         ` Domain-0 kernel boot failurewithxen-unstableandlinux-2.6.18-xen Masaki Kanno
2010-01-18 15:18       ` Domain-0 kernel boot failure withxen-unstableandlinux-2.6.18-xen Keir Fraser
2010-01-19 10:14         ` Domain-0 kernel boot failurewithxen-unstableandlinux-2.6.18-xen Masaki Kanno

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=4B4EEC6C0200007800029E50@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=kanno.masaki@jp.fujitsu.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).