The Pi automatically restarts but fail and all the associated network devices go down

Open
#5,261 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux, raspberry-pi

Research direction

Start by reviewing log.zip together with the reported Raspberry Pi 3 B+ system details, kernel version, and Bluetooth stress-test scenario. Determine whether the failed automatic restart and network-device outage can be reproduced and isolated; done means the system recovers without power cycling and the relevant regression is verified.

Written by the indexing model from the issue text.

Description

Describe the bug

The Pi automatically restarts but fail and all the associated network devices go down, it can be used only after being powered on and off again

Steps to reproduce the behaviour

This was an occasional occurrence in previous tests, but recently a certain occurrence was found: BLE Host received ADV from all surrounding Bluetooth devices and then only did data transfer using Bluetooth connection during stress tests

Device (s)

Raspberry Pi 3 Mod. B+

System

pi@raspberrypi:~ $ cat /etc/rpi-issue
Raspberry Pi reference 2020-02-13
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 5f884374b6ac6e155330c58caa1fb7249b8badf1, stage4

pi@raspberrypi:~ $ vcgencmd version
Apr 30 2021 13:47:07
Copyright (c) 2012 Broadcom
version d7f29d96450abfc77cd6cf011af1faf1e03e5e56 (clean) (release) (start)

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.10.17-v7+ #1414 SMP Fri Apr 30 13:18:35 BST 2021 armv7l GNU/Linux

Logs

log.zip

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.