From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Shankara Pailoor <sp3485@columbia.edu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
jslaby@suse.com, LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
linux-serial@vger.kernel.org
Subject: Re: RCU stall in 8250 serial driver Linux 4.15-rc1
Date: Tue, 23 Jan 2018 15:52:29 +0000 [thread overview]
Message-ID: <20180123155229.2035e674@alans-desktop> (raw)
In-Reply-To: <CAASgV=tRY1ioh4vZi3ZyugDJzCiADwo+Mg+HNoEwCzAaV_G=jQ@mail.gmail.com>
On Wed, 17 Jan 2018 09:24:32 -0800
Shankara Pailoor <sp3485@columbia.edu> wrote:
> Hi Greg,
>
> Sorry for that. Here is the stack trace. C Program below
> serial_in drivers/tty/serial/8250/8250.h:111 [inline]
> wait_for_xmitr+0x8a/0x1d0 drivers/tty/serial/8250/8250_port.c:2033
> serial8250_console_putchar+0x19/0x50 drivers/tty/serial/8250/8250_port.c:3170
> uart_console_write+0x98/0xc0 drivers/tty/serial/serial_core.c:1858
The console is spinning in polled mode trying to write data to the
console port, which it seems has gotten a bit stuck. Could be the
hypervisor hits some kind of buffering limit, could be hypervisor
interface broke.
Either way the console interface is supposed to stall the machine to
ensure the bytes always get out and if your serial port jams or gets
massively behind then this will happen.
Alan
next prev parent reply other threads:[~2018-01-23 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 16:53 RCU stall in 8250 serial driver Linux 4.15-rc1 Shankara Pailoor
2018-01-17 17:05 ` Greg KH
2018-01-17 17:24 ` Shankara Pailoor
2018-01-23 15:52 ` Alan Cox [this message]
2018-01-24 16:40 ` Andy Shevchenko
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=20180123155229.2035e674@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sp3485@columbia.edu \
--cc=syzkaller@googlegroups.com \
/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