All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216498] New: Can't load kvmgt anymore (works with 5.18)
Date: Sat, 17 Sep 2022 18:46:52 +0000	[thread overview]
Message-ID: <bug-216498-28872@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=216498

            Bug ID: 216498
           Summary: Can't load kvmgt anymore (works with 5.18)
           Product: Virtualization
           Version: unspecified
    Kernel Version: 5.19
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: dion@inhex.net
        Regression: No

Created attachment 301820
  --> https://bugzilla.kernel.org/attachment.cgi?id=301820&action=edit
5.19 dmesg with warning, GVT-g doesn't work

I'm using Intel GVT-g actively and it was very stable on older kernels
including 5.18.x.

But after updating to 5.19 it doesn't work anymore. I'm sure that it isn't
related to hardware change / bios update. It still works if I reboot to older
5.18 kernel. 


I'm getting followed in dmesg:

[   92.987534] ------------[ cut here ]------------
[   92.987538] assign a handler to a non-tracked mmio 4ab8
[   92.987555] WARNING: CPU: 0 PID: 3660 at
drivers/gpu/drm/i915/gvt/handlers.c:124 setup_mmio_info.constprop.0+0xd5/0x100
[kvmgt]

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-09-17 18:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 18:46 bugzilla-daemon [this message]
2022-09-17 18:47 ` [Bug 216498] Can't load kvmgt anymore (works with 5.18) bugzilla-daemon
2022-09-17 18:48 ` bugzilla-daemon
2022-09-19 11:04 ` bugzilla-daemon
2022-09-20 15:00 ` bugzilla-daemon

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=bug-216498-28872@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=kvm@vger.kernel.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.