Re: [PATCH v2] serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt

Hey Andy, On 29-03-17 11:11, Andy Shevchenko wrote: On Wed, Mar 29, 2017 at 10:58 AM, Olliver Schinagl wrote: On 07-02-17 00:30, Douglas Anderson wrote: First of all I didn't get why people from Cc list are suddenly disappeared. Check your mail client settings. Returning

Re: [PATCH v2] serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt

Hey Andy, On 29-03-17 11:11, Andy Shevchenko wrote: On Wed, Mar 29, 2017 at 10:58 AM, Olliver Schinagl wrote: On 07-02-17 00:30, Douglas Anderson wrote: First of all I didn't get why people from Cc list are suddenly disappeared. Check your mail client settings. Returning back some of them.

Re: [PATCH v2] serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt

On Wed, Mar 29, 2017 at 10:58 AM, Olliver Schinagl wrote: > On 07-02-17 00:30, Douglas Anderson wrote: First of all I didn't get why people from Cc list are suddenly disappeared. Check your mail client settings. Returning back some of them. >> It appears that somehow we have

Re: [PATCH v2] serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt

On Wed, Mar 29, 2017 at 10:58 AM, Olliver Schinagl wrote: > On 07-02-17 00:30, Douglas Anderson wrote: First of all I didn't get why people from Cc list are suddenly disappeared. Check your mail client settings. Returning back some of them. >> It appears that somehow we have a RX Timeout

Re: [PATCH v2] serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt

Hey Douglas, On 07-02-17 00:30, Douglas Anderson wrote: On a Rockchip rk3399-based board during suspend/resume testing, we found that we could get the console UART into a state where it would print this to the console a lot: serial8250: too much work for irq42 Followed eventually by: NMI

Re: [PATCH v2] serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt

Hey Douglas, On 07-02-17 00:30, Douglas Anderson wrote: On a Rockchip rk3399-based board during suspend/resume testing, we found that we could get the console UART into a state where it would print this to the console a lot: serial8250: too much work for irq42 Followed eventually by: NMI

Re: [PATCH v2] serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt

On 02/06/2017 03:30 PM, Douglas Anderson wrote: On a Rockchip rk3399-based board during suspend/resume testing, we found that we could get the console UART into a state where it would print this to the console a lot: serial8250: too much work for irq42 Followed eventually by: NMI

Re: [PATCH v2] serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt

On 02/06/2017 03:30 PM, Douglas Anderson wrote: On a Rockchip rk3399-based board during suspend/resume testing, we found that we could get the console UART into a state where it would print this to the console a lot: serial8250: too much work for irq42 Followed eventually by: NMI

[PATCH v2] serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt

On a Rockchip rk3399-based board during suspend/resume testing, we found that we could get the console UART into a state where it would print this to the console a lot: serial8250: too much work for irq42 Followed eventually by: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 11s! Upon

[PATCH v2] serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt

On a Rockchip rk3399-based board during suspend/resume testing, we found that we could get the console UART into a state where it would print this to the console a lot: serial8250: too much work for irq42 Followed eventually by: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 11s! Upon