linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: markh@compro.net
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux-kernel <linux-kernel@vger.kernel.org>,
	Mark Hounschell <dmarkh@cfl.rr.com>
Subject: Re: tty  TTY_HUPPED anomaly
Date: Wed, 04 Jan 2012 21:28:13 +0100	[thread overview]
Message-ID: <4F04B65D.6070505@suse.cz> (raw)
In-Reply-To: <4F04A187.2050705@compro.net>

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,
-- 
js
suse labs

  reply	other threads:[~2012-01-04 20:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 14:51 tty TTY_HUPPED anomaly Mark Hounschell
2011-12-23 18:46 ` Mark Hounschell
2011-12-23 20:40   ` Alan Cox
2012-01-04 15:59     ` Mark Hounschell
2012-01-04 16:27       ` Alan Cox
2012-01-04 18:59         ` Mark Hounschell
2012-01-04 20:28           ` Jiri Slaby [this message]
2012-01-04 20:35             ` Mark Hounschell
2012-01-04 20:40               ` Jiri Slaby
2012-01-04 20:50                 ` Mark Hounschell

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=4F04B65D.6070505@suse.cz \
    --to=jslaby@suse.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dmarkh@cfl.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.net \
    /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).