[Bug 1093378] New: conflicting udev rules completely break USB Serial bridges - openSUSE Bugs - openSUSE Mailing Lists

newer
[Bug 1052058] Gnome:...

[Bug 1093378] New: conflicting udev rules completely break USB Serial bridges

older
[Bug 1121188] New:...

bugzilla_noreply＠novell.com

15 May 2018 15 May '18

15:12

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 Bug ID: 1093378 Summary: conflicting udev rules completely break USB Serial bridges Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: sbrabec@suse.com QA Contact: qa-bugs@suse.de CC: jreuter@suse.com, kkaempf@suse.com, matwey.kornilov@gmail.com, mbrugger@suse.com, mgorse@suse.com, oneukum@suse.com, ro@suse.com, sckang@suse.com, sndirsch@suse.de, stefan.bruens@rwth-aachen.de, trenn@suse.com Depends on: 1092839, 1007652 Found By: --- Blocker: --- Following USB ids represent most common generic USB UART Bridges: 10C4:EA60 CP210x UART Bridge https://usb-ids.gowdy.us/read/UD/10c4/ea60 10C4:EA80 CP2110 HID UART Bridge https://usb-ids.gowdy.us/read/UD/10c4/ea80 0403:6001 FT232 USB-Serial (UART) IC https://usb-ids.gowdy.us/read/UD/0403/6001 (There are more such chips and ids) Many hardware vendors ignore rules and sell their products with this generic USB ids. As as result, plugging of such device starts an udev rule fight, which actually ends by a completely non-functional device. Actually, these applications fight for these devices: brttty: Recognizes it as a Braille terminal or display (bug 1092839) upower: Recognizes it as a Watts Up? Pro gpsd: Recognizes it as SiRF Star III 20ch Gmouse GPS (or another GPS device for other ids) ModemManager: Recognizes it as a modem candidate argyllcms: Recognized as JETI & KLEIN Spectrophotometer (bug 1007652, already fixed) Other packages that might attempt to steal these ids as well (or at least did it in past): avrdude: Recognizes it as a AVR programmer sigrok: Recognizes it as CEM DT-8852, Dangerous Prototypes Buspirate, ChronoVu LA8, ChronoVu LA16 openocd: Sets it up as a serial bridge to the embedded device (hopefully, only privileges are set) Found by: grep -ir '\(6001\|ea60\|ea80\)' /usr/lib/udev/rules.d /etc/udev/rules.d If hardware vendors ignore rules and release a device with a USB UART Bridge id and textual identification, Linux has no chance to recognize the device plugged. -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 4.6 KB)

Reply

Sign in to reply online Use email software

Show replies by date

bugzilla_noreply＠novell.com

15 May 15 May

15:43

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c1 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |systemd-maintainers@suse.de --- Comment #1 from Stanislav Brabec --- If the device cannot be identified by a textual identification, we either have to give up and let user to configure it manually, use serial probe (dangerous) or user assisted check. I am afraid, that this situation has no easy solution. I can imagine something like an user-assisted udev rules. Desktop system would ask e. g.: USB device with generic FT232 USB-Serial (UART) IC identified Please select the correct device: Serial port Serial modem QStarz GPS device Seika Braille display Watts Up? Pro ... [checkbox] Remember for this port only Remember for [1 hour] Notes: - It seems that udev currently does not support physical USB port based rules. - Braille devices need a special support, as these have to be supported during the installation. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15:53

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |behlert@suse.com Flags| |needinfo?(behlert@suse.com) -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15:57

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c3 --- Comment #3 from Matwey Kornilov --- So, what is exact issue here? I mean what is the way to make completely non-functional device by concurrent udev rules? -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

16:04

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC|sndirsch@suse.de | -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

