Kernel 5.1.16-v7l+ unable to reboot Pi4B

Open
#3,085 3 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
Mostly clear
Activity status
Stale
Tech stack
c

Research direction

Start by reproducing the reboot failure on a Pi4B with kernel 5.1.16-v7l+, using the listed sudo reboot steps and collecting the requested system information. No source file or test is named; done means the processor completes reboot instead of hanging during the reboot sequence.

Written by the indexing model from the issue text.

Description

Waiting for external input

Describe the bug
Kernel is unable to reboot the processor of the pi4b

To reproduce

  1. use kernel 5.1.16-v7l+
  2. sudo reboot
  3. system goes through reboot sequence
  4. kernel hangs trying to reboot

Expected behaviour
kernel reboots the processor

Actual behaviour
kernel does not reboot the processo

System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:

  • Which model of Raspberry Pi?
    Pi4B
  • Which OS and version (cat /etc/rpi-issue)?
    Raspberry Pi reference 2019-06-20
    Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 150e25c4f8123a4c9c63e8dca1b4737fa6c1135c, stage2
  • Which firmware version (vcgencmd version)?
    Jun 20 2019 16:04:31
    Copyright (c) 2012 Broadcom
    version 407b1da8fa3d1a7108cb1d250f5064a3420d2b7d (clean) (release) (start)
  • Which kernel version (uname -a)?
    Linux 0a9d2112 5.1.16-v7l+ #3 SMP Sun Jul 7 09:44:08 BST 2019 armv7l GNU/Linux
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.