CM5 Lite excessive reboot/shutdown delay if SD card is not present

Open
#7,014 2 comments 0 reactions 0 assignees View on GitHub

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
c, linux

Research direction

Start by reviewing the attached raspinfo.log and the reproduction steps on a CM5 Lite with an NVMe drive and no SD card. Reproduce the delayed reboot with the listed systemd kernel logging options; done means identifying and fixing the cause of the 10–80 second Powering off delay, with shutdown and reboot completing promptly.

Written by the indexing model from the issue text.

Description

Describe the bug

Discussed on this forum post: https://forums.raspberrypi.com/viewtopic.php?t=383051

A device using a CM5 Lite (in my case, HALPI2) and an NVMe will have a delay of up to 80 seconds at shutdown or reboot if an SD card is not inserted. With an SD card inserted (doesn't need to be formatted, just present) shutdowns are immediate.

Steps to reproduce the behaviour

With a CM5 Lite inserted on a HALPI2 or (as reported in the forum thread) the standard CM5 IO Board:

  • Flash on OS on an NVMe drive
  • Ramp up the kernel logging: systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 ignore_loglevel
  • Issue command: sudo reboot
  • The system will rapidly perform other reboot steps and then remain stuck in "Powering off" for a long time.
Device (s)

Raspberry Pi CM5 Lite

System

Raspinfo output attached.

raspinfo.log

Logs

Didn't have UART logging set up, so there's just a bad photo. The system is stuck here for 10-80 seconds or even more.

Image

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

  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/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.