I can confirm that the Intel VMD Bus Offset Setting (3) issue reported
here is also reproducible on another MSI Arrow Lake-HX platform, the
**MSI Raider 16 HX B2WI**.
### Hardware configuration
- **Laptop:** MSI Raider 16 HX B2WI
- **CPU:** Intel Core Ultra 9 275HX (Arrow Lake-HX)
- **GPU:** NVIDIA GeForce RTX 5080 Laptop GPU
- **BIOS:** E2651IMS.305 (2026-10-02)
- **Boot mode:** UEFI
- **Secure Boot:** Enabled
- **Intel VMD:** Enabled
- **VMD PCI address:** `0000:00:0e.0`
- **VMD PCI ID:** `8086:ad0b`
- **Subsystem ID:** `1462:14fb`
Internal NVMe storage:
- **Micron 2500 1 TB:** Existing Windows system drive
- **Samsung 990 PRO 2 TB:** Separate, unpartitioned SSD intended for Ubuntu
Both SSDs are correctly detected in the BIOS under Intel Rapid Storage
Technology as independent **Non-RAID Physical Disks**.
Windows also detects both SSDs correctly.
### Ubuntu environment
- **Ubuntu Live environment:** Ubuntu 24.04.5 LTS installation USB
- **Kernel reported by `uname -r`:** `7.0.0-31-generic`
- **Secure Boot:** Enabled
- **Intel VMD:** Enabled
The Ubuntu Live desktop boots successfully, but neither internal NVMe
SSD is detected.
### Reproduction
1. Boot Ubuntu from the installation USB in UEFI mode.
2. Select the Live environment without installing Ubuntu.
3. Run:
```bash
lsblk -o NAME,MODEL,SIZE,TYPE,FSTYPE,MOUNTPOINTS
```
Only the USB installation medium and Live filesystem devices are
visible. Neither internal NVMe SSD is enumerated.
4. Check the kernel log:
```bash
sudo dmesg | grep -Ei 'vmd|nvme|pcie'
```
The following error is reported:
```text
vmd 0000:00:0e.0: Unknown Bus Offset Setting (3)
```
5. Check the VMD PCI controller:
```bash
lspci -nnk -s 00:0e.0
```
Output:
```text
00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management
Device NVMe RAID Controller [8086:ad0b]
DeviceName: Onboard - Other
Subsystem: Micro-Star International Co., Ltd. [MSI] Volume Management
Device NVMe RAID Controller [1462:14fb]
Kernel modules: vmd
```
No `Kernel driver in use: vmd` line is reported.
6. Attempting to load the module manually:
```bash
sudo modprobe vmd
sudo udevadm settle
```
does not resolve the issue.
7. Checking for NVMe devices:
```bash
ls -l /dev/nvme*
```
confirms that no NVMe device nodes are present.
### Expected behavior
Both internal NVMe SSDs should be enumerated by Linux through the Intel
VMD controller, allowing Ubuntu to access the separate Samsung SSD.
### Actual behavior
The VMD controller is detected on the PCI bus, but its initialization
fails with `Unknown Bus Offset Setting (3)`. Neither internal NVMe SSD
becomes available.
The behavior matches the first issue described in this bug report.
### Additional observations
- Both SSDs are detected correctly by the BIOS and Windows.
- Neither SSD belongs to an Intel RST RAID volume.
- The BIOS exposes a global VMD enable/disable setting, but no per-SSD VMD
configuration option was identified.
- VMD has not been disabled, to preserve the existing Windows storage
configuration.
- No Linux installation or partitioning changes have been performed.
- The issue occurs directly in the Live environment, before installation.
**I have not tested the proposed VMD patches or the ARL004 interrupt-
ordering workaround.** Since the NVMe devices are not enumerated, I
cannot confirm whether the second issue involving NVMe completion
timeouts is also present on this system.
This report provides an additional reproduction of the Bus Offset
Setting (3) failure on an MSI Arrow Lake-HX laptop, with a different MSI
subsystem ID (`1462:14fb`) and two different NVMe SSD models.
I would be interested in testing an officially supported Ubuntu kernel
containing both fixes once available.
Thank you for investigating this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2166325
Title:
Intel VMD 8086:ad0b: Bus Offset 3 prevents NVMe enumeration and ARL004
causes NVMe completion stalls
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166325/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
