From: Jan Beulich <jbeulich@suse.com>
To: Denis <tachyon_gun@web.de>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org,
"Andrew Cooper" <andrew.cooper3@citrix.com>
Subject: Re: Aw: Re: Re: [help] Xen 4.14.5 on Devuan 4.0 Chimaera, regression from Xen 4.0.1
Date: Tue, 14 Mar 2023 16:37:51 +0100 [thread overview]
Message-ID: <40da0146-21fa-d5a9-7ae1-4ed2cf4a5785@suse.com> (raw)
In-Reply-To: <trinity-7c345507-5695-4649-a62b-be4dd793cc00-1678805608384@3c-app-webde-bap40>
On 14.03.2023 15:53, Denis wrote:
> On 14.03.2023 07:37; Jan Beulich wrote:
>> On 14.03.2023 02:15, Denis wrote:
>>> On 13.03.2023 10:36, Jan wrote
>>>> On 10.03.2023 21:50, Denis wrote:
>>>>> Should I test something else?
>>>>
>>>> ... there was no request for any further testing here, for the moment.
>>>
>>> ah...sorry, going by "Would be nice to have this confirmed forthe system
>>> in question, i.e. without Xen underneath Linux" I thought I could test
>>> something which might help shed some light on all of this.
>>
>> Well, yes, that Linux-without-Xen test would still be useful to have
>> results from. I didn't account for this in my earlier reply because
>> I had asked for it before already, and I did take "something else"
>> for meaning anything that might have turned up as useful from the new
>> data you had provided.
>
> What tests could I do or what info should I provide to help?
Boot plain Linux (no Xen underneath) and collect the full set of kernel
boot messages (some distros store this at /var/log/boot.msg); "full"
meaning we want to be able to see all output regardless of log-level.
Jan
next prev parent reply other threads:[~2023-03-14 15:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <trinity-8973751a-6742-4309-b02d-0b4c38f4206e-1678390468345@3c-app-webde-bap36>
2023-03-09 20:37 ` [help] Xen 4.14.5 on Devuan 4.0 Chimaera, regression from Xen 4.0.1 Andrew Cooper
2023-03-10 8:51 ` Jan Beulich
2023-03-10 20:50 ` Denis
2023-03-13 9:36 ` Jan Beulich
2023-03-13 11:43 ` Andrew Cooper
2023-03-13 11:54 ` Jan Beulich
2023-03-14 1:29 ` Aw: " Denis
2023-03-14 1:15 ` Denis
2023-03-14 6:37 ` Jan Beulich
2023-03-14 14:53 ` Aw: " Denis
2023-03-14 15:11 ` Andrew Cooper
2023-03-14 16:48 ` Denis
2023-03-14 17:12 ` Andrew Cooper
2023-03-14 19:12 ` Aw: " Denis
2023-03-16 15:59 ` Aw: " Jan Beulich
2023-03-19 19:42 ` Denis
2023-03-19 19:38 ` Aw: Re: Re: " Denis
2023-03-20 11:01 ` Andrew Cooper
2023-03-20 12:46 ` Denis
2023-03-20 14:23 ` Jan Beulich
2023-03-14 15:37 ` Jan Beulich [this message]
2023-03-14 16:45 ` Denis
2023-03-14 16:59 ` Jan Beulich
2023-03-14 19:09 ` Aw: " Denis
2023-03-15 8:11 ` Jan Beulich
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=40da0146-21fa-d5a9-7ae1-4ed2cf4a5785@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=tachyon_gun@web.de \
--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 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).