From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: [PATCH/RFC] mpc83xx/85xx SysRQ/brk over 8250 console
Date: Tue, 8 Jan 2008 00:11:19 -0600 [thread overview]
Message-ID: <E031E6FD-8A6F-49D5-9241-33B6ADEECCF7@kernel.crashing.org> (raw)
In-Reply-To: <20080108052743.GA18083@windriver.com>
On Jan 7, 2008, at 11:27 PM, Paul Gortmaker wrote:
> It seems that if a break is rec'd on the serial console (as per SysRQ
> or similar) on some 83xx and 85xx processors, then a pulse of IRQs is
> generated which makes the use of SysRQ itself about 99% impossible. I
> experimented with trying several ACK strategies, but in the end the
> thing which worked best was just to wait for the surge of events to
> pass
> (a fraction of a second). The number of events can be on the order of
> 1000 (as reported by /proc/interrupts)
>
> I really dislike seeing board specific ifdefs within what should be
> board independent code, so I'm hoping that once the problem is known,
> that a more elegant solution will pop into someone's head. Or at
> least
> this will hopefully save someone the grief of re-investigating the
> source
> and start a discussion.
>
> I've seen this on two different 834x boards and also an 8548 based
> board. At this point, it is not clear to me if the problem extends
> beyond these CPU/soc to all with UARTs at 4500/4600.
>
> While less than ideal, the work-around below which simply ignores the
> events does allow a person to use SysRQ on such platforms.
>
> The definition of the RFE bit (Rx FIFO error) can be found in pretty
> much any of the MPC CPU PDFs (for those with 4500/4600 16550s).
>
> Paul.
This should really get posted to linux-kernel@vger.kernel.org and
probably linux-serial@vger.kernel.org lists.
- k
prev parent reply other threads:[~2008-01-08 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 5:27 [PATCH/RFC] mpc83xx/85xx SysRQ/brk over 8250 console Paul Gortmaker
2008-01-08 6:11 ` Kumar Gala [this message]
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=E031E6FD-8A6F-49D5-9241-33B6ADEECCF7@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).