From: Alex Williamson <alex.williamson@hp.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] backup timer for UARTs that lose interrupts
Date: Tue, 08 Nov 2005 17:16:32 -0700 [thread overview]
Message-ID: <1131495392.9657.9.camel@tdi> (raw)
In-Reply-To: <20051108232316.GH13357@flint.arm.linux.org.uk>
On Tue, 2005-11-08 at 23:23 +0000, Russell King wrote:
> On Tue, Nov 08, 2005 at 01:27:57PM -0700, Alex Williamson wrote:
> > Hi Russell,
> >
> > The patch below works around a minor bug found in the UART of the
> > remote management card used in many HP ia64 and parisc servers (aka the
> > Diva UARTs).
>
> Would setting UART_BUG_TXEN help ?
>
> UART_BUG_TXEN is set for ports which need a kick up their backsides
> to get their transmit interrupt status asserted, so that when new
> chars are placed in the ring buffer we start transmitting them.
>
> Your problem sounds very similar to this.
I was hoping that would be the solution too. I just tried enabling
UART_BUG_TXEN to double check my previous results. Somehow it makes the
problem much, much worse. Instead of being the nuisance it usually is,
it seems like the UART gets way behind on transmitting bits. So it
would probably prevent the unattended reboot stall since we kick it
every time we want to transmit, but it renders the UART completely
unusable as a console. I can't even get it caught up enough to login
via the serial console w/ UART_BUG_TXEN enabled on the port. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
next prev parent reply other threads:[~2005-11-09 0:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 20:27 [PATCH] backup timer for UARTs that lose interrupts Alex Williamson
2005-11-08 23:23 ` Russell King
2005-11-09 0:16 ` Alex Williamson [this message]
2005-11-10 10:44 ` Russell King
2005-11-10 13:38 ` Alex Williamson
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=1131495392.9657.9.camel@tdi \
--to=alex.williamson@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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