From: Thorsten Leemhuis <regressions@leemhuis.info> To: Leo Li <leoyang.li@nxp.com>, "jocke@infinera.com" <joakim.tjernlund@infinera.com>, "regressions@leemhuis.info" <regressions@leemhuis.info>, "Eugene_Bordenkircher@selinc.com" <Eugene_Bordenkircher@selinc.com>, "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>, "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org> Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>, "balbi@kernel.org" <balbi@kernel.org> Subject: Re: bug: usb: gadget: FSL_UDC_CORE Corrupted request list leads to unrecoverable loop. Date: Thu, 20 Jan 2022 13:54:39 +0100 [thread overview] Message-ID: <ce653a10-c004-75b1-5f70-e23c0c2aee68@leemhuis.info> (raw) In-Reply-To: <AS8PR04MB89464D90D2E92A5D401474BD8F6B9@AS8PR04MB8946.eurprd04.prod.outlook.com> Hi, this is your Linux kernel regression tracker speaking. On 04.12.21 01:40, Leo Li wrote: >> -----Original Message----- >> From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com> >> Sent: Thursday, December 2, 2021 4:45 PM >> To: regressions@leemhuis.info; Leo Li <leoyang.li@nxp.com>; >> Eugene_Bordenkircher@selinc.com; linux-usb@vger.kernel.org; linuxppc- >> dev@lists.ozlabs.org >> Cc: gregkh@linuxfoundation.org; balbi@kernel.org >> Subject: Re: bug: usb: gadget: FSL_UDC_CORE Corrupted request list leads to >> unrecoverable loop. >> >> On Thu, 2021-12-02 at 20:35 +0000, Leo Li wrote: >>> >>>> -----Original Message----- >>>> From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com> >>>> Sent: Wednesday, December 1, 2021 8:19 AM >>>> To: regressions@leemhuis.info; Leo Li <leoyang.li@nxp.com>; >>>> Eugene_Bordenkircher@selinc.com; linux-usb@vger.kernel.org; >>>> linuxppc- dev@lists.ozlabs.org >>>> Cc: gregkh@linuxfoundation.org; balbi@kernel.org >>>> Subject: Re: bug: usb: gadget: FSL_UDC_CORE Corrupted request list >>>> leads to unrecoverable loop. >>>> >>>> On Tue, 2021-11-30 at 12:56 +0100, Joakim Tjernlund wrote: >>>>> On Mon, 2021-11-29 at 23:48 +0000, Eugene Bordenkircher wrote: >>>>>> Agreed, >>>>>> >>>>>> We are happy pick up the torch on this, but I'd like to try and >>>>>> hear from >>>> Joakim first before we do. The patch set is his, so I'd like to >>>> give him the opportunity. I think he's the only one that can add a >>>> truly proper description as well because he mentioned that this >>>> includes a "few more fixes" than just the one we ran into. I'd >>>> rather hear from him than try to reverse engineer what was being >> addressed. >>>>>> >>>>>> Joakim, if you are still watching the thread, would you like to >>>>>> take a stab >>>> at it? If I don't hear from you in a couple days, we'll pick up the >>>> torch and do what we can. Did anything happen? Sure, it's a old regression from the v3.4-rc4 days, but there iirc was already a tested proto-patch in that thread that fixes the issue. Or was progress made and I just missed it? Ciao, Thorsten P.S.: As a Linux kernel regression tracker I'm getting a lot of reports on my table. I can only look briefly into most of them. Unfortunately therefore I sometimes will get things wrong or miss something important. I hope that's not the case here; if you think it is, don't hesitate to tell me about it in a public reply, that's in everyone's interest. BTW, I have no personal interest in this issue, which is tracked using regzbot, my Linux kernel regression tracking bot (https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting this mail to get things rolling again and hence don't need to be CC on all further activities wrt to this regression. #regzbot ignore-activity >>>>> I am far away from this now and still on 4.19. I don't mind if you >>>>> tweak >>>> tweak the patches for better "upstreamability" >>>> >>>> Even better would be to migrate to the chipidea driver, I am told >>>> just a few tweaks are needed but this is probably something NXP >>>> should do as they have access to other SOC's using chipidea. >>> >>> I agree with this direction but the problem was with bandwidth. As this >> controller was only used on legacy platforms, it is harder to justify new effort >> on it now. >> >> Legacy? All PPC is legacy and not supported now? > > I'm not saying that they are not supported, but they are in maintenance only mode.
next prev parent reply other threads:[~2022-01-20 13:10 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-29 17:14 Eugene Bordenkircher 2021-10-29 17:24 ` Eugene Bordenkircher 2021-10-29 23:14 ` Li Yang 2021-10-30 14:20 ` Joakim Tjernlund 2021-11-02 21:15 ` Joakim Tjernlund 2021-11-15 8:36 ` Thorsten Leemhuis 2021-11-16 19:11 ` Eugene Bordenkircher 2021-11-25 13:59 ` Thorsten Leemhuis 2021-11-29 17:24 ` Eugene Bordenkircher 2021-11-29 23:37 ` Leo Li 2021-11-29 23:48 ` Eugene Bordenkircher 2021-11-30 11:56 ` Joakim Tjernlund 2021-12-01 14:19 ` Joakim Tjernlund 2021-12-02 20:35 ` Leo Li 2021-12-02 22:45 ` Joakim Tjernlund 2021-12-04 0:40 ` Leo Li 2022-01-20 12:54 ` Thorsten Leemhuis [this message] 2022-02-18 7:11 ` Thorsten Leemhuis 2022-02-18 10:21 ` Joakim Tjernlund 2022-02-18 10:39 ` gregkh 2022-02-18 11:17 ` Joakim Tjernlund 2022-02-18 11:48 ` gregkh
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=ce653a10-c004-75b1-5f70-e23c0c2aee68@leemhuis.info \ --to=regressions@leemhuis.info \ --cc=Eugene_Bordenkircher@selinc.com \ --cc=balbi@kernel.org \ --cc=gregkh@linuxfoundation.org \ --cc=joakim.tjernlund@infinera.com \ --cc=leoyang.li@nxp.com \ --cc=linux-usb@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --subject='Re: bug: usb: gadget: FSL_UDC_CORE Corrupted request list leads to unrecoverable loop.' \ /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
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).