18:27

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c4 --- Comment #4 from Stanislav Brabec --- Currently, brltty is a part of the default installation that includess gdm (gdm recommends orca, orca recomments brltty). brltty attempts to rebind the USB serial port to uinput. In the same moment, gpsd attempts to start GPS daemon on the serial port, and upower attempts to bind power meter. As a result, /dev/ttyUSB0 disappears (see bug 1092839). kvě 15 15:59:04 goblin.suse.cz kernel: usb 1-1.6: new full-speed USB device number 14 using ehci-pci kvě 15 15:59:04 goblin.suse.cz kernel: usb 1-1.6: New USB device found, idVendor=10c4, idProduct=ea60 kvě 15 15:59:04 goblin.suse.cz kernel: usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kvě 15 15:59:04 goblin.suse.cz kernel: usb 1-1.6: Product: CP2102 USB to UART Bridge Controller kvě 15 15:59:04 goblin.suse.cz kernel: usb 1-1.6: Manufacturer: Silicon Labs kvě 15 15:59:04 goblin.suse.cz kernel: usb 1-1.6: SerialNumber: 0001 kvě 15 15:59:04 goblin.suse.cz kernel: cp210x 1-1.6:1.0: cp210x converter detected kvě 15 15:59:04 goblin.suse.cz kernel: usb 1-1.6: cp210x converter now attached to ttyUSB0 kvě 15 15:59:04 goblin.suse.cz mtp-probe[30348]: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6" kvě 15 15:59:04 goblin.suse.cz mtp-probe[30348]: bus: 1, device: 14 was not an MTP device kvě 15 15:59:04 goblin.suse.cz /usr/lib/gdm/gdm-x-session[11355]: (II) config/udev: Adding input device (unnamed) (/dev/ttyUSB0) kvě 15 15:59:04 goblin.suse.cz /usr/lib/gdm/gdm-x-session[11355]: (II) No input driver specified, ignoring this device. kvě 15 15:59:04 goblin.suse.cz /usr/lib/gdm/gdm-x-session[11355]: (II) This device may have been added with another device file. kvě 15 15:59:04 goblin.suse.cz /usr/lib/gdm/gdm-x-session[10039]: (II) config/udev: Adding input device (unnamed) (/dev/ttyUSB0) kvě 15 15:59:04 goblin.suse.cz /usr/lib/gdm/gdm-x-session[10039]: (II) No input driver specified, ignoring this device. kvě 15 15:59:04 goblin.suse.cz /usr/lib/gdm/gdm-x-session[10039]: (II) This device may have been added with another device file. kvě 15 15:59:04 goblin.suse.cz upowerd[10080]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 15 15:59:04 goblin.suse.cz upowerd[10080]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6 kvě 15 15:59:08 goblin.suse.cz brltty[29484]: USB configuration set error 16: Zařízení nebo zdroj jsou používány. kvě 15 15:59:08 goblin.suse.cz brltty-systemd-wrapper[29484]: brltty: USB configuration set error 16: Zařízení nebo zdroj jsou používány. kvě 15 15:59:08 goblin.suse.cz brltty-systemd-wrapper[29484]: brltty: USB interface in use: 0 (cp210x) kvě 15 15:59:08 goblin.suse.cz brltty[29484]: USB interface in use: 0 (cp210x) kvě 15 15:59:08 goblin.suse.cz kernel: usb 1-1.6: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 kvě 15 15:59:08 goblin.suse.cz kernel: cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 kvě 15 15:59:08 goblin.suse.cz kernel: cp210x 1-1.6:1.0: device disconnected kvě 15 15:59:08 goblin.suse.cz systemd-udevd[30365]: Process 'gpsd.sh' failed with exit code 1. kvě 15 15:59:08 goblin.suse.cz upowerd[10080]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 15 15:59:08 goblin.suse.cz upowerd[10080]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 15 15:59:08 goblin.suse.cz brltty[29484]: Ignored Byte: 00 kvě 15 15:59:08 goblin.suse.cz brltty-systemd-wrapper[29484]: brltty: Ignored Byte: 00 kvě 15 15:59:10 goblin.suse.cz upowerd[10080]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 15 15:59:10 goblin.suse.cz upowerd[10080]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 15 15:59:12 goblin.suse.cz upowerd[10080]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 15 15:59:13 goblin.suse.cz upowerd[10080]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 15 15:59:16 goblin.suse.cz upowerd[10080]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 15 15:59:16 goblin.suse.cz upowerd[10080]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 15 15:59:18 goblin.suse.cz upowerd[10080]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 15 15:59:18 goblin.suse.cz upowerd[10080]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 ... repeats many times -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

