From: Dario Faggioli <dfaggioli@suse.com>
To: Ian Jackson <iwj@xenproject.org>,
committers@xenproject.org, xen-devel@lists.xenproject.org
Cc: "Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Frédéric Pierret" <frederic.pierret@qubes-os.org>,
"George Dunlap" <George.Dunlap@citrix.com>
Subject: Re: [ANNOUNCE] Xen 4.15 release update - still in feature freeze
Date: Mon, 29 Mar 2021 19:16:24 +0200 [thread overview]
Message-ID: <970850cb5839e06dca089229029850cc67eae260.camel@suse.com> (raw)
In-Reply-To: <e98fa56dd32a73c6b230683958c433170315671e.camel@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
On Thu, 2021-03-18 at 19:11 +0100, Dario Faggioli wrote:
> On Mon, 2021-03-15 at 12:18 +0000, Ian Jackson wrote:
>
> >
> > https://bugzilla.opensuse.org/show_bug.cgi?id=1179246
> >
> So, this is mostly about the third issue, the one described in the
> openSUSE bug, which was however also reported here, by different
> people.
>
> As I've just wrote there (on the bug), I've been working on trying to
> reproduce the problem on a variety of different machines. Seems AMD
> seemed to be the most impacted, I've lately focused on hardware from
> such vendor.
>
FWIW, as a further update, there are now new info/logs here:
https://bugzilla.opensuse.org/show_bug.cgi?id=1179246
which I'm analyzing. And I should be able to have direct access to a
box where the issue can reproduced.
Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-03-29 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 12:18 [ANNOUNCE] Xen 4.15 release update - still in feature freeze Ian Jackson
2021-03-15 13:10 ` Andrew Cooper
2021-03-15 13:46 ` Jan Beulich
2021-03-16 9:43 ` Roger Pau Monné
2021-03-16 10:12 ` Jan Beulich
2021-03-18 18:11 ` Dario Faggioli
2021-03-29 17:16 ` Dario Faggioli [this message]
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=970850cb5839e06dca089229029850cc67eae260.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=George.Dunlap@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=committers@xenproject.org \
--cc=frederic.pierret@qubes-os.org \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.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.