[CCing the regression list, as it should be in the loop for regressions: https://docs.kernel.org/admin-guide/reporting-regressions.html] [TLDR: I'm adding this report to the list of tracked Linux kernel regressions; the text you find below is based on a few templates paragraphs you might have encountered already in similar form. See link in footer if these mails annoy you.] On 23.05.23 10:59, Richard Tresidder wrote: > We seem to be getting corruption of received data from a ublox GPS unit > To me it looks like a fifo overrun of some sort?? > > background: > I'm attempting to use 6.3.3 as a new base for one of our systems. > Previously it was using 5.1.7 as a base. > The uart in question is one of the two in the Cyclone V SOC HPS. > And to muddy the waters the linux console TTYS0 is the other Uart from > the same HPS core > Yet the console appears to be working ok. > Note all other libs and apps are at the same revision and build, it is > only the kernel that is different. > Both versions of the kernel are also built using the same bitbake bsdk.. > > Seeing the following with 6.3.3: > [...] 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 57e9af7831dcf211c5c689c2a #regzbot title serial: 8250_dma: data corruption with ublox GPS unit #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. Developers: When fixing the issue, remember to add 'Link:' tags pointing to the report (the parent of this mail). 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 That page also explains what to do if mails like this annoy you.
