Raspberry Pi boots up too fast to enumerate all PCIe devices
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- linux, raspberry-pi
- Domain
- embedded-iot, operating-systems
Research direction
Start with the CM5 reproduction using multiple graphics cards behind a PCIe switch and compare lspci results across the kernel versions mentioned. Check the historical config.txt boot_delay reference and determine whether device timing explains the missing enumeration; done means the cause is confirmed or a specific kernel/config change is defined and validated.
Written by the indexing model from the issue text.
Description
Describe the bug
Often when testing complex multi-device PCIe scenarios behind a switch, one or more devices won't fully enumerate, and debugging why is a little perplexing.
For example, running four RTX 5000 GPUs behind a PCIe switch often results in one or all of them not showing up: https://github.com/geerlingguy/raspberry-pi-pcie-devices/issues/791
I've also noticed this sometimes with just two or even sometimes one PCIe device, since I test a lot of exotic cards, which may need a little time to get going. At least that's my theory.
This is definitely an edge case, but it would be nice to have a means to debug it and at least confirm the theory.
There used to be a boot_delay option in config.txt which might've helped with this, but that is not present anymore.
Steps to reproduce the behaviour
- Plug in multiple modern graphics cards behind a PCIe switch connected to the Pi's external PCIe lane.
- Boot Raspberry Pi OS.
- Run
lspci, and sometimes only one or zero devices are listed.
Device (s)
Raspberry Pi CM5
System
jgeerling@cm5:~ $ cat /etc/rpi-issue
Raspberry Pi reference 2025-11-24
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 6e49e5317491c159c114681ddb4ac0623d855611, stage4
jgeerling@cm5:~ $ uname -a
Linux cm5 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 GNU/Linux
(But I've also been testing on 6.17 and 6.18 with various kernels...)
Logs
No response
Additional context
No response
- Dominant language
- C
- Stars
- 13.2k
- Forks
- 5.5k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 21
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7415 · 2 comments · 1 reaction ·
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace app Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raspberrypi/linux#7399 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
raspberrypi/linux#7357 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7054 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/linux#7634 · 8 comments · 1 reaction ·
All issues in raspberrypi/linux
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·