From: Nick Bowler <nbowler@draconx.ca>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org
Cc: regressions@lists.linux.dev
Subject: PROBLEM: Broken or delayed ethernet on Xilinx ZCU104 since 5.18 (regression)
Date: Fri, 4 Aug 2023 11:26:37 -0400 [thread overview]
Message-ID: <CADyTPEzqf8oQAPSFRWJLxAhd-WE4fX2zdoe9Vu6V9hZMn1Yc8g@mail.gmail.com> (raw)
Hi,
With recent kernels (5.18 and newer) the ethernet is all wonky on my
ZCU104 board.
There is some behaviour inconsistency between kernel versions identified
during bisection, so maybe there is more than one issue with the ethernet?
6.5-rc4: after 10 seconds, the following message is printed:
[ 10.761808] platform ff0e0000.ethernet: deferred probe pending
but the network device seemingly never appears (I waited about a minute).
6.1 and 6.4: after 10 seconds, the device suddenly appears and starts
working (but this is way too late).
5.18: the device never appears and no unusual messages are printed
(I waited ten minutes).
With 5.17 and earlier versions, the eth0 device appears without any delay.
Unfortunately, as bisection closed on the problematic section, all the
built kernels became untestable as they appear to crash during early
boot. Nevertheless, I manually selected a commit that sounded relevant:
commit e461bd6f43f4e568f7436a8b6bc21c4ce6914c36
Author: Robert Hancock <robert.hancock@calian.com>
Date: Thu Jan 27 10:37:36 2022 -0600
arm64: dts: zynqmp: Added GEM reset definitions
Reverting this fixes the problem on 5.18. Reverting this fixes the
problem on 6.1. Reverting this fixes the problem on 6.4. In all of
these versions, with this change reverted, the network device appears
without delay.
Unfortunately, it seems this is not sufficient to correct the problem on
6.5-rc4 -- there is no apparent change in behaviour, so maybe there is
a new, different problem?
I guess I can kick off another bisection to find out when this revert
stops fixing things...
Let me know if you need any more info!
Thanks,
Nick
next reply other threads:[~2023-08-04 15:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 15:26 Nick Bowler [this message]
2023-08-04 15:45 ` PROBLEM: Broken or delayed ethernet on Xilinx ZCU104 since 5.18 (regression) Linux regression tracking (Thorsten Leemhuis)
2023-08-08 16:00 ` Robert Hancock
2023-08-04 15:52 ` Rob Herring
2023-08-04 16:24 ` Nick Bowler
2023-08-04 16:28 ` Nick Bowler
2023-08-04 16:47 ` Russell King (Oracle)
2023-08-04 16:54 ` Nick Bowler
2023-08-04 17:02 ` Rob Herring
2023-08-04 17:52 ` Nick Bowler
2023-08-04 20:22 ` Rob Herring
2023-08-04 21:31 ` Nick Bowler
2023-08-04 22:27 ` Russell King (Oracle)
2023-08-05 6:57 ` Nick Bowler
2023-08-05 7:03 ` Andrew Lunn
2023-08-05 6:58 ` Andrew Lunn
2023-08-05 7:10 ` Nick Bowler
2023-08-05 7:25 ` Andrew Lunn
2023-08-05 7:34 ` Nick Bowler
2023-08-29 13:30 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-08-05 1:03 ` Saravana Kannan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADyTPEzqf8oQAPSFRWJLxAhd-WE4fX2zdoe9Vu6V9hZMn1Yc8g@mail.gmail.com \
--to=nbowler@draconx.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).