[Bug 252275] pci: Bad tailq NEXT(0xffffffff81cde660->tqh_last) != NULL when using custom patch
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Dec 29 22:34:07 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252275
Bug ID: 252275
Summary: pci: Bad tailq NEXT(0xffffffff81cde660->tqh_last) !=
NULL when using custom patch
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: neel at neelc.org
I have a custom patch which I believe is required to use NVMe for a new laptop
(HP Spectre x360 13t-aw200), and I get an kernel panic whenever I use the
patch. This Spectre (and probably most 11th gen Intel "Evo" laptops) force NVMe
RAID.
The panic is: Bad tailq NEXT(0xffffffff81cde660->tqh_last) != NULL
Full trace: https://imgur.com/a/XUQksOi
The custom patch is:
--- a/sys/dev/vmd/vmd.c
+++ b/sys/dev/vmd/vmd.c
@@ -66,13 +66,20 @@ struct vmd_type {
#define INTEL_VENDOR_ID 0x8086
#define INTEL_DEVICE_ID_VMD 0x201d
#define INTEL_DEVICE_ID_VMD2 0x28c0
+#define INTEL_DEVICE_ID_VMD3 0x9a0b
static struct vmd_type vmd_devs[] = {
{ INTEL_VENDOR_ID, INTEL_DEVICE_ID_VMD, "Intel Volume Management
Device" },
{ INTEL_VENDOR_ID, INTEL_DEVICE_ID_VMD2, "Intel Volume Management
Device" },
+ { INTEL_VENDOR_ID, INTEL_DEVICE_ID_VMD3, "Intel Volume Management
Device" },
{ 0, 0, NULL }
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list