2021-04-13 05:48:19

by Alex Williamson

[permalink] [raw]
Subject: Regression: gvt: vgpu 1: MI_LOAD_REGISTER_MEM handler error


Running a Windows guest on a i915-GVTg_V4_2 from an HD 5500 IGD on
v5.12-rc6 results in host logs:

gvt: vgpu 1: lrm access to register (20c0)
gvt: vgpu 1: MI_LOAD_REGISTER_MEM handler error
gvt: vgpu 1: cmd parser error
0x0
0x29

gvt: vgpu 1: scan wa ctx error
gvt: vgpu 1: failed to submit desc 0
gvt: vgpu 1: fail submit workload on ring rcs0
gvt: vgpu 1: fail to emulate MMIO write 00002230 len 4

The guest goes into a boot loop triggering this error before reaching
the desktop and rebooting. Guest using Intel driver 20.19.15.5171
dated 11/4/2020 (from driver file 15.40.5171).

This VM works well with the same guest and userspace software stack on
Fedora's kernel 5.11.11-200.fc33.x86_64. Thanks,

Alex


2021-04-13 12:27:57

by Alex Williamson

[permalink] [raw]
Subject: Re: Regression: gvt: vgpu 1: MI_LOAD_REGISTER_MEM handler error

On Mon, 12 Apr 2021 10:32:14 -0600
Alex Williamson <[email protected]> wrote:

> Running a Windows guest on a i915-GVTg_V4_2 from an HD 5500 IGD on
> v5.12-rc6 results in host logs:
>
> gvt: vgpu 1: lrm access to register (20c0)
> gvt: vgpu 1: MI_LOAD_REGISTER_MEM handler error
> gvt: vgpu 1: cmd parser error
> 0x0
> 0x29
>
> gvt: vgpu 1: scan wa ctx error
> gvt: vgpu 1: failed to submit desc 0
> gvt: vgpu 1: fail submit workload on ring rcs0
> gvt: vgpu 1: fail to emulate MMIO write 00002230 len 4
>
> The guest goes into a boot loop triggering this error before reaching
> the desktop and rebooting. Guest using Intel driver 20.19.15.5171
> dated 11/4/2020 (from driver file 15.40.5171).
>
> This VM works well with the same guest and userspace software stack on
> Fedora's kernel 5.11.11-200.fc33.x86_64. Thanks,

Bisected to:

commit f18d417a57438498e0de481d3a0bc900c2b0e057
Author: Yan Zhao <[email protected]>
Date: Wed Dec 23 11:45:08 2020 +0800

drm/i915/gvt: filter cmds "srm" and "lrm" in cmd_handler

do not allow "srm" and "lrm" except for GEN8_L3SQCREG4 and 0x21f0.

Cc: Colin Xu <[email protected]>
Cc: Kevin Tian <[email protected]>
Signed-off-by: Yan Zhao <[email protected]>
Signed-off-by: Zhenyu Wang <[email protected]>
Link: http://patchwork.freedesktop.org/patch/msgid/[email protected]
Reviewed-by: Zhenyu Wang <[email protected]>

2021-04-13 12:28:13

by Zhenyu Wang

[permalink] [raw]
Subject: Re: Regression: gvt: vgpu 1: MI_LOAD_REGISTER_MEM handler error

On 2021.04.12 19:23:47 -0600, Alex Williamson wrote:
> On Mon, 12 Apr 2021 10:32:14 -0600
> Alex Williamson <[email protected]> wrote:
>
> > Running a Windows guest on a i915-GVTg_V4_2 from an HD 5500 IGD on
> > v5.12-rc6 results in host logs:
> >
> > gvt: vgpu 1: lrm access to register (20c0)
> > gvt: vgpu 1: MI_LOAD_REGISTER_MEM handler error
> > gvt: vgpu 1: cmd parser error
> > 0x0
> > 0x29
> >
> > gvt: vgpu 1: scan wa ctx error
> > gvt: vgpu 1: failed to submit desc 0
> > gvt: vgpu 1: fail submit workload on ring rcs0
> > gvt: vgpu 1: fail to emulate MMIO write 00002230 len 4
> >
> > The guest goes into a boot loop triggering this error before reaching
> > the desktop and rebooting. Guest using Intel driver 20.19.15.5171
> > dated 11/4/2020 (from driver file 15.40.5171).
> >
> > This VM works well with the same guest and userspace software stack on
> > Fedora's kernel 5.11.11-200.fc33.x86_64. Thanks,
>
> Bisected to:

Looks we didn't hit this one on Broadwell with recent testing. I'll double
check, maybe Broadwell missed something after our cmd parser rework.

Thanks for reporting!

>
> commit f18d417a57438498e0de481d3a0bc900c2b0e057
> Author: Yan Zhao <[email protected]>
> Date: Wed Dec 23 11:45:08 2020 +0800
>
> drm/i915/gvt: filter cmds "srm" and "lrm" in cmd_handler
>
> do not allow "srm" and "lrm" except for GEN8_L3SQCREG4 and 0x21f0.
>
> Cc: Colin Xu <[email protected]>
> Cc: Kevin Tian <[email protected]>
> Signed-off-by: Yan Zhao <[email protected]>
> Signed-off-by: Zhenyu Wang <[email protected]>
> Link: http://patchwork.freedesktop.org/patch/msgid/[email protected]
> Reviewed-by: Zhenyu Wang <[email protected]>
>


Attachments:
(No filename) (1.78 kB)
signature.asc (201.00 B)
Download all attachments