Pi 5: NVMe IG5216 stays "CSTS=0x0" after brcm-pcie re-probe on 6.18, recovers on 6.12

Open
#912 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
shell
Domain
embedded-iot

Research direction

Start by comparing the attached kernel serial logs and the reported configurations: Pi 5 Rev 1.1, BOOT_ORDER=0xf4166, PCIE_PROBE=1, and bootloader versions 2026/09/25 and 2026/05/26. The issue points to raspberrypi/linux#7716 for kernel-side investigation and relates the failure to bootloader access followed by PCIe re-probing. Done means identifying why the NVMe controller remains at CSTS=0x0 on 6.18 and determining a bootloader-side fix or next diagnostic step; this needs PCIe and NVMe domain knowledge.

Written by the indexing model from the issue text.

Description

Describe the bug

Apacer AS2280P4U 256GB (Innogrit IG5216, 1dbe:5216, FW 2.O.3.1G). The bootloader boots from it fine, but the kernel then finds the controller stuck:

brcm-pcie 1000110000.pcie: link up, 5.0 GT/s PCIe x1 (!SSC)
nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0    (after ~50 s)

Only a port re-probe recovers it (on 6.12; on 6.18 not at all). When the bootloader doesn't touch the drive (SD boot), this never happens.
Same pattern as #859, different controller.

Pi 5 Rev 1.1 + [carrier board], bootloader 2026/09/25 and 2026/05/26 (same result), BOOT_ORDER=0xf4166, PCIE_PROBE=1.
Kernel serial logs attached. Kernel side: raspberrypi/linux#7716.

Steps to reproduce the behaviour
  1. Pi 5 + [carrier board] + Apacer AS2280P4U 256GB with Raspberry Pi OS on it.
  2. BOOT_ORDER=0xf4166, PCIE_PROBE=1.
  3. Power on → bootloader loads kernel/initramfs from NVMe → kernel reports the above.
Device (s)

Raspberry Pi 5

Bootloader configuration.
Bootloader version and configuration

Tested with 2026/09/25 (1accd665) and 2026/05/26 (086b83e3) – same result.

[all]
BOOT_UART=1
BOOT_ORDER=0xf4166
PCIE_PROBE=1
NET_INSTALL_AT_POWER_ON=1
System

No response

Bootloader logs

No response

USB boot

No response

NVMe boot

No response

Network (TFTP boot)

No response

Dominant language
Shell
Stars
1.5k
Forks
246
Avg merge
9h 7m
Merged PRs (30d)
16

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/rpi-eeprom

All issues in raspberrypi/rpi-eeprom

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.