Bug 1029758 - cp210x usb serial port controller instant disconnect
Summary: cp210x usb serial port controller instant disconnect
Status: RESOLVED DUPLICATE of bug 1007652
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Current
Hardware: x86-64 Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Oliver Neukum
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-16 16:57 UTC by Josua Mayer
Modified: 2017-03-23 14:03 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
complete dmesg (25.71 KB, application/gzip)
2017-03-16 17:01 UTC, Josua Mayer
Details
rpm -qa | sort (202.86 KB, text/plain)
2017-03-22 07:06 UTC, Josua Mayer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Josua Mayer 2017-03-16 16:57:23 UTC
Since 4.10.0 both of my devices featuring a cp210x usb to serial converter stopped working.

dmesg after connecting:
[ 1467.142430] usb 1-1.1: new full-speed USB device number 7 using ehci-pci
[ 1467.281679] usb 1-1.1: New USB device found, idVendor=10c4, idProduct=ea60
[ 1467.281682] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1467.281683] usb 1-1.1: Product: CP2102 USB to UART Bridge Controller
[ 1467.281684] usb 1-1.1: Manufacturer: Silicon Labs
[ 1467.281685] usb 1-1.1: SerialNumber: 0001
[ 1467.289726] cp210x 1-1.1:1.0: cp210x converter detected
[ 1467.291959] usb 1-1.1: cp210x converter now attached to ttyUSB0
[ 1467.383699] usb 1-1.1: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1
[ 1467.385369] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[ 1467.385403] cp210x 1-1.1:1.0: device disconnected

As can be seen the ttyUSB0 appears to disconnect immediately, but I am not that fast.

I have so far ruled out:
1) the cable (using windows on same pc, all good)
2) the device (using another PC running 42.2)

Is anyone else seeing this? any ideas what to do about it?
Comment 1 Josua Mayer 2017-03-16 17:01:33 UTC
Created attachment 717747 [details]
complete dmesg
Comment 2 Oliver Neukum 2017-03-21 22:34:14 UTC
A braille reader takes the device. We actually already had a very similar bug.
A package took over devices blindly.
Please provide the output of "rpm -qa"
Comment 3 Josua Mayer 2017-03-22 07:06:32 UTC
Created attachment 718302 [details]
rpm -qa | sort
Comment 4 Oliver Neukum 2017-03-23 14:03:44 UTC
The issue with brltty taking devices is still open and also affects your device.

*** This bug has been marked as a duplicate of bug 1007652 ***