Wifi fails under heavy load and requires reboot (mmc1: Timeout waiting for hardware interrupt)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c, linux
- Domain
- embedded-iot, networking, operating-systems
Research direction
Review the system information at https://pastebin.com/TxW2rkR8 and logs at https://pastebin.com/GNxF3A9h, starting with the mmc1: Timeout waiting for hardware interrupt message and the conditions around sustained webcam traffic. Reproduce the failure under heavy Wi-Fi load and compare the logs and recovery behavior with the expected uninterrupted connection.
Written by the indexing model from the issue text.
Description
Describe the bug
I'm running octoprint on my Raspberry with a webcam and connecting in headless mode over wifi. If I watch the webcam stream from octoprint, which puts the wifi under heavy load, after a while (random, can be minutes, can be hours), the wifi cuts out. Nothing but a reboot can bring it back. Currently I'm using the octopi image, but I had the same issue using the official Raspbian image.
To reproduce
- Connect to a wifi
- Put the wifi under heavy load for an extended period of time
- Sometimes the wifi stops working, does not happen every time
Expected behaviour
Wifi keeps working
Actual behaviour
Wifi stops working, device is unresponsive. Even with a screen and keyboard connected, I was unable to bring the device down (ifdown didn't find the device anymore), ifconfig still listed it but not connected, trying to scan for wifi networks let to a timeout.
System
https://pastebin.com/TxW2rkR8
Logs
https://pastebin.com/GNxF3A9h
Additional info
I have a second MicroSD card I can use to run tests on, if that would help
- 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 ·