18:43

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c5 --- Comment #5 from Matwey Kornilov --- So, the issue is that udev default rules allows uncontrollable device rebinding. What if we drop this rules and left it for users to allow device rebinding based on USB device serial number (for instance)? There could be template in /etc/udev/rules.d to fill serial and uncoment. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

18:47

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c6 --- Comment #6 from Matwey Kornilov --- The second question is how this VendorID/DeviceID issue is managed on Windows? -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

19:17

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c7 --- Comment #7 from Matwey Kornilov --- (In reply to Matwey Kornilov from comment #6)

The second question is how this VendorID/DeviceID issue is managed on Windows?

Probably they just use USB device class to distinguish different devices. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

19:44

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c8 --- Comment #8 from Stefan Brüns --- (In reply to Matwey Kornilov from comment #5)

So, the issue is that udev default rules allows uncontrollable device rebinding. What if we drop this rules and left it for users to allow device rebinding based on USB device serial number (for instance)? There could be template in /etc/udev/rules.d to fill serial and uncoment.

Silabs (CP210x) USB-serial chips can be reprogrammed (http://cp210x-program.hg.sourceforge.net/hgweb/cp210x-program/cp210x-program...) with unique serial numbers, but everything you get from your friendly least-untrusted internet seller has a "0" as its serial number. I don't know about the Braille devices, but if these vendors are incapable to request a Product ID from the chip vendor, they don't likely care for useful serial numbers (other than "1234ABCD"). ModemManager IIRC actually has a sensible approach, it white- or graylists items. Whitelisted items are guaranteed to be modems (e.g. by correct USB VID/PID, interface), graylisted items are allowed to be probed manually. We have two/three? different classes of services using these "serial" ports: - programms acessing the port on request, e.g. argyllcms, sigrok, avrdude - daemons running as a system service (upower, ModemManager, gpsd, ...) - daemons running in a user session? Critical are the ones in the second group, as these may be fighting over the device. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

19:48

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c9 --- Comment #9 from Stefan Brüns --- (In reply to Matwey Kornilov from comment #7)

(In reply to Matwey Kornilov from comment #6)

...
The second question is how this VendorID/DeviceID issue is managed on Windows?

Probably they just use USB device class to distinguish different devices.

They probably just install software package to access the device, not multiple, and configure it explicitly. I am quite sure if you e.g. install a braille device and a GPS mouse with the same serial converter chip and swap the USB port you end up with two unusable devices. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

16 May 16 May

14:28

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c10 --- Comment #10 from Stanislav Brabec --- I can confirm the worst case. Manufacturers violate all rules, and the don't change USB id nor textual identification, and even don't set a serial number. Even very expensive Braille devices seems to do that. Different devices are completely undistinguishable on USB level (just by port and additional knowledge). For these USB ids, we are back in the serial port age: Try to guess by protocol, configure manually or invent user assisted udev rules using a desktop helper. In case of Braille devices, I discuss a chance for user assisted identification by the installer. https://brltty.app/pipermail/brltty/2018-May/015936.html OBS check that will generate error for any rules attempting to re-purpose any of generic USB UART, USB I2C and USB SPI bridges ids would be very useful. Example, my QStarz BT-Q1000P GPS uses: USB device strings: Mfr=1, Product=2, SerialNumber=3 idVendor 0x10c4 Cygnal Integrated Products, Inc. idProduct 0xea60 CP2102/CP2109 UART Bridge Controller [CP210x family] iManufacturer 1 Silicon Labs iProduct 2 CP2102 USB to UART Bridge Controller iSerial 3 0001 Cheap Chinese devices often use USB id squatting, which is better in this case. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15:45

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c11 --- Comment #11 from Stefan Brüns --- Regarding udev/port identification comment on the brltty ML: You can identify the physical location of a device from its devpath, which is available in udev, e.g.: $> ls -l /sys/bus/usb/devices/ | egrep '3-[24]:' lrwxrwxrwx 1 root root 0 Mai 16 17:33 3-2:1.0 -> ../../../devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/ lrwxrwxrwx 1 root root 0 Mai 16 17:33 3-4:1.0 -> ../../../devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0/ $> lsusb -t | grep -A10 'Bus 03' | egrep 'Bus |Port [24]:' /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M |__ Port 4: Dev 5, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M i.e. in the devpath you have '<Bus>-<Port>:.<Interface>' Note, logical port numbers may differ from the physical ordering on the hub. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15:58

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c12 --- Comment #12 from Stefan Brüns --- Regarding probing of serial devices: There is active probing and passive probing. If you e.g. read: https://github.com/brltty/brltty/blob/master/Drivers/Braille/Albatross/brail... and https://github.com/brltty/brltty/blob/master/Drivers/Braille/Albatross/brail... it opens the port in turn with 9600 and 19200 baud, waits for a '0xff, 0xfe, 0xff, 0xfe' sequence, and only then starts replying. I think this is considerably save, and could stay activated. It would be nice to have a list of devices capable of passive probing, I think this would narrow down the number of undetectable devices considerably. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

16:29

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c13 --- Comment #13 from Stanislav Brabec --- Looking at strace log, it seems that brltty indeed does a probe, but it loops forever on a bare CP2101 device. And if I kill brltty, device remains in an unusable state (/dev/ttyS0 does not exist). -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

16:37

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c14 --- Comment #14 from Stefan Brüns --- (In reply to Stanislav Brabec from comment #13)

Looking at strace log, it seems that brltty indeed does a probe, but it loops forever on a bare CP2101 device. And if I kill brltty, device remains in an unusable state (/dev/ttyS0 does not exist).

Can you create a backtrace, to get an idea which device/brltty driver is misbehaving? The driver likely uses libusb to detach the kernel driver, but fails to reattach in case it is forcefully killed. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:54

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c15 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@suse.com --- Comment #15 from Stanislav Brabec --- Created attachment 770488 --> http://bugzilla.opensuse.org/attachment.cgi?id=770488&action=edit strace output Here is a strace output. Console output: brltty -E -n BRLTTY 5.6 rev unknown [http://brltty.com/] brltty: NoSpeech Speech Driver: brltty: Linux Screen Driver: brltty: USB configuration set error 16: Device or resource busy. brltty: USB interface in use: 0 (cp210x) brltty: Ignored Byte: 00 Getting a backtrace would require two computers, as brltty watches for keypresses as well. This strace output was created from a X console from the same machine. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

18:05

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c16 --- Comment #16 from Stanislav Brabec --- Created attachment 770489 --> http://bugzilla.opensuse.org/attachment.cgi?id=770489&action=edit backtrace To prevent catching of key presses, this backtrace was created from another computer. dmesg of the session: [10453.707138] usb 1-1.6: new full-speed USB device number 16 using ehci-pci [10453.817237] usb 1-1.6: New USB device found, idVendor=10c4, idProduct=ea60 [10453.817240] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10453.817241] usb 1-1.6: Product: CP2102 USB to UART Bridge Controller [10453.817242] usb 1-1.6: Manufacturer: Silicon Labs [10453.817243] usb 1-1.6: SerialNumber: 0001 [10453.817940] cp210x 1-1.6:1.0: cp210x converter detected [10453.820806] usb 1-1.6: cp210x converter now attached to ttyUSB0 [10454.714575] usb 1-1.6: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [10454.715351] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [10454.715374] cp210x 1-1.6:1.0: device disconnected [11283.834960] input: BRLTTY 5.6 Linux Screen Driver Keyboard as /devices/virtual/input/input18 [11289.325954] usb 1-1.6: USB disconnect, device number 16 [11291.595554] usb 1-1.6: new full-speed USB device number 17 using ehci-pci [11291.706220] usb 1-1.6: New USB device found, idVendor=10c4, idProduct=ea60 [11291.706227] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [11291.706231] usb 1-1.6: Product: CP2102 USB to UART Bridge Controller [11291.706235] usb 1-1.6: Manufacturer: Silicon Labs [11291.706238] usb 1-1.6: SerialNumber: 0001 [11291.707348] cp210x 1-1.6:1.0: cp210x converter detected [11291.709657] usb 1-1.6: cp210x converter now attached to ttyUSB0 [11291.973045] usb 1-1.6: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [11291.973952] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [11291.974015] cp210x 1-1.6:1.0: device disconnected And syslog: syslog indicates that upowerd attempts to access this device even if no rule matches. Even if gpsd udev rule is commented out, I see gpsd.sh in the log. grep -ir 'ea60' /usr/lib/udev/rules.d /etc/udev/rules.d /usr/lib/udev/rules.d/77-mm-usb-serial-adapters-greylist.rules:#ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1" /usr/lib/udev/rules.d/51-gpsd.rules:#KERNEL=="ttyUSB*", ATTR{idVendor}=="10c4", ATTR{idProduct}=="ea60", RUN="gpsd.sh" /usr/lib/udev/rules.d/69-brltty.rules:# Device: 10C4:EA60 /usr/lib/udev/rules.d/69-brltty.rules:#ENV{PRODUCT}=="10c4/ea60/*", ENV{BRLTTY_BRAILLE_DRIVER}="mm,sk", GOTO="brltty_usb_run" kvě 16 19:43:11 goblin.suse.cz kernel: usb 1-1.6: new full-speed USB device number 17 using ehci-pci kvě 16 19:43:12 goblin.suse.cz kernel: usb 1-1.6: New USB device found, idVendor=10c4, idProduct=ea60 kvě 16 19:43:12 goblin.suse.cz kernel: usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kvě 16 19:43:12 goblin.suse.cz kernel: usb 1-1.6: Product: CP2102 USB to UART Bridge Controller kvě 16 19:43:12 goblin.suse.cz kernel: usb 1-1.6: Manufacturer: Silicon Labs kvě 16 19:43:12 goblin.suse.cz kernel: usb 1-1.6: SerialNumber: 0001 kvě 16 19:43:12 goblin.suse.cz kernel: cp210x 1-1.6:1.0: cp210x converter detected kvě 16 19:43:12 goblin.suse.cz kernel: usb 1-1.6: cp210x converter now attached to ttyUSB0 kvě 16 19:43:12 goblin.suse.cz mtp-probe[29137]: checking bus 1, device 17: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6" kvě 16 19:43:12 goblin.suse.cz mtp-probe[29137]: bus: 1, device: 17 was not an MTP device kvě 16 19:43:12 goblin.suse.cz /usr/lib/gdm/gdm-x-session[6005]: (II) config/udev: Adding input device (unnamed) (/dev/ttyUSB0) kvě 16 19:43:12 goblin.suse.cz /usr/lib/gdm/gdm-x-session[2042]: (II) config/udev: Adding input device (unnamed) (/dev/ttyUSB0) kvě 16 19:43:12 goblin.suse.cz /usr/lib/gdm/gdm-x-session[2042]: (II) No input driver specified, ignoring this device. kvě 16 19:43:12 goblin.suse.cz /usr/lib/gdm/gdm-x-session[2042]: (II) This device may have been added with another device file. kvě 16 19:43:12 goblin.suse.cz /usr/lib/gdm/gdm-x-session[6005]: (II) No input driver specified, ignoring this device. kvě 16 19:43:12 goblin.suse.cz /usr/lib/gdm/gdm-x-session[6005]: (II) This device may have been added with another device file. kvě 16 19:43:12 goblin.suse.cz upowerd[2085]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 16 19:43:12 goblin.suse.cz upowerd[2085]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6 kvě 16 19:43:12 goblin.suse.cz brltty[29116]: USB configuration set error 16: Zařízení nebo zdroj jsou používány. kvě 16 19:43:12 goblin.suse.cz brltty[29116]: USB interface in use: 0 (cp210x) kvě 16 19:43:12 goblin.suse.cz kernel: usb 1-1.6: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 kvě 16 19:43:12 goblin.suse.cz kernel: cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 kvě 16 19:43:12 goblin.suse.cz kernel: cp210x 1-1.6:1.0: device disconnected kvě 16 19:43:12 goblin.suse.cz systemd-udevd[29153]: Process 'gpsd.sh' failed with exit code 1. kvě 16 19:43:12 goblin.suse.cz ModemManager[1209]: <info> (tty/ttyUSB0): released by modem /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6 kvě 16 19:43:12 goblin.suse.cz ModemManager[1209]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6': Operation was cancelled kvě 16 19:43:12 goblin.suse.cz upowerd[2085]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 16 19:43:12 goblin.suse.cz upowerd[2085]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 16 19:43:12 goblin.suse.cz brltty[29116]: Ignored Byte: 00 kvě 16 19:43:13 goblin.suse.cz upowerd[2085]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 16 19:43:17 goblin.suse.cz upowerd[2085]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 16 19:43:19 goblin.suse.cz upowerd[2085]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 16 19:43:22 goblin.suse.cz upowerd[2085]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 16 19:43:24 goblin.suse.cz upowerd[2085]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 16 19:43:27 goblin.suse.cz upowerd[2085]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 16 19:43:29 goblin.suse.cz upowerd[2085]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 kvě 16 19:43:32 goblin.suse.cz upowerd[2085]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 And udevadm monitor shows: KERNEL[12574.759230] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6 (usb) KERNEL[12574.759964] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) KERNEL[12574.763005] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0 (usb-serial) KERNEL[12574.763878] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0/tty/ttyUSB0 (tty) KERNEL[12574.763921] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0 (usb-serial) KERNEL[12574.763959] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) KERNEL[12574.763990] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6 (usb) UDEV [12574.782739] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6 (usb) UDEV [12574.784559] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) UDEV [12574.785363] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0 (usb-serial) UDEV [12574.790623] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0/tty/ttyUSB0 (tty) UDEV [12574.791682] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0 (usb-serial) UDEV [12574.792608] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) UDEV [12574.793527] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6 (usb) KERNEL[12576.052423] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0/tty/ttyUSB0 (tty) KERNEL[12576.052461] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0 (usb-serial) KERNEL[12576.052481] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0 (usb-serial) KERNEL[12576.052509] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) KERNEL[12576.052549] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) UDEV [12576.056876] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0/tty/ttyUSB0 (tty) UDEV [12576.058033] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0 (usb-serial) UDEV [12576.059221] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/ttyUSB0 (usb-serial) UDEV [12576.060342] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) UDEV [12576.061785] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) KERNEL[12577.721086] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) UDEV [12577.724423] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) KERNEL[12581.053759] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) UDEV [12581.055593] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) KERNEL[12582.921818] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) UDEV [12582.925826] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) KERNEL[12586.057426] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) UDEV [12586.059705] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) KERNEL[12587.918781] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) UDEV [12587.922419] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0 (usb) -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

20 Dec 20 Dec

17:08

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c31 Günter Halt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guenter.halt@halt-hoenow.de Component|Basesystem |Basesystem Version|Current |Leap 15.0 Product|openSUSE Tumbleweed |openSUSE Distribution Target Milestone|--- |Leap 15.0 --- Comment #31 from Günter Halt --- no device /dev/ttyUSBx created for USB-RS232-Converter in Leap15 Part of lsusb report: Bus 010 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light It works in openSuSE Leap 42.3 fine However, if an second USB-RS232-Adaper is present, one of both is working! lsusb |grep CP2102 Bus 008 Device 003: ID 10c4:ea60 ... CP2102/CP2109 UART Bridge Controller Bus 003 Device 004: ID 10c4:ea60 ....CP2102/CP2109 UART Bridge Controller ... ls -l /dev/ttyUSB* crw-rw---- 1 root dialout 188, 1 20. Dez 17:40 /dev/ttyUSB1 # no device /dev/ttyUSB0 !!!! Remove an Adapter: lsusb |grep CP2102 Bus 008 Device 003: ID 10c4:ea60 ... CP2102/CP2109 UART Bridge Controller O.K. ls -l /dev/ttyUSB* -> ls: Zugriff auf '/dev/ttyUSB*' nicht möglich: Datei oder Verzeichnis nicht gefunden not O.K. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

21:21

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c32 --- Comment #32 from Stefan Brüns --- (In reply to Martin Wilck from comment #30)

(In reply to Stefan Brüns from comment #29)

...
(In reply to Martin Wilck from comment #28)

...
(In reply to Stefan Brüns from comment #27)

...
So I doubt one could catch everything with some BLACKLIST_foo option.

IMO it would work for everything that's proved by udev. User-space tools that try to access devices directly would need explicit support, which opens a can of worms.

Thats no differentiation: 1. The device is hot-/cold-plugged 2. The kernel loads a driver and generates a udev event 3. udev starts some kind of userspace "helper", e.g. gpsd, brltty 4a. the helper *may* detach the kernel driver and use e.g. libusb, or 4b. the helper opens e.g. the tty port

I was talking about processing "SUBSYSTEM==usb" events in step 3.

That's the stage at which to decide which upper level driver to use, no matter whether it's kernel or user-space. blacklisted helpers wouldn't even be tried. Selecting which modules to load, or which helpers to try, is very well possible at this stage, and can be implemented completely in udev rules. But I may be missing your point.

Udev sees e.g. a CP2102, with the corresponding USB VID/PID. Although device vendors could use their own VID/PID, too many don't. The CP2102 can be anything, a sole USB-TTY-converter, a braille device, a GPS mouse, a scope, a power supply.

The "can of worms" referred to cases where a helper is started by some other means (i.e. other than udev), and tries probing devices by itself. Sane tools will be looking at the udev properties already, yet some may need to be prevented from detaching competing drivers.

The available properties are in many cases not sufficient to even determine the device type. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10 Jan 10 Jan

22:28

New subject: [Bug 1093378] conflicting udev rules completely break USB Serial bridges

http://bugzilla.opensuse.org/show_bug.cgi?id=1093378 http://bugzilla.opensuse.org/show_bug.cgi?id=1093378#c33 --- Comment #33 from Martin Wilck --- I understand. But still I'm not sure what to do about it. The best thing might actually be not to configure any driver, but to show the device as "unkown device" or such, and offer the user a way to choose a driver. But I wouldn't do that in a RUN clause, as argued above. Rather, if the port the device is connected to is associated with a seat, it would make sense to let the user on that seat decide on the device type, create a temporary udev rule (or let the user decide whether he wants a temporary or persistent rule), and retrigger the "add" event, this time with the correct driver. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

1940

Age (days ago)

2180

Last active (days ago)

Download

20 comments

1 participants

tags

participants (1)

bugzilla_noreply＠novell.com