From: Prasad Koya <prasad.koya@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-serial@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: UART_IIR_BUSY set for 16550A
Date: Sat, 24 May 2014 18:22:02 -0700 [thread overview]
Message-ID: <CAGXD9Odvyd_go-x9-gR7Q7_etYPLHekDM3SKRN+PCvDHc__LHg@mail.gmail.com> (raw)
In-Reply-To: <20140525003642.GC6946@thunk.org>
Thanks for looking into this.
With 16550A, I'm seeing this weird issue with 3.4 kernel. At random
times 8250 driver reads 0xcc out of IIR. I'm not sure why bit 2 is
set.
#define UART_IIR_BUSY 0x07 /* DesignWare APB Busy Detect */
Soon after this I'm running into "serial8250: too much work for irq4".
And this is printed after iterating 512 times in 8250_interrupt
handler. This message is printed one more time right after this and it
appears that console does not work after those messages. I was
suspicious about that 'busy detect' bit. Am trying to reproduce this
and see what is in LCR when this hits. Can I (or how do I) reset the
device if I see this bit set?
On Sat, May 24, 2014 at 5:36 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> On Fri, May 23, 2014 at 10:08:49AM -0700, Prasad Koya wrote:
>>
>> I don't see anyone in kernel using UART_IIR_BUSY bit except Designware
>> serial driver. We are using 8250 driver for our 16550A and
>> occasionally we see UART_IIR_BUSY set and soon after that console is
>> hosed. In what situations is this bit set? I don't see much
>> documentation for this.
>
> UART_IIR_BUSY is not a bit, it's a magic bit pattern, which is I
> believe a Designware-specific hack. As far as standard
> 8250-compatible UART's are concerned, if the low bit (bit 0) is set in
> the IIR register, there are no interrupts pending, and so you
> shouldn't need to check the 0x06 bits (i.e., bits 1 and 2).
>
> - Ted
next prev parent reply other threads:[~2014-05-25 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 17:08 UART_IIR_BUSY set for 16550A Prasad Koya
2014-05-25 0:36 ` Theodore Ts'o
2014-05-25 1:22 ` Prasad Koya [this message]
2014-05-25 2:44 ` Theodore Ts'o
2014-05-25 6:21 ` Prasad Koya
2014-05-25 12:04 ` Theodore Ts'o
2014-05-27 23:33 ` Prasad Koya
2014-05-28 5:03 ` Theodore Ts'o
2014-05-28 5:47 ` Prasad Koya
2014-05-29 6:18 ` Theodore Ts'o
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=CAGXD9Odvyd_go-x9-gR7Q7_etYPLHekDM3SKRN+PCvDHc__LHg@mail.gmail.com \
--to=prasad.koya@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).