Regression: serial: imx: overrun errors on debug UART

[Stefan Wahren]

Hi Thorsten,

Am 20.06.23 um 16:47 schrieb Linux regression tracking (Thorsten Leemhuis):
> On 24.05.23 15:07, Stefan Wahren wrote:
>>
>> Am 23.05.23 um 21:44 schrieb Sergey Organov:
>>> "Linux regression tracking (Thorsten Leemhuis)"
>>> <regressions at leemhuis.info> writes:
>>>
>>> Solving this would need to identify the cause of interrupts being
>>> disabled for prolonged times, and nobody volunteered to investigate this
>>> further. One suspect, the Linux serial console, has been likely excluded
>>> already though, as not actually being in use for printk() output.
>>>
>>
>> I don't think that we can exclude the serial console as a whole, i never
>> made such a observation. But at least we can exclude kernel logging on
>> the debug UART.
> 
> Stefan, just wondering: was this ever addressed upstream? I assume it's
> not, just wanted to be sure.
> 
> I'm a bit unsure what to do with this and consider asking Greg for
> advice, as he applied the patch. On one hand it's *IMHO* clearly a
> regression (but for the record,  some people involved in the discussion
> claim it's not). OTOH the culprit was applied more than a year ago now,
> so reverting it might cause more trouble than it's worth at this point,
> as that could lead to regressions for other users.

thanks for tracking this issue, but in my opinion the discussion goes in 
circles. So i don't see a point in reanimating this again.

Articles like [1] suggests me this is a general issue.

Best regards

[1] - https://www.phoronix.com/news/Printk-Threaded-Atomic-v1

> 
> 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
> If I did something stupid, please tell me, as explained on that page.
> 
> #regzbot poke