Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #92909

Bug#1135235: linux-image-6.19.13+deb14-amd64: Reoccuring host crash "Invalid SPTE change" with gaming win kvm/qemu guest and device passthrough

Path csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod
From Sean Christopherson <seanjc@google.com>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1135235: linux-image-6.19.13+deb14-amd64: Reoccuring host crash "Invalid SPTE change" with gaming win kvm/qemu guest and device passthrough
Date Fri, 05 Jun 2026 23:50:01 +0200
Message-ID <N2KAp-aBka-7@gated-at.bofh.it> (permalink)
References <MPiBX-1lGE-1@gated-at.bofh.it> <MVJJ7-5Pih-1@gated-at.bofh.it> <MW6w1-64AA-5@gated-at.bofh.it> <N1Uiv-a1Hf-5@gated-at.bofh.it> <MPiBX-1lGE-1@gated-at.bofh.it> <N1Uiv-a1Hf-5@gated-at.bofh.it>
X-Mailbox-Line From debian-bugs-dist-request@lists.debian.org Fri Jun 5 21:43:08 2026
Old-Return-Path <debbugs@buxtehude.debian.org>
X-Spam-Flag NO
X-Spam-Score -0.55
Reply-To Sean Christopherson <seanjc@google.com>, 1135235@bugs.debian.org
Resent-To debian-bugs-dist@lists.debian.org
Resent-Cc debian-kernel@lists.debian.org
X-Debian-Pr-Message followup 1135235
X-Debian-Pr-Package src:linux
X-Debian-Pr-Keywords moreinfo
X-Debian-Pr-Source linux
X-Gm-Message-State AOJu0Yz+/VQWt4VnFXX5USvldW1rsxeHYlT1wo+T5M5onbiEP8fhJSZ2 WCJHiLw1LYqzdlCZ+3gdzhBbq6WGfxhIoS/8PnsejGN09jR+zOloV3pMHhdqfM0qrM15CQyir5S CNOjvuQ==
X-Received from pfjd3.prod.google.com ([2002:a05:6a00:2443:b0:842:33b9:bdf8]) (user=seanjc job=prod-delivery.src-stubby-dispatcher) by 2002:a05:6a00:4098:b0:842:38c7:9925 with SMTP id d2e1a72fcca58-842b0e3367emr5830537b3a.2.1780695723712; Fri, 05 Jun 2026 14:42:03 -0700 (PDT)
MIME-Version 1.0
Content-Type text/plain; charset="us-ascii"
X-Debian-Message from BTS
X-Mailing-List <debian-bugs-dist@lists.debian.org> archive/latest/1974242
List-ID <debian-bugs-dist.lists.debian.org>
List-URL <https://lists.debian.org/debian-bugs-dist/>
Approved robomod@news.nic.it
Lines 43
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Cc 1135235@bugs.debian.org
X-Original-Date Fri, 5 Jun 2026 21:42:03 +0000
X-Original-Message-ID <aiNCq17MbKfs3hGy@google.com>
X-Original-References <177749023441.304242.8022456530166067549.reportbug@mspc2024debian.lan> <177902420697.2035014.8796825668567298024@eldamar.lan> <agsXnbjjKdrq8e-T@google.com> <db210e1d-0d3b-4501-89c5-de7d7de66b03@0in.de> <177749023441.304242.8022456530166067549.reportbug@mspc2024debian.lan> <db210e1d-0d3b-4501-89c5-de7d7de66b03@0in.de>
Xref csiph.com linux.debian.bugs.dist:1297090 linux.debian.kernel:92909

Cross-posted to 2 groups.

Show key headers only | View raw


On Wed, Jun 03, 2026, Maximilian Senftleben wrote:
> Hi,
> 
> sorry for the late reply, took me a while to first built the kernel with
> that options and then actually find time to play long enough.
> 
> If I did everything correctly, then I build 7.0.7 with
> - CONFIG_VMAP_STACK=y
> - CONFIG_KASAN=y
> 
> I did not get it to crash on that built kernel yet, however I booted
> 7.0.9+deb14-amd64 once, and after playing a while got a crash again.
> 
> I will try using the built kernel next week to see if I can get it to crash
> as well.

Hmm, can you try 7.0.9 with KASAN?  Or even just a 7.0.9 kernel that you built?
It's possible there's a bug somewhere between 7.0.7 and 7.0.9. 

> Or do I have to look somewhere else if kasan is active?

KASAN reports issues in dmesg.  But generally speaking, if the error is bad
enough to crash the kernel, you'll see a KASAN splat *and* a crash.

> On 18.05.26 15:43, Sean Christopherson wrote:
> > Odds are very good this is due to host memory corruption, and is not a bug in
> > KVM's MMU.  We (Google) had a period of time where our kernel was triggering stack
> > overflows if a networking IRQ hit at just the right/wrong time, and whenever the
> > overflow wandered into KVM page tables, it would result in failures like these.
> > I got quite familiar with the signature :-)
> Not sure if it could be something else, however I at least run memtest for
> ~12h without problems.
> > If you aren't already, can you try running with CONFIG_VMAP_STACK=y?  Stack
> > overflow doesn't seem likely in this case since the gfn would put the SPTE in the
> > middle of the page table, but it's easy enough to rule out.
> > 
> > The other thing to try would be to run with CONFIG_KASAN=y.  That might make your
> > gaming quite miserable, but if this is indeed due to a rogue write, it's the best
> > shot for catching the culprit.
> 
> 
> Regards
> 

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1135235: linux-image-6.19.13+deb14-amd64: Reoccuring host crash "Invalid SPTE change" with gaming win kvm/qemu guest and device passthrough Salvatore Bonaccorso <carnil@debian.org> - 2026-05-17 15:30 +0200
  Bug#1135235: linux-image-6.19.13+deb14-amd64: Reoccuring host crash "Invalid SPTE change" with gaming win kvm/qemu guest and device passthrough Sean Christopherson <seanjc@google.com> - 2026-05-18 15:50 +0200
    Bug#1135235: linux-image-6.19.13+deb14-amd64: Reoccuring host crash "Invalid SPTE change" with gaming win kvm/qemu guest and device passthrough Maximilian Senftleben <kernel@0in.de> - 2026-06-03 16:00 +0200
      Bug#1135235: linux-image-6.19.13+deb14-amd64: Reoccuring host crash "Invalid SPTE change" with gaming win kvm/qemu guest and device passthrough Sean Christopherson <seanjc@google.com> - 2026-06-05 23:50 +0200
        Bug#1135235: linux-image-6.19.13+deb14-amd64: Reoccuring host crash "Invalid SPTE change" with gaming win kvm/qemu guest and device passthrough Maximilian Senftleben <kernel@0in.de> - 2026-06-24 22:10 +0200
          Bug#1135235: linux-image-6.19.13+deb14-amd64: Reoccuring host crash "Invalid SPTE change" with gaming win kvm/qemu guest and device passthrough Sean Christopherson <seanjc@google.com> - 2026-06-25 18:20 +0200

csiph-web