[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1511298864.25007.370.camel@linux.intel.com>
Date: Tue, 21 Nov 2017 23:14:24 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Fengguang Wu <fengguang.wu@...el.com>, linux-serial@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Sean Young <sean@...s.org>,
Matthias Brugger <mbrugger@...e.com>,
linux-kernel@...r.kernel.org, lkp@...org
Subject: Re: [serial8250_interrupt] RIP: 0010:arch_local_irq_restore+0x2/0x8
On Tue, 2017-11-21 at 16:39 +0200, Andy Shevchenko wrote:
> On Tue, 2017-11-21 at 21:31 +0800, Fengguang Wu wrote:
> > On Tue, Nov 21, 2017 at 08:33:57PM +0800, Fengguang Wu wrote:
>>> FYI this happens in mainline kernel 4.14.0-02748-gabc36be.
> > > It shows up since v4.13 .
> >
> > Sorry it actually also shows up in 4.10:
>> [ 21.020567] irq 3: nobody cared (try booting with the "irqpoll"
> > option)
> > [ 21.039171] uart_start+0x73/0xe0
> > [ 21.044977] vfs_write+0xc8/0x1e0
> > [ 21.054662] Disabling IRQ #3
Another question who and why initiates a write to ttyS1 (console seems
on ttyS0).
--
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy
Powered by blists - more mailing lists