Flooded by error ➜ eth0: not whole frame pointed by descriptor
Describe the issue you are experiencing
The problem
Since I am on 2024.8.x, I am seeing my ha CLI screen being flooded with error message that looks like the following:
macb 1f00100000.ethernet eth0: not whole frame pointed by descriptor
I would love to know if this needs attention. I am not seeing any side effect in regular usage so far.
My online exploration tells me that this is connected to the config of the network adapter and if I increase the rx buffer size this should be okay. I wanted to check here before I go down the process of enabling SSH and doing these changes, which may or may not persist through updates.
What operating system image do you use?
rpi5-64 (Raspberry Pi 5 64-bit OS)
What version of Home Assistant Operating System is installed?
6.6.31-haos-raspi
Did the problem occur after upgrading the Operating System?
Yes
Hardware details
Running on Pi5 with wired ethernet to my TP-Link ER605 router.
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
-
Anything in the Host logs that might be useful for us?
-
System information
System Information
| version | core-2024.8.3 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.12.4 |
| os_name | Linux |
| os_version | 6.6.31-haos-raspi |
| arch | aarch64 |
| timezone | Asia/Calcutta |
| config_dir | /config |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | September 26, 2024 at 5:30 AM |
| relayer_connected | true |
| relayer_region | ap-southeast-1 |
| remote_enabled | true |
| remote_connected | true |
| alexa_enabled | false |
| google_enabled | false |
| remote_server | ap-southeast-1-2.ui.nabu.casa |
| certificate_status | ready |
| instance_id | 8b1ce8c77a6e4f01a24fbf0a36ba482a |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 13.1 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2024.08.0 |
| agent_version | 1.6.0 |
| docker_version | 26.1.4 |
| disk_total | 228.5 GB |
| disk_used | 8.2 GB |
| healthy | true |
| supported | true |
| host_connectivity | true |
| supervisor_connectivity | true |
| ntp_synchronized | true |
| virtualization | |
| board | rpi5-64 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Matter Server (6.4.2), Terminal & SSH (9.14.0), AdGuard Home (5.1.1), UniFi Network Application (3.2.0) |
Dashboards
| dashboards | 5 |
|---|---|
| resources | 0 |
| views | 4 |
| mode | storage |
Recorder
| oldest_recorder_run | August 29, 2024 at 3:13 PM |
|---|---|
| current_recorder_run | September 3, 2024 at 1:47 PM |
| estimated_db_size | 145.27 MiB |
| database_engine | sqlite |
| database_version | 3.45.3 |
Additional information
I am running only AdGuard as an additional addon that serves DNS.
First time I see this to be honest. Is this something that happens also when you stop all the add-ons and when HAOS is mostly idling? Isn't there something causing excessive traffic in your network?
Same issue on PI 5 with HA supervised with last version.
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Hi All,
I got the same issue with a raspberry Pi5. I thought it was a hardware issue and I replaced my pi5 by a new one. I got the same issue. This issue disappeared by usin an ethernet-usb adaptator and by connecting my network through usb. This issue also appeared with different sd card and SSD conected with a hat. Is ther any solution for this issue. I used HA last release and, of course, I have updated my pi5.
Thank you very much for your help
I just moved my HA installation RPI4 -> RPi5 and I'm also having these errors. They appear as a group of 3-5 every few seconds. HA seems to be working okay otherwise.
Getting this again on another Pi5 running Debian 12 Bookworm (Mainsail OS based on Raspberry Pi OS). This doesn't seem related to HAOS, but this ticket is the only place it's been reported since 2018. No other leads.
@jace This might be a better place to report the issue then: https://github.com/raspberrypi/linux/issues