Re: Ryzen 6000 (Mobile)

[Jan Beulich <jbeulich@suse.com>]

On 15.08.2022 13:07, Dylanger Daly wrote:
> It would appear this issue isn't specific to the Lenovo Yoga Slim 7 ProX, someone else in the Qubes community is having the same issue (https://github.com/QubesOS/qubes-issues/issues/7620#issuecomment-1209114810)
> 
> Can anyone shed some light on what possibly might be making a Xen 4.14 Hypervisor crash after attempting to start a domU?

Well, to shed light on what's going on we need logged output, which I
understand isn't easy with laptops. Simply trying to guess what's
going wrong isn't very likely to lead us anywhere.

> Dom0 start's just fine, it 'feels' like a memory violation or DMA/IOMMU issue, because the VM does successfully start, however 1 or 2 seconds after it successfully boot the mouse (in dom0) locks up for 2-3 seconds and the entire device resets.

In the Qubes report there's talk of a 5s delay, which makes me assume
Xen crashes (or Dom0 reports itself crashed to Xen), which - unless
overridden - would result in a 5s delay (after logging state) until a
reboot would be attempted. This aspect could be verified by passing
"noreboot" on the Xen command line, in which case the device shouldn't
try to reboot itself at all. But all we'd learn from this is that
there's _some_ form of a crash (but not e.g. a triple fault), still
without knowing any details.

Jan

> I can't seem to get any logs at all, xen's console, dom0 dmesg and domU's dmesg all appear to be fine in the lead up to the crash. I assume no one has had a chance to use Xen on Ryzen 6000 (Rembrandt) yet due to the fact it's hard to get your hands on with the chip shortage etc.
> 
> I'm hoping it's something that can be fixed with a cmdline flag, it's very frustrating having this shiny new laptop sitting on my desk :P
> 
> Cheers all