From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Johan Hovold <jhovold@gmail.com>,
Peter Korsgaard <jacmet@sunsite.dk>,
Alan Cox <alan@linux.intel.com>,
Preston Fick <preston.fick@silabs.com>
Subject: Re: 3.7.3, ttyUSB0 serial problem - devices stop working and only reboot helps (Inappropriate ioctl for device)
Date: Sat, 19 Jan 2013 09:18:36 +0100 [thread overview]
Message-ID: <201301190918.37001.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <20130119004732.GA32311@kroah.com>
On Saturday 19 of January 2013, Greg Kroah-Hartman wrote:
> On Fri, Jan 18, 2013 at 11:28:43PM +0100, Arkadiusz Miskiewicz wrote:
> > Hi.
> >
> > Using 3.7.3 kernel and connecting two rs232 usb adapters, CP2102 and
> > FT232RL, one after disconnecting another.
> >
> > After few cycles of reconnecting and using socat (below) I'm getting
> > problems accessing ttyUSB0:
> > ioctl(3, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS,
> > 0x7fffb70c6ae0) = -1 ENOTTY (Inappropriate ioctl for device)
> >
> > Unloading and reloading (by udev) modules ftdio_sio, cp210x, usbserial
> > doesn't help. I have to reboot to get ttyUSB0 working (regardless of
> > which driver, ftdio_sio or cp210x is handling ttyUSB0 - both stop
> > working).
> >
> > Any clues?
>
> The kernel log shows the device getting removed a bunch and then coming
> back, which implies electrical issues (flaky connection, low power,
> etc.) Are you really removing it and plugging it back in? Or is it
> doing it all by itself?
I was doing plug in CP2102, remove it, plug in FT232RL after few seconds,
remove it, plug in CP... (and various variations, several times) and testing
with socat before removing devices. After some iteration the problem appears
and only reboot helps.
Reproducible. suspend to ram/resume cycle didn't change anything, device still
has a problem, even after reconnection of device.
>
> thanks,
>
> greg k-h
--
Arkadiusz Miśkiewicz, arekm / maven.pl
next prev parent reply other threads:[~2013-01-19 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 22:28 3.7.3, ttyUSB0 serial problem - devices stop working and only reboot helps (Inappropriate ioctl for device) Arkadiusz Miskiewicz
2013-01-19 0:47 ` Greg Kroah-Hartman
2013-01-19 8:18 ` Arkadiusz Miskiewicz [this message]
2013-01-19 8:48 ` Arkadiusz Miskiewicz
2013-01-20 2:19 ` Woody Suwalski
2013-01-20 9:04 ` Arkadiusz Miskiewicz
2013-01-20 12:26 ` Arkadiusz Miskiewicz
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=201301190918.37001.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacmet@sunsite.dk \
--cc=jhovold@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=preston.fick@silabs.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