From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 221828] Windows 11 blue screen 0xc0000185 when using disk cache none on newer kernels
Date: Tue, 04 Aug 2026 09:11:25 +0000 [thread overview]
Message-ID: <bug-221828-28872-RnnomOtH41@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221828-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221828
The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |regressions@leemhuis.info
--- Comment #1 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
(In reply to Samuil P. from comment #0)
> Is this a known issue?
Hard to say. Wonder if it might be the problems this fixes:
https://lore.kernel.org/all/20260720201057.1862857-1-kbusch@meta.com/
Or just a timing issue.
Maybe a developer will show up with an idea what's wrong. But if that doesn't
happen in the next few days you most likely will have to run a git bisection to
see where the problem is coming from:
https://docs.kernel.org/admin-guide/bug-bisect.html
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-08-04 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 13:24 [Bug 221828] New: Windows 11 blue screen 0xc0000185 when using disk cache none on newer kernels bugzilla-daemon
2026-08-03 13:27 ` [Bug 221828] " bugzilla-daemon
2026-08-03 13:28 ` bugzilla-daemon
2026-08-04 9:11 ` bugzilla-daemon [this message]
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-221828-28872-RnnomOtH41@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.