From: Roman Shaposhnik <roman@zededa.com>
To: xen-devel@lists.xenproject.org
Subject: [Xen-devel] [TESTDAY] Test report
Date: Fri, 15 Nov 2019 17:12:43 -0800 [thread overview]
Message-ID: <CAMmSBy8qFCEssF6vdTTAgxpijGns4QFgKQpT6Kvj9AorQ5mSZQ@mail.gmail.com> (raw)
NOTE: this may or may not be a hair on fire problem, reporting it
anyway since I'd hate to pass on something that maybe a serious issue.
I haven't had time to debug this just yet -- so just reporting it here
pretty raw.
Software:
Xen 4.13 RC2
Linux kernel 4.19.5
Hardware:
Supermicro E300
https://www.supermicro.com/en/products/system/Mini-ITX/SYS-E300-8D.cfm
Supermicro E100
https://www.supermicro.com/en/products/system/Box_PC/SYS-E100-9S.cfm
Supermicro E50
https://www.supermicro.com/en/products/system/Box_PC/SYS-E50-9AP.cfm
Functionality tested: trying to boot Dom0
Comments: Xen boots completely and then seems like it either dies
right after saying
Xen relinquishing a console
or Dom0 dies (without printing a single line of output)
FWIW, this started happening after upgrade to RC2. IOW, if I take my
previous RC1 binary and stick it into the very same setup --
everything boots fine.
The issue doesn't seem to be reproducible on Dell boxes (and in my
virtual QEmu setup) that I've got.
Thanks,
Roman.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-11-16 1:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 1:12 Roman Shaposhnik [this message]
2019-11-18 6:15 ` [Xen-devel] [TESTDAY] Test report Jürgen Groß
2019-11-19 7:22 ` Roman Shaposhnik
-- strict thread matches above, loose matches on Subject: below --
2019-11-15 2:39 Roman Shaposhnik
2019-11-15 7:04 ` Jürgen Groß
2019-11-14 18:34 Tamas K Lengyel
2019-11-14 18:39 ` Andrew Cooper
2019-11-14 22:36 ` Tamas K Lengyel
2019-11-15 11:56 ` Andrew Cooper
2019-11-15 15:19 ` Tamas K Lengyel
2019-11-15 15:32 ` Jürgen Groß
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=CAMmSBy8qFCEssF6vdTTAgxpijGns4QFgKQpT6Kvj9AorQ5mSZQ@mail.gmail.com \
--to=roman@zededa.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.