From: Jeff DeFouw <jeffd@i2k.com>
To: linux-serial@vger.kernel.org
Subject: 8250 misses interrupt, stalls
Date: Fri, 8 Aug 2008 01:27:27 -0400 [thread overview]
Message-ID: <20080808052727.GB23330@blorp.plorb.com> (raw)
I have a Celeron ETX processor module with a Winbond W83627HF SuperIO
chip, providing two 16550A compatible UARTs, which connects over LPC to
an 82801DB south bridge. I'm only using the first serial port at the
moment. The modules 8250 and 8250_pnp are loaded, and the serial port
is on standard resources (irq 4). After one of my complex applications
at work runs for a few minutes, the serial port suddenly stops. The
UART IIR indicates an interrupt is pending, and the LSR indicates data
is waiting to be received (as well as sent), but the interrupt handler
is not being called. If while it's stuck I reset the enabled interrupts
(save IER, clear IER, restore IER) the I/O resumes. I don't see
anything wrong with the way the UART is being serviced. The kernel is
patched to 2.6.25.11, configured by Debian as SMP, no PREEMPT, shared
IRQ (nothing else is on irq 4) and without any external modules loaded.
It's a Celeron without any HT or multiple cores, so it's uniprocessor.
I haven't been able to make a simple test case. The real program is
kind of a loopback that's continuously receiving and sending data at
115200 8N1 with no flow control. The full data rate isn't being used,
and I'm not getting any overruns (until it stalls). A simple loopback
program doesn't demonstrate the problem, but the real application runs
into it every time within 10 minutes (usually under 5).
--
Jeff DeFouw <jeffd@i2k.com>
next reply other threads:[~2008-08-08 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 5:27 Jeff DeFouw [this message]
2008-08-08 12:36 ` 8250 misses interrupt, stalls Kohne, Mike
2008-08-13 14:56 ` [PATCH/RFC] " Robert Evans
2008-08-20 15:29 ` Jeff DeFouw
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=20080808052727.GB23330@blorp.plorb.com \
--to=jeffd@i2k.com \
--cc=linux-serial@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.