From: e9hack <e9hack@googlemail.com>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>
Subject: Trouble with USB serial driver (ftdi_sio.c) on 2.6.31
Date: Sat, 12 Sep 2009 14:08:31 +0200 [thread overview]
Message-ID: <4AAB8F3F.40403@googlemail.com> (raw)
Hi,
I've some trouble with the USB serial driver (ftdi_sio.c for a FT232RL from FTDI). If the
port is opened for the first time, the driver works perfectly. If the port is closed and
open again, it isn't possible to read any data from port. Writing data to the port works.
The FT232RL must be reconnect to get it working again. A reboot without reconnect doesn't
solve this problem. If I look at the debug output, I don't see read requests from
ftdi_sio.c. If reading is possible, I see this read messages:
...
Sep 12 13:36:21 vdr kernel: [ 147.338926]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: Status only: 001o 000o
Sep 12 13:36:21 vdr kernel: [ 147.339921]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_read_bulk_callback - port 0
Sep 12 13:36:21 vdr kernel: [ 147.339927]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_process_read - port 0
Sep 12 13:36:21 vdr kernel: [ 147.339930]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: Status only: 001o 000o
Sep 12 13:36:21 vdr kernel: [ 147.340931]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_read_bulk_callback - port 0
Sep 12 13:36:21 vdr kernel: [ 147.340936]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_process_read - port 0
Sep 12 13:36:21 vdr kernel: [ 147.340940]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: Status only: 001o 000o
Sep 12 13:36:21 vdr kernel: [ 147.341927]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_read_bulk_callback - port 0
Sep 12 13:36:21 vdr kernel: [ 147.341932]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_process_read - port 0
Sep 12 13:36:21 vdr kernel: [ 147.341936]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: Status only: 001o 000o
Sep 12 13:36:21 vdr kernel: [ 147.342924]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_read_bulk_callback - port 0
Sep 12 13:36:21 vdr kernel: [ 147.342928]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_process_read - port 0
Sep 12 13:36:21 vdr kernel: [ 147.342932]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: Status only: 001o 000o
Sep 12 13:36:21 vdr kernel: [ 147.343924]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_read_bulk_callback - port 0
Sep 12 13:36:21 vdr kernel: [ 147.343929]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_process_read - port 0
Sep 12 13:36:21 vdr kernel: [ 147.343933] ftdi_sio ttyUSB0: ftdi_process_read - length =
7, data = 01 00 aa 40 0a 00 64
Sep 12 13:36:21 vdr kernel: [ 147.344930]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_read_bulk_callback - port 0
Sep 12 13:36:21 vdr kernel: [ 147.344936]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_process_read - port 0
Sep 12 13:36:21 vdr kernel: [ 147.344940]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: Status only: 001o 000o
Sep 12 13:36:21 vdr kernel: [ 147.345923]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_read_bulk_callback - port 0
Sep 12 13:36:21 vdr kernel: [ 147.345928]
/usr/src/linux-2.6.31-rc3/drivers/usb/serial/ftdi_sio.c: ftdi_process_read - port 0
...
This occurs with 2.6.31 and 2.6.31-rc3. I don't see this problem with 2.6.30.5. It exist
one exception: If I reboot from 2.6.31 to 2.6.30.5, I get the same problem. If I reconnect
the FT232RL, the FT232RL works perfectly. I don't see any problems after closing and
reopening.
Regards,
Hartmut
next reply other threads:[~2009-09-12 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 12:08 e9hack [this message]
2009-09-14 16:43 ` Trouble with USB serial driver (ftdi_sio.c) on 2.6.31 Greg KH
2009-09-14 22:28 ` Johan Hovold
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=4AAB8F3F.40403@googlemail.com \
--to=e9hack@googlemail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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