From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Greg KH <greg@kroah.com>
Cc: johnlinn@comcast.net, linux-serial@vger.kernel.org
Subject: Re: kernel lockup due to bad baud rate data
Date: Thu, 16 Jun 2011 09:19:28 +0100 [thread overview]
Message-ID: <20110616091928.1aa28c86@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20110616002130.GA25488@kroah.com>
On Wed, 15 Jun 2011 17:21:30 -0700
Greg KH <greg@kroah.com> wrote:
> On Thu, Jun 16, 2011 at 12:09:12AM +0000, johnlinn@comcast.net wrote:
> > I'm testing with 2.6.39 and our serial driver that's unique to our ARM
> > platform. I suspect we have a problem with our serial driver but
> > wanted to see if anyone has seen any similar behavior.
> >
> > When running with 2 serial ports, any input from a serial terminal
> > running at the wrong baud rate (9600 instead of 115.2K) on a 2nd shell
> > (not the console shell) causes the kernel to lock up. It doesn't
> > crash, I'm still trying to understand what it's doing. I can no
> > longer ping the board as the network was working prior.
> >
> > I just wanted to make sure there's not any known tty issues related to
> > this.
>
> There are some odd issues with stuff in this area, care to try 3.0-rc3
> and see if the problem is there as well or not?
If its driver specific as this seems I'd take a guess on the driver for
the hardware not properly handling framing errors or break so you get an
irq storm or some other failure from the framing error.
next prev parent reply other threads:[~2011-06-16 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1719676005.1623192.1308182800563.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
2011-06-16 0:09 ` kernel lockup due to bad baud rate data johnlinn
2011-06-16 0:21 ` Greg KH
2011-06-16 8:19 ` Alan Cox [this message]
2011-06-16 13:31 ` johnlinn
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=20110616091928.1aa28c86@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=johnlinn@comcast.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox