From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756895Ab2ADUu2 (ORCPT ); Wed, 4 Jan 2012 15:50:28 -0500 Received: from mx2.compro.net ([12.186.155.4]:43786 "EHLO mx2.compro.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756337Ab2ADUu0 (ORCPT ); Wed, 4 Jan 2012 15:50:26 -0500 X-IronPort-AV: E=Sophos;i="4.71,458,1320642000"; d="scan'208";a="7462238" Message-ID: <4F04BB90.7090000@compro.net> Date: Wed, 04 Jan 2012 15:50:24 -0500 From: Mark Hounschell Reply-To: markh@compro.net Organization: Compro Computer Svcs. User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: Jiri Slaby CC: Alan Cox , Linux-kernel , Mark Hounschell , Jiri Slaby Subject: Re: tty TTY_HUPPED anomaly References: <4EF49579.9040907@compro.net> <4EF4CC92.5090502@compro.net> <20111223204015.541924f2@pyx> <4F047767.5060708@compro.net> <20120104162745.76fc3852@pyramind.ukuu.org.uk> <4F04A187.2050705@compro.net> <4F04B65D.6070505@suse.cz> <4F04B7FF.5010906@compro.net> <4F04B957.3000408@suse.cz> In-Reply-To: <4F04B957.3000408@suse.cz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/04/2012 03:40 PM, Jiri Slaby wrote: > On 01/04/2012 09:35 PM, Mark Hounschell wrote: >> On 01/04/2012 03:28 PM, Jiri Slaby wrote: >>> On 01/04/2012 07:59 PM, Mark Hounschell wrote: >>>>> I would guess (given the distro change is the trigger) that you've >>>>> got a >>>>> SuSE problem not a kernel one. The kernel behaviour and code looks >>>>> correct. My guess therefore is that newer SuSE is running stuff in the >>>>> boot which is probing serial ports and messing with the carrier wrongly >>>>> and in ways it didn't use to. That would fit the fact that something >>>>> similarly broken has apparently also appeared in the Fedora user space >>>>> bootup. >>> >>> And we (suse) have a report for enterprise, that says ModemManager >>> causes a similar issue. Could you perhaps check whether you have that >>> thing installed? >>> >>> thanks, >> >> Yep. ModemManager-0.5-3.1.3.i586 > > And what happens if you remove that? > It seems to fix my problem. Thanks for stepping in. I was about to take this to the SuSE-e list. Anything else ya need, let me know. Mark