From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753914Ab2IGNJh (ORCPT ); Fri, 7 Sep 2012 09:09:37 -0400 Received: from inx.pm.waw.pl ([195.116.170.130]:42031 "EHLO inx.pm.waw.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752954Ab2IGNJg (ORCPT ); Fri, 7 Sep 2012 09:09:36 -0400 X-Greylist: delayed 607 seconds by postgrey-1.27 at vger.kernel.org; Fri, 07 Sep 2012 09:09:35 EDT From: Krzysztof Halasa To: khalasa@piap.pl (Krzysztof =?utf-8?Q?Ha=C5=82asa?=) Cc: Alan Cox , linux-kernel@vger.kernel.org Subject: Re: 3.4.10 N_GSM tty_io WARNING and lockup References: <20120906140137.75ebe6ba@pyramind.ukuu.org.uk> Date: Fri, 07 Sep 2012 14:59:26 +0200 In-Reply-To: ("Krzysztof =?utf-8?Q?Ha=C5=82as?= =?utf-8?Q?a=22's?= message of "Fri, 07 Sep 2012 13:07:20 +0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > In the meantime I've rebased to v3.5.3 and it started to work. Do you > think it is worth it investigating v3.4.10 at this point? BTW I'm not sure if it's a known bug: I closed the /dev/ttyS0 with /dev/gsmmuxX still open, and then tried to set N_TTY ldisc on the master device. It didn't work so well :-( # killall -9 microcom # they use /dev/gsmmux[0-3] # killall -9 iru # the program messing with ldiscs # ps axf 344 ? Ss 0:00 \_ sshd: root@pts/1 346 pts/1 Ss 0:00 | \_ -sh 405 pts/1 D+ 0:00 | \_ [microcom] 347 ? Ss 0:00 \_ sshd: root@pts/2 349 pts/2 Ss 0:00 | \_ -sh 403 pts/2 D+ 0:00 | \_ [microcom] 406 ? Ss 0:00 \_ sshd: root@pts/3 408 pts/3 Ss 0:00 | \_ -sh 412 pts/3 D+ 0:00 | \_ [microcom] 409 ? Ss 0:00 \_ sshd: root@pts/4 411 pts/4 Ss 0:00 \_ -sh 413 pts/4 D+ 0:00 \_ [microcom] 415 pts/0 D 0:00 iru -- Krzysztof Halasa