All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Linux upstream can't boot Xen x86 any more
Date: Thu, 23 Oct 2014 16:43:14 +0100	[thread overview]
Message-ID: <21577.8722.55274.543728@mariner.uk.xensource.com> (raw)
In-Reply-To: <osstest-30868-mainreport@xen.org>

xen.org writes ("[linux-linus test] 30868: regressions - trouble: broken/fail/pass"):
> flight 30868 linux-linus real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/30868/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-amd64-xl           5 xen-boot           fail REGR. vs. 30019
>  test-amd64-i386-xl            5 xen-boot           fail REGR. vs. 30019

Lots and lots of these.  The last bit of the serial log is this:

Oct 23 09:20:29.074636 (XEN) Freed 292kB init memory.
Oct 23 09:20:29.082623 (XEN) ==== PCI devices ====
Oct 23 09:20:29.082656 (XEN) ==== segment 0000 ====
Oct 23 09:20:29.082680 mapping kernel into physical memory
Oct 23 09:20:29.090587 about to get started...
Oct 23 09:20:29.090615 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.

The osstest bisector is working on it (at least it is now - I have
just unbroken it) but it'll be a while because there's a huge range of
commits involved.

Ian.

  reply	other threads:[~2014-10-23 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 12:24 [linux-linus test] 30868: regressions - trouble: broken/fail/pass xen.org
2014-10-23 15:43 ` Ian Jackson [this message]
2014-10-23 15:47   ` Linux upstream can't boot Xen x86 any more David Vrabel
2014-10-23 15:48     ` Ian Jackson

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=21577.8722.55274.543728@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xenproject.org \
    /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.