Bug#982270: linux: [armhf] several imx6 systems unable to detect ethernet

From	Vagrant Cascadian <vagrant@debian.org>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#982270: linux: [armhf] several imx6 systems unable to detect ethernet
Date	2021-05-17 23:50 +0200
Message-ID	<CfThD-3wL-1@gated-at.bofh.it> (permalink)
References	<BG2KR-4Es-3@gated-at.bofh.it> <BHpm1-6SO-1@gated-at.bofh.it> <BG2KR-4Es-3@gated-at.bofh.it> <BHpm1-6SO-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On 2021-02-11, Vagrant Cascadian wrote:
> Control: reassign 982270 linux
> Control: retitle 982270 linux: [armhf] several imx6 systems unable to detect ethernet
> Control: found 982270 5.10.13-1
>
> On 2021-02-07, Rick Thomas wrote:
>> It booted fine but when it got to the "Detect network hardware" phase,
>> it failed and said:
>>
>>>     No Ethernet card was detected. If you know the name of the driver
>>>     needed by your Ethernet card, you can select it from the list.
>>>     Driver needed by your Ethernet card:
>
> I can confirm this is an issue on hummingboard-i2ex, cubox-i4x4 and
> wandboard quad, all of which are similar imx6 systems, and all of which
> use the SoC's gigabit ethernet interface.
>
> I've had better luck with linux 5.9.x and 4.19.x versions, although
> possibly backported patches on the stable branches may also trigger
> similar issues, just not consistantly. 5.10.x seems to consistantly
> result in no working ethernet interface.
>
> Marked as found in 5.10.13-1, but I believe this affects all 5.10.x
> versions I have seen.
>
> Possibly related to changes to the mdio interface infrastructure, but
> this pretty much needs someone to able take the time to git bisect and
> boot test the issue...

I'm also experiencing periodic issues on 4.19.x:

   fec 2188000.ethernet eth0: MDIO read timeout

Not sure if that is related or a separate issue... there the ethernet
interface is present, but periodically becomes unusable, and bringing
the interface down and up again "fixes" the problem:

  $ ip a
  ...
  2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
  state DOWN group default qlen 1000
      link/ether 12:4f:47:94:87:e1 brd ff:ff:ff:ff:ff:ff
      inet 10.0.0.56/24 brd 10.0.0.255 scope global eth0
         valid_lft forever preferred_lft forever
      inet6 fe80::104f:47ff:fe94:87e1/64 scope link
         valid_lft forever preferred_lft forever

  $ ping 10.0.0.1
  PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
  ^C
  --- 10.0.0.1 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms


  $ sudo ifdown eth0 ; sudo ifup eth0
  $ ping 10.0.0.1
  PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
  From 10.0.0.56 icmp_seq=1 Destination Host Unreachable
  64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.265 ms
  64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.452 ms
  ^C
  --- 10.0.0.1 ping statistics ---
  3 packets transmitted, 2 received, +1 errors, 33.3333% packet loss,
  time 2024ms


live well,
  vagrant

Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread

Thread

Bug#982270: linux: [armhf] several imx6 systems unable to detect ethernet Vagrant Cascadian <vagrant@debian.org> - 2021-05-17 23:50 +0200

csiph-web