Network not working anymore though ethernet after heavy load RPi 4b

Open
#4,054 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, linux

Research direction

Start by reviewing the linked DMESG and RASPINFO, then reproduce the Ethernet failure on the Raspberry Pi 4B after heavy load using the reported kernel version. The issue is done when the cause is identified, Ethernet remains usable alongside the reported server workload, and the result is verified with connection testing.

Written by the indexing model from the issue text.

Description

Describe the bug
I cannot use ethernet anymore since I get IP but no connection at all while no problems on Wifi.

To reproduce
List the steps required to reproduce the issue.

Expected behaviour
I wanted to use my device as "server" attached to a external drive and with transmission, SMB and DLNA connected through ethernet port to get better speed than wireless.

Actual behaviour
Im using wifi while I find some fix for this but its way slower.

System
RASPINFO https://pastebin.pl/view/76187585

  • Which model of Raspberry Pi? PI 4b
  • Which OS and version (cat /etc/rpi-issue)? Linux raspberrypi 5.4.79-v7l+ #1373
  • Which firmware version (vcgencmd version)? version ab1181cc0cb6df52bfae3b1d3fef0ce7c325166c (clean) (release) (start)
  • Which kernel version (uname -a)? Linux raspberrypi 5.4.79-v7l+

Logs
DMESG https://pastebin.pl/view/53644379

Additional context
Right now I havent it connected through ethernet since I use RPi trough ssh and a small touchscreen and If I plug ethernet I cannot use SSH, doesnt matter if im also connected to wifi, I cannot connect overall.

I dont know what else should I upload because Im new at this so thanks for the help and my apologies for the misspelled words!

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.