From: Greg KH <gregkh@linuxfoundation.org>
To: Sven Lahr <Sven.Lahr@biotage.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: FTDI spontanteous disconnect/reconnect
Date: Thu, 3 Apr 2014 11:01:02 -0700 [thread overview]
Message-ID: <20140403180102.GA21565@kroah.com> (raw)
In-Reply-To: <3F4B290D8BFAD2458191EB243C0592C4850B0D4EC9@seuppms301>
On Thu, Apr 03, 2014 at 07:03:13PM +0200, Sven Lahr wrote:
> Hi there
>
> I work for a company that produces a system that contains a device with an FTDI 232R chip, as well as a Linux (Debian) computer that the device is attached to.
> We often get reports from our customers that the device is
> disconnected, and then reconnected shortly thereafter. I have searched
> the web, and apparently quite a lot of people experience this when
> they use the Linux driver.
The driver can't disconnect itself from the bus, that sounds like an
electrical issue.
> I wonder if there is any plan to fix this. From what I can tell the
> Linux driver hasn't been updated in 5 years.
Where are you looking? The in-kernel driver is updated all the time.
>
> Below I have pasted the relevant part of my kernel log.
>
>
> Best regards
> Sven Lähr, Biotage AB, Sweden
>
> Feb 27 19:45:44 kernel: [ 936.368366] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
> Feb 27 19:45:44 kernel: [ 936.368379] ftdi_sio 4-2:1.0: device disconnected
> Feb 27 19:45:44 kernel: [ 936.608030] usb 4-2: new full-speed USB device number 3 using uhci_hcd
> Feb 27 19:45:44 kernel: [ 936.806105] usb 4-2: New USB device found, idVendor=0403, idProduct=6001
> Feb 27 19:45:44 kernel: [ 936.806110] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> Feb 27 19:45:44 kernel: [ 936.806115] usb 4-2: Product: FT232R USB UART
> Feb 27 19:45:44 kernel: [ 936.806118] usb 4-2: Manufacturer: FTDI
> Feb 27 19:45:44 kernel: [ 936.806121] usb 4-2: SerialNumber: A602WS4T
> Feb 27 19:45:44 kernel: [ 936.814150] ftdi_sio 4-2:1.0: FTDI USB Serial Device converter detected
> Feb 27 19:45:44 kernel: [ 936.814195] usb 4-2: Detected FT232RL
> Feb 27 19:45:44 kernel: [ 936.814198] usb 4-2: Number of endpoints 2
> Feb 27 19:45:44 kernel: [ 936.814201] usb 4-2: Endpoint 1 MaxPacketSize 64
> Feb 27 19:45:44 kernel: [ 936.814205] usb 4-2: Endpoint 2 MaxPacketSize 64
> Feb 27 19:45:44 kernel: [ 936.814208] usb 4-2: Setting MaxPacketSize 64
> Feb 27 19:45:44 kernel: [ 936.816223] usb 4-2: FTDI USB Serial Device converter now attached to ttyUSB1
That shows the device disconnecting itself, and then coming back.
Perhaps something is lowering the voltage on the device such that the
host thinks it is gone?
Again, this isn't something that the driver can even do, so I'd start
looking for physical issues first.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-04-03 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 17:03 FTDI spontanteous disconnect/reconnect Sven Lahr
2014-04-03 18:01 ` Greg KH [this message]
2014-04-04 6:13 ` FW: " Sven Lahr
2014-04-04 6:31 ` Mats Kärrman
2014-04-04 15:34 ` FW: " Greg KH
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=20140403180102.GA21565@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Sven.Lahr@biotage.com \
--cc=linux-serial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.