All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	linux-serial@vger.kernel.org, Jiri Slaby <jslaby@suse.cz>
Subject: Re: n_tty_write() going into schedule but NOT coming out
Date: Fri, 05 Apr 2013 15:52:47 -0400	[thread overview]
Message-ID: <1365191567.3585.10.camel@thor.lan> (raw)
In-Reply-To: <515ADC96.7090908@synopsys.com>

[ --cc Ingo and Peter Z. as this is not scheduler-related]

On Tue, 2013-04-02 at 18:56 +0530, Vineet Gupta wrote:
> On 04/01/2013 08:40 PM, Peter Hurley wrote:
> > On Mon, 2013-04-01 at 19:27 +0530, Vineet Gupta wrote:
> >> Hi,
> >>
> >> Any thoughts: I observe the same issue even with CONFIG_PREEMPT and
> >> CONFIG_PREEMPT_COUNT

I'll see if I can reproduce this over the weekend on an old single-core
laptop I still have.

There were some race conditions in the N_TTY line discipline which I
recently fixed. Those changes are in linux-next. Can you test if this is
reproducible on linux-next?

Assuming I don't reproduce this on the laptop, the only other
explanation I can think of right now is that ARCLinux is not properly
handling signal-driven i/o (assuming the BusyBox /bin/sh uses SIGIO). Do
you know if there is anything special about the way ARCLinux handle
signals?

Regards,
Peter Hurley


  parent reply	other threads:[~2013-04-05 19:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-30 12:35 n_tty_write() going into schedule but NOT coming out Vineet Gupta
2013-03-30 12:35 ` Vineet Gupta
2013-04-01 13:57 ` Vineet Gupta
2013-04-01 13:57   ` Vineet Gupta
2013-04-01 15:10   ` Peter Hurley
2013-04-02 11:09     ` Vineet Gupta
2013-04-02 11:09       ` Vineet Gupta
2013-04-02 13:26     ` Vineet Gupta
2013-04-02 13:26       ` Vineet Gupta
2013-04-02 13:38       ` Peter Hurley
2013-04-05 19:52       ` Peter Hurley [this message]
2013-04-06  9:32         ` Vineet Gupta
2013-04-06  9:32           ` Vineet Gupta
2013-04-03  5:44 ` Ilya Zykov
2013-04-03  7:42   ` Vineet Gupta
2013-04-03  7:42     ` Vineet Gupta

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=1365191567.3585.10.camel@thor.lan \
    --to=peter@hurleysoftware.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.