bcmgenet fd580000.ethernet: failed to get enet clock

Open
#3,884 1 comment 0 reactions 0 assignees View on GitHub

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

Start with the bcmgenet driver and the Raspberry Pi 4 device-tree clock definitions for the 5.4 kernel, then reproduce the reported dmesg messages with the provided configuration. Determine whether the enet, enet-wol, and enet-eee clock lookup failures indicate a functional problem; done means the errors are explained or corrected and Ethernet behavior is covered by an appropriate test.

Written by the indexing model from the issue text.

Description

I am seeing enet clock erros in dmesgs with 5.4 kernel, I am having ethernet connected to rpi4-64, the interface seems to come up fine and get DHCP assigned address too. But wanted to know if these errors are harmless or not. So I can ignore them in yocto autotests.

root@raspberrypi4-64:~# uname -a
Linux raspberrypi4-64 5.4.69-v8 #1 SMP PREEMPT Mon Oct 5 17:19:05 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux

root@raspberrypi4-64:~# dmesg|grep "fd580000.ethernet: failed"
[    0.973060] bcmgenet fd580000.ethernet: failed to get enet clock
[    0.973102] bcmgenet fd580000.ethernet: failed to get enet-wol clock
[    0.973122] bcmgenet fd580000.ethernet: failed to get enet-eee clock
root@raspberrypi4-64:~# ifconfig
eth0      Link encap:Ethernet  HWaddr DC:A6:32:01:12:B5
          inet addr:10.0.0.54  Bcast:10.0.0.127  Mask:255.255.255.128
          inet6 addr: fe80::dea6:32ff:fe01:12b5/64 Scope:Link
          inet6 addr: 2601:646:9200:4e0:dea6:32ff:fe01:12b5/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:63427 errors:0 dropped:6 overruns:0 frame:0
          TX packets:5532 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12614066 (12.0 MiB)  TX bytes:1237622 (1.1 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:60904 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60904 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:145365017 (138.6 MiB)  TX bytes:145365017 (138.6 MiB)

in .config I have

CONFIG_BCM7XXX_PHY=y
# CONFIG_BCM87XX_PHY is not set
CONFIG_BCM_NET_PHYLIB=y
CONFIG_BROADCOM_PHY=y

Let me know if more info is needed.

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.