LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Anderson <sean.anderson@seco.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	Christian Zigotzky <chzigotzky@xenosoft.de>,
	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: Tue, 3 Jan 2023 15:17:10 -0500	[thread overview]
Message-ID: <460bbe6b-3bbb-2960-be96-8da58b341ef6@seco.com> (raw)
In-Reply-To: <3a5f08ed-65dc-c6ff-5da5-b9ce6880c6fd@leemhuis.info>

On 1/2/23 02:58, Linux kernel regression tracking (#info) wrote:
> [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)

#regzbot fix: 7dc618385419

      reply	other threads:[~2023-01-03 20:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-01 14:18 [FSL P50x0] DPAA Ethernet issue Christian Zigotzky
2023-01-01 18:11 ` Sean Anderson
2023-01-02  3:32   ` Christian Zigotzky
2023-01-03  4:03     ` Christian Zigotzky
2023-01-03 19:59       ` Christian Zigotzky
2023-01-02  7:58 ` Linux kernel regression tracking (#info)
2023-01-03 20:17   ` Sean Anderson [this message]

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=460bbe6b-3bbb-2960-be96-8da58b341ef6@seco.com \
    --to=sean.anderson@seco.com \
    --cc=chzigotzky@xenosoft.de \
    --cc=darren@stevens-zone.net \
    --cc=davem@davemloft.net \
    --cc=info@xenosoft.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madskateman@gmail.com \
    --cc=matthew@a-eon.biz \
    --cc=regressions@leemhuis.info \
    --cc=rtd2@xtra.co.nz \
    /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