From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "oneukum@suse.com" <oneukum@suse.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: ttyACM: disabled by hub (EMI?), re-enabling... Causes garbage chars & disconnect
Date: Mon, 25 May 2020 15:15:20 +0000 [thread overview]
Message-ID: <b39259fc7f397b27f4af145eeafb33ec36638660.camel@infinera.com> (raw)
In-Reply-To: <1590418977.2838.16.camel@suse.com>
On Mon, 2020-05-25 at 17:02 +0200, Oliver Neukum wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> Am Montag, den 25.05.2020, 14:46 +0000 schrieb Joakim Tjernlund:
>
> > This (EMI?) disconnect causes 2 things.
> > 1) I loose the TTY temporarily and have to reconnect.
>
> Unfortunately I see no way to reestablish contact transparantly
> on the level of the driver.
>
> > 2) After reconnect there are garbage chars on the gadget side, such as:
> > h�^@^@� ^@^@� ^@
>
> This looks like MM is acting up in user space.
>
> > or
> > X���)H��4Ğ^���
> > which causes confusion on for the tty/bash on the gadget.
> >
> > The disconnect is mostly just annoying but the garbage chars are a major pain, one cannot trust
> > that cmds are understod. Is there a bug in ttyACM driver causing these?
>
> Hi,
>
> thanks for the bug report. The most likely cause of your problem is
> ModemManager probing the new device. It has a blacklist.
No, I have already blacklisted this device from modemmanger, is blacklist not reliable in this case?
Jocke
next prev parent reply other threads:[~2020-05-25 15:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 14:46 ttyACM: disabled by hub (EMI?), re-enabling... Causes garbage chars & disconnect Joakim Tjernlund
2020-05-25 15:02 ` Oliver Neukum
2020-05-25 15:15 ` Joakim Tjernlund [this message]
2020-05-25 16:49 ` Joakim Tjernlund
2020-05-26 8:47 ` Oliver Neukum
2020-05-26 8:59 ` Joakim Tjernlund
2020-05-26 10:14 ` Oliver Neukum
2020-05-26 16:46 ` Joakim Tjernlund
2020-05-26 17:19 ` Joakim Tjernlund
2020-05-27 8:38 ` Oliver Neukum
2020-05-27 9:40 ` Joakim Tjernlund
2020-05-27 10:12 ` Greg KH
2020-05-27 10:41 ` Oliver Neukum
2020-05-27 13:16 ` Joakim Tjernlund
2020-05-27 15:41 ` Joakim Tjernlund
2020-06-05 10:09 ` Joakim Tjernlund
2020-06-08 9:13 ` Oliver Neukum
2020-06-08 11:39 ` Joakim Tjernlund
2020-06-08 15:40 ` Oliver Neukum
2020-06-08 16:00 ` Joakim Tjernlund
2020-06-08 19:21 ` Oliver Neukum
2020-06-15 11:01 ` Joakim Tjernlund
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=b39259fc7f397b27f4af145eeafb33ec36638660.camel@infinera.com \
--to=joakim.tjernlund@infinera.com \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
/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).