Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ivica Mikec <mikeci@acm.org>
To: <linux-mips@linux-mips.org>
Subject: Possible bug in 8250.c
Date: Thu, 11 Aug 2011 16:23:27 -0700	[thread overview]
Message-ID: <59027.1313105007@sonic.net> (raw)

Hi!


I noticed a problem in 8250.c.

My board has only one UART port, and is 16550 compatible, so in function serial8250_interrupt I see that serial_in function is called twice. Second time, code "else if (end == NULL)" is executed and function return IRQ_NONE. This causes an entry in /proc/irq/spurious:

count 239
unhandled 1
last_unhandled 4294700846 ms

But this is not a spurious interrupt.

Regards.

WARNING: multiple messages have this Message-ID (diff)
From: Ivica Mikec <mikeci@acm.org>
To: linux-mips@linux-mips.org
Subject: Possible bug in 8250.c
Date: Thu, 11 Aug 2011 16:23:27 -0700	[thread overview]
Message-ID: <59027.1313105007@sonic.net> (raw)
Message-ID: <20110811232327.f5loucA24E3YW7s09PFwz9EzkWDdYy3Q9YZKwDl5QHI@z> (raw)

Hi!


I noticed a problem in 8250.c.

My board has only one UART port, and is 16550 compatible, so in function serial8250_interrupt I see that serial_in function is called twice. Second time, code "else if (end == NULL)" is executed and function return IRQ_NONE. This causes an entry in /proc/irq/spurious:

count 239
unhandled 1
last_unhandled 4294700846 ms

But this is not a spurious interrupt.

Regards.

             reply	other threads:[~2011-08-11 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 23:23 Ivica Mikec [this message]
2011-08-11 23:23 ` Possible bug in 8250.c Ivica Mikec

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=59027.1313105007@sonic.net \
    --to=mikeci@acm.org \
    --cc=linux-mips@linux-mips.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