[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [BUG] Linux kernel crash in amd_smn_init during PVH Dom0 boot on AMD EPYC


  • To: Arthur Borsboom <arthurborsboom@xxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Wed, 19 Aug 2026 09:52:22 +0200
  • Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=google header.d=suse.com header.i="@suse.com" header.h="Content-Transfer-Encoding:Content-Type:In-Reply-To:Autocrypt:From:Content-Language:References:Cc:To:Subject:User-Agent:MIME-Version:Date:Message-ID"
  • Autocrypt: addr=jbeulich@xxxxxxxx; keydata= xsDiBFk3nEQRBADAEaSw6zC/EJkiwGPXbWtPxl2xCdSoeepS07jW8UgcHNurfHvUzogEq5xk hu507c3BarVjyWCJOylMNR98Yd8VqD9UfmX0Hb8/BrA+Hl6/DB/eqGptrf4BSRwcZQM32aZK 7Pj2XbGWIUrZrd70x1eAP9QE3P79Y2oLrsCgbZJfEwCgvz9JjGmQqQkRiTVzlZVCJYcyGGsD /0tbFCzD2h20ahe8rC1gbb3K3qk+LpBtvjBu1RY9drYk0NymiGbJWZgab6t1jM7sk2vuf0Py O9Hf9XBmK0uE9IgMaiCpc32XV9oASz6UJebwkX+zF2jG5I1BfnO9g7KlotcA/v5ClMjgo6Gl MDY4HxoSRu3i1cqqSDtVlt+AOVBJBACrZcnHAUSuCXBPy0jOlBhxPqRWv6ND4c9PH1xjQ3NP nxJuMBS8rnNg22uyfAgmBKNLpLgAGVRMZGaGoJObGf72s6TeIqKJo/LtggAS9qAUiuKVnygo 3wjfkS9A3DRO+SpU7JqWdsveeIQyeyEJ/8PTowmSQLakF+3fote9ybzd880fSmFuIEJldWxp Y2ggPGpiZXVsaWNoQHN1c2UuY29tPsJgBBMRAgAgBQJZN5xEAhsDBgsJCAcDAgQVAggDBBYC AwECHgECF4AACgkQoDSui/t3IH4J+wCfQ5jHdEjCRHj23O/5ttg9r9OIruwAn3103WUITZee e7Sbg12UgcQ5lv7SzsFNBFk3nEQQCACCuTjCjFOUdi5Nm244F+78kLghRcin/awv+IrTcIWF hUpSs1Y91iQQ7KItirz5uwCPlwejSJDQJLIS+QtJHaXDXeV6NI0Uef1hP20+y8qydDiVkv6l IreXjTb7DvksRgJNvCkWtYnlS3mYvQ9NzS9PhyALWbXnH6sIJd2O9lKS1Mrfq+y0IXCP10eS FFGg+Av3IQeFatkJAyju0PPthyTqxSI4lZYuJVPknzgaeuJv/2NccrPvmeDg6Coe7ZIeQ8Yj t0ARxu2xytAkkLCel1Lz1WLmwLstV30g80nkgZf/wr+/BXJW/oIvRlonUkxv+IbBM3dX2OV8 AmRv1ySWPTP7AAMFB/9PQK/VtlNUJvg8GXj9ootzrteGfVZVVT4XBJkfwBcpC/XcPzldjv+3 HYudvpdNK3lLujXeA5fLOH+Z/G9WBc5pFVSMocI71I8bT8lIAzreg0WvkWg5V2WZsUMlnDL9 mpwIGFhlbM3gfDMs7MPMu8YQRFVdUvtSpaAs8OFfGQ0ia3LGZcjA6Ik2+xcqscEJzNH+qh8V m5jjp28yZgaqTaRbg3M/+MTbMpicpZuqF4rnB0AQD12/3BNWDR6bmh+EkYSMcEIpQmBM51qM EKYTQGybRCjpnKHGOxG0rfFY1085mBDZCH5Kx0cl0HVJuQKC+dV2ZY5AqjcKwAxpE75MLFkr wkkEGBECAAkFAlk3nEQCGwwACgkQoDSui/t3IH7nnwCfcJWUDUFKdCsBH/E5d+0ZnMQi+G0A nAuWpQkjM1ASeQwSHEeAWPgskBQL
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 19 Aug 2026 07:52:28 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 19.08.2026 09:09, Arthur Borsboom wrote:
>> Well, a pretty natural question: What amount of research have you done 
>> yourself?
> 
> Lovely response. You really know how to motivate people and welcome
> them into a community.
> 
> It has taken me about 1,5 day of work to find out why the screen
> remained black, to determine where the problem was, how to retrieve
> potential info by a serial-over-LAN console, subscribe to the mailing
> list, and create this bug report to help.
> 
> But don't worry, I won't do any debugging anymore for the Xen project,
> you have made sure of that. No need to respond.

Well, no, I can't really skip responding here. Yes, there was a risk that
you may take my reply as "not welcoming". Yet please can you try to see
both sides of the medal? From your initial report, which effectively
wasn't much more than the dumping of a log with the traces of a crash,
how could anyone have concluded how little or much work it was for you to
get there. As much as you have felt offended by my reply, I consider such
reports as an abuse as well: This is xen-devel@, not xen-users@, and I
think it is only fair for us to expect that reporters check whether their
problem was reported before, and whether therefore a fix already exists.

In fact, looking back - you did identify the earlier report. I clearly
scrolled down too quickly, and I'm sorry for that. The question then is,
though: What did you expect from re-reporting the issue to xen-devel@?
A patch for the issue is in flight, yet that patch to be taken is
nothing any of the Xen developers really have much control over: It's
not Xen interfacing code in Linux which is affected. So I continue to
have the feeling that this wasn't helpful at all, and my putting time
into finding the (apparently) most recent variant of the pending fix was
not valued / pointless, as I ended up offending you be a non-technical
aspect of my reply.

As a result I wonder: Would it have left you with better feelings if
your mail was left entirely unresponded to (as would end up reasonably
likely, according to my observations over many years)?

Jan



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.