All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Dylanger Daly <dylangerdaly@protonmail.com>
Cc: xen-devel@lists.xenproject.org, Andrew.Cooper3@citrix.com
Subject: Re: Ryzen 6000 (Mobile)
Date: Thu, 25 Aug 2022 10:35:43 +0200	[thread overview]
Message-ID: <3b2ad2ca-3c6c-4dcb-c603-bd5440350f20@suse.com> (raw)
In-Reply-To: <Zz_iE6KdPdkQ_TjUf-W2ODPIXo2WwXz0JxF5vgPjVuz8uWfJyto5S_nYRzSNrE0jC3r4ILhjkLH_PtW_fmIeTQIQtI6wTZxnUvOl0pr6ne4=@protonmail.com>

On 24.08.2022 20:15, Dylanger Daly wrote:
> I'm sorry I didn't get where in /sys/firmware you'd like to take a look at.

It's been a long time since I last needed to access that, when it
was still /proc/mem and/or /proc/kmem. Their modern equivalents might
be /sys/devices/virtual/mem/{,k}mem ... But if that's not usable to
get at the needed data, perhaps we should go with logging it by way
of a patch to Xen. Please let me know if I need to hand you a patch
to do so.

> Sometimes when I power the laptop off I can see it's crashing somewhere in ACPI/weird address issue

In ACPI or in EFI? In the latter case suppressing the use of the EFI
runtime service for shutdown/reboot may help ("efi=no-rs" to disable
all runtime services use might be a good first try).

> Is there anyone else struggling with AMD Ryzen 6000 on Xen?

Don't know.

Jan


  reply	other threads:[~2022-08-25  8:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 23:04 Ryzen 6000 (Mobile) Dylanger Daly
2022-07-19  6:29 ` Jan Beulich
2022-07-19  6:47   ` Dylanger Daly
2022-07-19  6:58     ` Jan Beulich
2022-07-19  6:50   ` Dylanger Daly
2022-07-19  9:34 ` Andrew Cooper
2022-07-20  0:33   ` Dylanger Daly
2022-07-20  8:11     ` Jan Beulich
2022-07-20  8:13       ` Jan Beulich
2022-08-15 11:07         ` Dylanger Daly
2022-08-15 11:30           ` Jan Beulich
2022-08-15 11:50             ` Dylanger Daly
2022-08-15 11:55               ` Jan Beulich
2022-08-15 12:03           ` Andrew Cooper
2022-08-15 15:39             ` Dylanger Daly
2022-08-15 16:19               ` Jan Beulich
2022-08-15 16:54                 ` Dylanger Daly
2022-08-16  6:17                   ` Jan Beulich
2022-08-16  8:34                     ` Dylanger Daly
2022-08-16  8:59                       ` Jan Beulich
2022-08-16  9:19                         ` Dylanger Daly
2022-08-16  9:30                           ` Jan Beulich
2022-08-16 11:22                   ` Jan Beulich
2022-08-24 18:15                     ` Dylanger Daly
2022-08-25  8:35                       ` Jan Beulich [this message]
2022-08-25 11:10                         ` Dylanger Daly
2022-08-25 14:55                           ` Jan Beulich
2022-08-29 15:26                             ` Dylanger Daly
2022-09-06 10:52                               ` Jan Beulich
2022-09-06 11:45                                 ` Dylanger Daly
2022-08-31 22:12                             ` Dylanger Daly
2022-09-06 10:50                               ` Jan Beulich
2022-09-03 15:59                             ` Dylanger Daly
2022-09-05 20:44                             ` Dylanger Daly
     [not found]                             ` <6JMvOsjmpWkAsnm6AXzNsjtj5_jy5vG_vG_PwTyDzX0z1buoX89r5UEpSGKf-H7CTBtg9gNlq4Icy7Q9OIDjfrxp2AqNMXbyKTCD0y_d0Hc=@protonmail.com>
2022-09-06 11:51                               ` 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=3b2ad2ca-3c6c-4dcb-c603-bd5440350f20@suse.com \
    --to=jbeulich@suse.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=dylangerdaly@protonmail.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.