Issues on Zen4 (hw12) runner

["Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>]

[-- Attachment #1: Type: text/plain, Size: 2970 bytes --]

Hi,

I wanted to post another revision of the series adding hw12 runner,
hoping that all known issues are fixed now, but unfortunately there is
still something broken. I've rebased my series on top of staging
(ed9488a0d) and got this pipeline:

https://gitlab.com/xen-project/people/marmarek/xen/-/pipelines/1807819142
(note due to some added debugging, some tests are incorrectly marked as
success even if they failed...)

1. USB ethernet doesn't work on PVH dom0: https://gitlab.com/xen-project/people/marmarek/xen/-/jobs/9978694739
There supposed to be an USB ethernet device connected to the USB
controller at c3:00.4. In the PV dom0 case it's detected as:

    [    3.911555] usb 7-1.4: new high-speed USB device number 3 using xhci_hcd
    [    4.004201] usb 7-1.4: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
    [    4.004675] usb 7-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
    [    4.005079] usb 7-1.4: Product: USB 10/100/1000 LAN
    [    4.005349] usb 7-1.4: Manufacturer: Realtek
    [    4.005599] usb 7-1.4: SerialNumber: 684D35

But it's not there on PVH. The USB controller itself is detected, just
not device(s) connected to it. This applies to other controllers too
(there should be about 3 or 4 other USB devices - none of them show up).

2. There is a bunch of "unhandled memory read" errors during PVH dom0
startup: https://gitlab.com/xen-project/people/marmarek/xen/-/jobs/9978694739

    (XEN) [    4.026323] arch/x86/hvm/emulate.c:417:d0v0 unhandled memory read from 0xfedc0020 size 1
    (XEN) [    4.026789] arch/x86/hvm/emulate.c:417:d0v0 unhandled memory read from 0xfedc0021 size 1
    (XEN) [    4.027247] arch/x86/hvm/emulate.c:417:d0v0 unhandled memory read from 0xfedc0020 size 1
    (XEN) [    4.027671] arch/x86/hvm/emulate.c:417:d0v0 unhandled memory read from 0xfedc0021 size 1
    ...

This repeats several times. Could be related to the USB issue above?

There is also, likely related:

    (XEN) [    5.002036] arch/x86/hvm/vmsi.c:845:d0v9 0000:c1:00.1: PIRQ 2484: unsupported address 0
    (XEN) [    5.002365] arch/x86/hvm/vmsi.c:845:d0v9 0000:c1:00.1: PIRQ 2484: unsupported address 0
    (XEN) [    5.002693] arch/x86/hvm/vmsi.c:845:d0v9 0000:c1:00.1: PIRQ 2484: unsupported address 0

3. Sometimes it fails to print anything on the console, like here: https://gitlab.com/xen-project/people/marmarek/xen/-/jobs/9977761447
This is likely some boot issue before Xen starts (possibly the power button
is pressed to early). Anyway, I need to fix it before adding the runner.

4. There is a bunch of unknown MSR accesses, but that's likely to be
expected. For example:

    (XEN) [    6.010446] arch/x86/pv/emul-priv-op.c:1017:d0v11 RDMSR 0xc00102b0 unimplemented
    (XEN) [    6.010798] arch/x86/pv/emul-priv-op.c:1017:d0v0 RDMSR 0xc00102b1 unimplemented


-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]