Re: [FSL P50x0] DPAA Ethernet issue

From: "Linux kernel regression tracking (#info)" <regressions@leemhuis.info>
To: Christian Zigotzky <chzigotzky@xenosoft.de>,
	sean.anderson@seco.com, davem@davemloft.net,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	mad skateman <madskateman@gmail.com>,
	Darren Stevens <darren@stevens-zone.net>,
	"R.T.Dickinson" <rtd2@xtra.co.nz>,
	Matthew Leaman <matthew@a-eon.biz>
Cc: Christian Zigotzky <info@xenosoft.de>
Subject: Re: [FSL P50x0] DPAA Ethernet issue
Date: Mon, 2 Jan 2023 08:58:51 +0100	[thread overview]
Message-ID: <3a5f08ed-65dc-c6ff-5da5-b9ce6880c6fd@leemhuis.info> (raw)
In-Reply-To: <0bfc8f3d-cb62-25f4-2590-ff424adbe48a@xenosoft.de>

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; all text you find below is based on a few templates
paragraphs you might have encountered already already in similar form.
See link in footer if these mails annoy you.]

On 01.01.23 15:18, Christian Zigotzky wrote:
> 
> The DPAA Ethernet doesn’t work anymore on our FSL P5020/P5040 boards [1]
> since the first updates after the final kernel 6.1 [2].
> We bisected yesterday [3] and found the problematic commit [4]. I was
> able to revert it. After that the DPAA Ethernet works again. I created a
> patch for reverting the commit [4]. After patching and compiling, the
> DPAA Ethernet also works again.
> 
> It seems, that the new driver doesn’t work with our onboard DPAA network
> interfaces.
> 
> Could you please check your commit? [4]
> 
> Thanks,
> Christian
> 
> [1] http://wiki.amiga.org/index.php?title=X5000
> [2] https://forum.hyperion-entertainment.com/viewtopic.php?p=56326#p56326
> [3] https://forum.hyperion-entertainment.com/viewtopic.php?p=56334#p56334
> [4] lnet: dpaa: Convert to phylink:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.1&id=5d93cfcf7360eac9903774fe94f626c9ead2049d

Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:

#regzbot ^introduced 5d93cfcf7360
#regzbot title lnet: dpaa: Ethernet issues
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (see page linked in footer for details).

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
-- 
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr

Annoyed by mails like this? Feel free to send them to /dev/null:
https://linux-regtracking.leemhuis.info/about/#infomails