From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Hurley Subject: Re: n_tty_write() going into schedule but NOT coming out Date: Fri, 05 Apr 2013 15:52:47 -0400 Message-ID: <1365191567.3585.10.camel@thor.lan> References: <5156DC21.20901@synopsys.com> <5159925B.5050806@synopsys.com> <1364829008.3617.21.camel@thor.lan> <515ADC96.7090908@synopsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from mailout01.c08.mtsvc.net ([205.186.168.189]:52394 "EHLO mailout01.c08.mtsvc.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1162587Ab3DETww (ORCPT ); Fri, 5 Apr 2013 15:52:52 -0400 In-Reply-To: <515ADC96.7090908@synopsys.com> Sender: linux-serial-owner@vger.kernel.org List-Id: linux-serial@vger.kernel.org To: Vineet Gupta Cc: lkml , linux-serial@vger.kernel.org, Jiri Slaby [ --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