Re: Ryzen 6000 (Mobile)

[Dylanger Daly <dylangerdaly@xxxxxxxxxxxxxx>]

I'd focus on the booting issues first. And I guess you can take a video

of that (assuming that a single screenshot likely isn't going to be

enough), possibly with "vga=keep" in place (albeit that introduces

extra slowness)?

There's also the option of using an EHCI debug port for the serial

console, but this requires (a) a special cable and (b) the system

designers not having inserted any hubs between the controller and

the connector.

Do you know if it's possible to have `console=vga vga=keep` and specify a secondary monitor? This would be very useful if I could have Xen log via a secondary monitor, in any case I'll record a video today. I can't seem to get anything useful out of /var/log/xen/console/hypervisor.log, I assume this log file isn't written to on a 'live' basis.

I would assume AMD has disabled any sort of debugging/NIDnT/CCD, surprisingly or unsurprisingly it's easier to debug Chromebooks with their CCD USB-C cables.

Ok, these sound like two different things.  One is dom0 failing to boot, and one is the hang/reset when starting the VMs.

Lets start with the dom0 problem first.  The link you provide suggests a credit2 bug.  Does dom0 boot if you pass `sched=credit` on the command line, in place of `dom0_max_vcpus=1 dom0_vcpus_pin` ?

Yes, this is correct, I think the first problem is an AMD 6000 Series CPU issue, as others have reported this same first issue: https://github.com/QubesOS/qubes-issues/issues/7570 (having to add `dom0_max_vcpus=1 dom0_vcpus_pin`)

I believe the second issue could be platform specific, that being a UEFI Option relating to the scheduler or something else causing the device to hang, anecdotally others that have the same-ish CPU aren't having this issue, so it could be specific to the Lenovo Yoga Slim 7 Pro X (Gen 7).

Issue #1 seems to be common with newer AMD Ryzen Mobile CPUs

Issue #2 seems to be Lenovo specific, I've tried limiting other domU's to 1 vcpu to no avail, I haven't tried pinning a vcpu to a domU yet.

Unfortunately I tried adding `sched=credit` in place of the pinning config and dom0 didn't come up to ask for a LUKs password. Dom0 does indeed boot, it just doesn't make it past the early stage of kernel setup.

Cheers, Dylanger