linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Michael.McTernan.2001@cs.bris.ac.uk (Michael McTernan)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: iMX: lockup with irqs disabled in drivers/tty/imx.c
Date: Fri, 15 Jun 2012 09:36:14 +0100	[thread overview]
Message-ID: <4FDAF3FE.7000907@cs.bris.ac.uk> (raw)
In-Reply-To: <CAOMZO5CDoJm8QgeA=r6k+hcZ-Z8sGZ19AgA1d8wWTGh3PaXmoQ@mail.gmail.com>

On 06/12/2012 07:53 PM, Fabio Estevam wrote:
>> I can then trigger the lockup by simply booting the unit and issuing "echo>
>> /dev/ttymxc1".  The same can be done on the other ports too. Once locked,
>> magic sys-req appears not to work, pinging the target is dead etc...
>
> I did a 'echo "hello">  /dev/ttymxc1' and I am not able to see the
> lockup on a mx31pdk running 3.5-rc1.

Depending on the setup and board, you may find that the RTS pin is 
asserted so you don't hit the lockup, or more likely, that the Rx pin is 
being driven by a RS232 level shifter so you don't get the early break 
character which triggers the problem.

On my board the RTS will never be set and the Rx pin is pulled low so 
generates a break condition and lockup reliably (prior to patching).

I don't have a i.MX31 reference manual or PDK schematic, but you may be 
able to change the IO mux config to move the serial port Rx and RTS to 
free pins with pull downs in order to reproduce the bug.

This bug is very much a corner case, and arguably the hardware 
setup/board config isn't right, but for the sake of a few lines of code 
it would seem better to avoid such as nasty lockup which isn't 
straightforward to debug.

Regards,

Mike

      reply	other threads:[~2012-06-15  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-20 11:04 ARM: iMX: lockup with irqs disabled in drivers/tty/imx.c Michael McTernan
2012-06-04 16:54 ` manfred.schlaegl at gmx.at
2012-06-10 17:38 ` Fabio Estevam
2012-06-12 18:53 ` Fabio Estevam
2012-06-15  8:36   ` Michael McTernan [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=4FDAF3FE.7000907@cs.bris.ac.uk \
    --to=michael.mcternan.2001@cs.bris.ac.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).