From: Ryan Wilbur <rwilbur633@gmail.com>
To: ryan.wilbur@nautel.com, lmorrison@nautel.com,
jonathan.downing@nautel.com
Cc: Ryan Wilbur <rwilbur633@gmail.com>, stable@vger.kernel.org
Subject: [PATCH v1] serial: 8250: clear stuck RX-timeout interrupt on LPC32xx (PORT_LPC3220)
Date: Thu, 16 Jul 2026 12:06:23 -0300 [thread overview]
Message-ID: <20260716150623.433496-1-rwilbur633@gmail.com> (raw)
The LPC32xx UART can latch an RX character-timeout interrupt while the
RX FIFO is empty: IIR reports UART_IIR_RX_TIMEOUT (0x0c) but LSR.DR is
clear. A character timeout is only cleared by reading RHR, but
serial8250_rx_chars() reads RHR only when LSR.DR is set, so nothing ever
clears the condition. The interrupt is level-triggered and re-fires
immediately, so on a single-core ARM926 the resulting interrupt
storm livelocks the CPU.
It is reproducible when userspace repeatedly opens the front-panel port
(ttyS1): serial8250_do_set_termios() re-enables interrupts on unlock and
the handler then spins forever with iir=0xcc lsr=0x60 ier=0x05, tripping
the soft-lockup detector in serial8250_handle_irq_locked().
Fix this by doing one throwaway RHR read to clear the timeout. It is gated
on PORT_LPC3220 and only fires when the FIFO is empty (LSR.DR clear), so
no real received data is ever discarded, and it is a no-op on healthy
UARTs which never report a timeout with DR==0.
This is the same class of bug already worked around for other 8250 cores;
see commit 424d79183af0 ("serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt")
which reports the identical iir=0xcc/lsr=0x60. See also
UART_RX_TIMEOUT_QUIRK in 8250_omap, and the note in 8250_bcm7271.
Cc: stable@vger.kernel.org
Signed-off-by: Ryan Wilbur <rwilbur633@gmail.com>
---
drivers/tty/serial/8250/8250_port.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250/8250_port.c
index 8c241ec7f4f2..20014f54637b 100644
--- a/drivers/tty/serial/8250/8250_port.c
+++ b/drivers/tty/serial/8250/8250_port.c
@@ -1803,6 +1803,20 @@ void serial8250_handle_irq_locked(struct uart_port *port, unsigned int iir)
if (!(status & UART_LSR_DR) && (status & UART_LSR_FIFOE))
serial8250_clear_and_reinit_fifos(up);
+ /*
+ * On PORT_LPC3220 the UART can raise an RX character-timeout
+ * interrupt with an empty RX FIFO (IIR reports RX_TIMEOUT but
+ * LSR.DR is clear). The timeout is only cleared by reading RHR,
+ * but the RX path below is skipped when the FIFO is empty, so
+ * nothing clears it. IRQ then re-fires immediately and livelocks
+ * this single-core. Do one throwaway RHR read to clear it.
+ * Same bug worked around for other 8250 cores (8250_dw, 8250_omap, 8250_bcm7271).
+ */
+ if (port->type == PORT_LPC3220 &&
+ (iir & UART_IIR_RX_TIMEOUT) == UART_IIR_RX_TIMEOUT &&
+ !(status & UART_LSR_DR))
+ serial_in(up, UART_RX);
+
/*
* If port is stopped and there are no error conditions in the
* FIFO, then don't drain the FIFO, as this may lead to TTY buffer
base-commit: da7b5fd4e17f8e44c5590f2d603c01d499f056e6
--
2.25.1
next reply other threads:[~2026-07-16 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 15:06 Ryan Wilbur [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-16 14:23 [PATCH v1] serial: 8250: clear stuck RX-timeout interrupt on LPC32xx (PORT_LPC3220) Ryan Wilbur
2026-07-16 14:14 Ryan Wilbur
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=20260716150623.433496-1-rwilbur633@gmail.com \
--to=rwilbur633@gmail.com \
--cc=jonathan.downing@nautel.com \
--cc=lmorrison@nautel.com \
--cc=ryan.wilbur@nautel.com \
--cc=stable@vger.kernel.org \
/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