All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Alex Williamson <alex.williamson@hp.com>
Cc: rmk+serial@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] backup timer for UARTs that lose interrupts (take 2)
Date: Wed, 16 Nov 2005 09:30:04 -0800	[thread overview]
Message-ID: <437B6C9C.3060307@mvista.com> (raw)
In-Reply-To: <1132158489.5457.10.camel@tdi>

Could you _please_ not put inline patches after the signature mark ("-- ").  In my mailer (mozilla) 
this causes the patch to be greyed out and, more importantly, NOT included in a reply.  This, in 
turn, makes it hard to comment on details in the patch.

Thanks
George
-- 


Alex Williamson wrote:
> Hi Russell,
> 
>    I've revised the patch for this backup timer idea based on your
> comments.  Hopefully the restoring of the timer function to the default
> serial8250_timeout is more obvious now.  I also re-ordered some of the
> conditions around the bug test to add further clarity.  Please let me
> know if you see any further issues with this patch.  Patch below is
> against 2.6.14-mm2.  Here's the original patch description message:
> 
>    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).  The problem is that the UART does not reassert the THRE
> interrupt if it has been previously cleared and the IIR THRI bit is
> re-enabled.  This can produce a very annoying failure mode when used as
> a serial console, allowing a boot/reboot to hang indefinitely until an
> RX interrupt kicks it into working again (ie. an unattended reboot could
> stall).  Paul Bame submitted a complete workaround for 2.4 kernels a few
> years ago - http://lkml.org/lkml/2003/5/6/203.  The problem has not been
> as prevalent on the 2.6 serial driver, thus the solution below is
> simplified to only insert a backup timeout to kick the UART when it gets
> into trouble.  This runs alongside the normal interrupt driven UART code
> and has a longer period that the standard polling driver to reduce CPU
> overhead.  The detection test should be safe for all UARTs and the
> backup timer can easily be extended to include other UARTs with similar
> disorders.
> 
>    Please apply.  Thanks,
> 
> 	Alex
> 

-- 
George Anzinger   george@mvista.com
HRT (High-res-timers):  http://sourceforge.net/projects/high-res-timers/

  reply	other threads:[~2005-11-16 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 16:28 [PATCH] backup timer for UARTs that lose interrupts (take 2) Alex Williamson
2005-11-16 17:30 ` George Anzinger [this message]
2005-11-16 17:41   ` Randy.Dunlap
2005-11-16 18:32     ` George Anzinger
2005-11-16 17:44   ` 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=437B6C9C.3060307@mvista.com \
    --to=george@mvista.com \
    --cc=alex.williamson@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+serial@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 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.