mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] suggested fix for 83xx/85xx PowerPC UART break bug
Date: Thu, 31 Jul 2008 15:31:43 -0500	[thread overview]
Message-ID: <EF0F4B21-1612-445C-AEBF-CD7B72762AD1@kernel.crashing.org> (raw)
In-Reply-To: <20080731152616.GA14248@windriver.com>


On Jul 31, 2008, at 10:26 AM, Paul Gortmaker wrote:

>
> This is something I'd tripped over earlier, and wanted to follow up on
> to get an acceptable fix in for everyone's benefit before it falls  
> through
> the cracks again.
>
> There seems to be an issue with recent 83xx/85xx SOC UARTs, in which  
> a break
> triggers a short lived IRQ storm (hence killing any hope of using  
> SysRQ).
> The only fix I found to work was to just ignore the bogus events that
> had the associated signature bit set.
>
> This fix is what I was using against earlier kernels, but I hate to  
> add more
> board/arch specific ifdefs to files like 8250.c, so I'm wondering if
> anyone has any other suggestions before I simply end up cleaning up  
> the
> boardlist (now ppc is dead) and respinning the patch much as it is now
> and resending.

How did you test this or generate it?  I was thinking about this the  
other day and figured we need to try and track this down with the HW  
guys.  If we can generate a simple test I can try and run it through  
the various boards/parts we have and see which ones show the issue and  
which dont.

- k

  reply	other threads:[~2008-07-31 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 15:26 Paul Gortmaker
2008-07-31 20:31 ` Kumar Gala [this message]
2008-08-01  1:43   ` Paul Gortmaker

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=EF0F4B21-1612-445C-AEBF-CD7B72762AD1@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    /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

all inboxes | Powered by JetHome®