How to prevent USB ports being renamed during operation?

Hi

We have a number of serial devices connected via FTDI USB to serial cables to a PC. When Linux boots up it assigns them a name like ttyUSB1 etc. The name varies each time the computer boots. The problem occurs when the ports are renamed after the computer has booted and our daemon is running. When the port name is changed while the daemon is running the attached device appears to be not working because the port has been renamed. For example we have a serial keyboard that Linux assigned to ttyUSB3 at boot up. Later for unknown reason that same device is assigned to ttyUSB5. The computer was not rebooted. The cable was not detached and then attached again. The daemon has been running the whole time. So what would cause the port to get renamed and how do I stop this from happening?

Thanks,
Simon

I see you already guessed in that direction. To me it looks something like that. Loss of connection for a short while after which it is re-detected by the Kernel.

Maybe you could use fixed device names by writing your own udev rules (which then identify the device without doubt and give it a name of your liking). I took a short look into /usr/lib/udev/rules.d/60-serial.rules, but this is clearly outside my competence.

ILL mobo turns off USB ports due to power saving settings.
Turn off this feature in BIOS.

Hi

Yes we have already done that but the issue persists so as suggested we have created some udev rules which appear to be working.

What about this file: /usr/lib/udev/rules.d/77-mm-usb-serial-adapters-greylist.rules ?

The following is the content of /etc/udev/rules.d/99-usb-serial.rules. As you can see the last two items relate to a mag reader and special keyboard. According to these rules the the mag reader should be ttyUSB3 and the keyboard ttyUSB4 but this morning the site called and said the keyboard and mag reader stopped working. When I checked the mag reader was ttyUSB5 and the keyboard ttyUSB6. So how can this be happening? Is there something wrong with how I configured the rules? Does the file have to have a particular name?


SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="kt_lcd_mo_4x40", SYMLINK+="ttyUSB0"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="kt_pmp_mnet_stat2", ATTRS{serial}=="FT640VEE", SYMLINK+="ttyUSB1"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="kt_pmp_mnet_stat2", ATTRS{serial}=="FT5PWZOO", SYMLINK+="ttyUSB2"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="kt_magr_idtech_sp", SYMLINK+="ttyUSB3"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="kt_keyb_stern_4x11", SYMLINK+="ttyUSB4"

Here is the content of the /usr/lib/udev/rules.d/77-mm-usb-serial-adapters-greylist.rules What is its function?


# do not edit this file, it will be overwritten on update


ACTION!="add|change|move", GOTO="mm_usb_serial_adapters_greylist_end"
SUBSYSTEM!="usb", GOTO="mm_usb_serial_adapters_greylist_end"
ENV{DEVTYPE}!="usb_device",  GOTO="mm_usb_serial_adapters_greylist_end"


# Belkin F5U183 Serial Adapter
ATTRS{idVendor}=="050d", ATTRS{idProduct}=="0103", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"


# FTDI-based serial adapters
#   FTDI does USB to serial converter ICs; and it's very likely that they'll
#   never do modems themselves, so it should be safe to add a rule only based
#   on the vendor Id.
ATTRS{idVendor}=="0403", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"


# Devices using Microchip's VID
ATTRS{idVendor}=="04d8", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"


# ATEN Intl UC-232A (Prolific)
ATTRS{idVendor}=="0557", ATTRS{idProduct}=="2008", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"


# Prolific USB to Serial adapter
ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"


# Magic Control Technology Corp adapters
ATTRS{idVendor}=="0711", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"


# Cygnal Integrated Products, Inc. CP210x
ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"
ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea71", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"


# QinHeng Electronics HL-340
ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"


# Atmel Corp. LUFA USB to Serial Adapter Project (Arduino)
ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="204b", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"


# Netchip Technology, Inc. Linux-USB Serial Gadget (CDC ACM mode)
ATTRS{idVendor}=="0525", ATTRS{idProduct}=="a4a7", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"


# Cypress Serial-USB devices
ATTRS{idVendor}=="04B4", ATTRS{idProduct}=="0002", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"
ATTRS{idVendor}=="04B4", ATTRS{idProduct}=="0003", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"
ATTRS{idVendor}=="04B4", ATTRS{idProduct}=="0004", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"
ATTRS{idVendor}=="04B4", ATTRS{idProduct}=="0005", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"
ATTRS{idVendor}=="04B4", ATTRS{idProduct}=="0006", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"
ATTRS{idVendor}=="04B4", ATTRS{idProduct}=="0007", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"
ATTRS{idVendor}=="04B4", ATTRS{idProduct}=="0009", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"
ATTRS{idVendor}=="04B4", ATTRS{idProduct}=="000A", ENV{ID_MM_DEVICE_MANUAL_SCAN_ONLY}="1"


LABEL="mm_usb_serial_adapters_greylist_end"



Show what is going on:

**erlangen:~ #** journalctl --since 14:25 _KERNEL_SUBSYSTEM=usb 
-- Journal begins at Mon 2021-11-22 23:45:25 CET, ends at Tue 2021-11-30 14:26:03 CET. -- 
Nov 30 14:25:21 erlangen kernel: usb 1-10: new full-speed USB device number 4 using xhci_hcd 
Nov 30 14:25:21 erlangen kernel: **usb 1-10: Device not responding to setup address.**
Nov 30 14:25:21 erlangen kernel: **usb 1-10: Device not responding to setup address.**
Nov 30 14:25:22 erlangen kernel: **usb 1-10: device not accepting address 4, error -71**
Nov 30 14:25:34 erlangen kernel: usb 1-10: new full-speed USB device number 6 using xhci_hcd 
Nov 30 14:25:34 erlangen kernel: usb 1-10: New USB device found, idVendor=091e, idProduct=28ca, bcdDevice= 5.09 
Nov 30 14:25:34 erlangen kernel: usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=5 
Nov 30 14:25:34 erlangen kernel: usb 1-10: SerialNumber: 0000eae6763f 
Nov 30 14:25:34 erlangen kernel: usb-storage 1-10:1.0: USB Mass Storage device detected 
**erlangen:~ #**

Hi

First off my colleague discovered that I had made a mistake in ATTRS{idProduct} which should read ATTRS{Product}. So I will correct that mistake and see if the problem is fixed.

Simon

Here is the journal. I see that a disconnect happened at 3:51 but the PC runs continuously, has a UPC and is housed in a locked cabinet so I am not sure how a disconnect occurred.


remote@BowmanvilleBulkOutbound:~> sudo journalctl --since 00:00 _KERNEL_SUBSYSTEM=usb
-- Logs begin at Mon 2021-11-29 10:54:44 EST, end at Tue 2021-11-30 12:13:20 EST. --
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: usb 1-8: USB disconnect, device number 5
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: usb 1-8.2: USB disconnect, device number 6
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: USB disconnect, device number 7
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: ftdi_sio 1-8.2.1:1.0: device disconnected
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: USB disconnect, device number 8
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: ftdi_sio 1-8.2.3:1.0: device disconnected
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8: new high-speed USB device number 9 using xhci_hcd
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8: New USB device found, idVendor=0424, idProduct=2514
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: hub 1-8:1.0: USB hub found
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: hub 1-8:1.0: 4 ports detected
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8.2: new high-speed USB device number 10 using xhci_hcd
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8.2: New USB device found, idVendor=0424, idProduct=2514
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: hub 1-8.2:1.0: USB hub found
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: hub 1-8.2:1.0: 4 ports detected
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: new full-speed USB device number 11 using xhci_hcd
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: New USB device found, idVendor=0403, idProduct=6015
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: Product: kt_magr_idtech_sp
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: Manufacturer: FTDI
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: SerialNumber: FT5KV04L
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: ftdi_sio 1-8.2.1:1.0: FTDI USB Serial Device converter detected
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: Detected FT-X
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: FTDI USB Serial Device converter now attached to ttyUSB5
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: new full-speed USB device number 12 using xhci_hcd
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: New USB device found, idVendor=0403, idProduct=6001
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: Product: kt_keyb_stern_4x11
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: Manufacturer: FTDI
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: SerialNumber: FT6GXB8R
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: ftdi_sio 1-8.2.3:1.0: FTDI USB Serial Device converter detected
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: Detected FT232RL
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: FTDI USB Serial Device converter now attached to ttyUSB6



No other messages around 03:51:47? Devices reconnect readily. Disconnect could be caused by a hardware glitch.

I reported the entire contents of journal query. So these were the only entries from midnight on. Is there some further commands I need to use to find anything around 03:51?

Simon

I have no idea what your journal contents and size are.
Show full output of “journalctl -b 0 _KERNEL_SUBSYSTEM=usb”.
Show anything immediately before 03:51:47: "journalctl --since 03:41:47 --until 03:51:47. Interval depends on what is going on. If unsure post full boot to susepaste using “journalctl -b”.


> journalctl -b 0 _KERNEL_SUBSYSTEM=usb
-- Logs begin at Mon 2021-11-29 10:54:44 EST, end at Tue 2021-11-30 19:40:39 EST. --
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb usb1: Product: xHCI Host Controller
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb usb1: Manufacturer: Linux 4.12.14-lp151.28.48-default xhci-hcd
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb usb1: SerialNumber: 0000:00:15.0
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: hub 1-0:1.0: USB hub found
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: hub 1-0:1.0: 8 ports detected
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb usb2: Product: xHCI Host Controller
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb usb2: Manufacturer: Linux 4.12.14-lp151.28.48-default xhci-hcd
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb usb2: SerialNumber: 0000:00:15.0
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: hub 2-0:1.0: USB hub found
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: hub 2-0:1.0: 7 ports detected
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-3: new full-speed USB device number 2 using xhci_hcd
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-3: New USB device found, idVendor=0403, idProduct=6015
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-3: Product: kt_lcd_mo_4x40
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-3: Manufacturer: FTDI
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-3: SerialNumber: FT5QGDYH
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-5: new full-speed USB device number 3 using xhci_hcd
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-5: New USB device found, idVendor=0403, idProduct=6001
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-5: Product: kt_pmp_mnet_stat2
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-5: Manufacturer: UTEK
Nov 29 10:54:45 BowmanvilleBulkInbound kernel: usb 1-5: SerialNumber: FT640VEE
Nov 29 10:54:46 BowmanvilleBulkInbound kernel: usb 1-6: new full-speed USB device number 4 using xhci_hcd
Nov 29 10:54:46 BowmanvilleBulkInbound kernel: usb 1-6: New USB device found, idVendor=0403, idProduct=6001
Nov 29 10:54:46 BowmanvilleBulkInbound kernel: usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 29 10:54:46 BowmanvilleBulkInbound kernel: usb 1-6: Product: kt_pmp_mnet_stat2
Nov 29 10:54:46 BowmanvilleBulkInbound kernel: usb 1-6: Manufacturer: UTEK
Nov 29 10:54:46 BowmanvilleBulkInbound kernel: usb 1-6: SerialNumber: FT5PWZOO
Nov 29 10:54:46 BowmanvilleBulkInbound kernel: usb 1-8: new high-speed USB device number 5 using xhci_hcd
Nov 29 10:54:46 BowmanvilleBulkInbound kernel: usb 1-8: New USB device found, idVendor=0424, idProduct=2514
Nov 29 10:54:46 BowmanvilleBulkInbound kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 29 10:54:46 BowmanvilleBulkInbound kernel: hub 1-8:1.0: USB hub found
Nov 29 10:54:46 BowmanvilleBulkInbound kernel: hub 1-8:1.0: 4 ports detected
Nov 29 10:54:46 BowmanvilleBulkOutbound kernel: usb 1-8.2: new high-speed USB device number 6 using xhci_hcd
Nov 29 10:54:46 BowmanvilleBulkOutbound kernel: usb 1-8.2: New USB device found, idVendor=0424, idProduct=2514
Nov 29 10:54:46 BowmanvilleBulkOutbound kernel: usb 1-8.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 29 10:54:46 BowmanvilleBulkOutbound kernel: hub 1-8.2:1.0: USB hub found
Nov 29 10:54:46 BowmanvilleBulkOutbound kernel: hub 1-8.2:1.0: 4 ports detected
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: new full-speed USB device number 7 using xhci_hcd
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: New USB device found, idVendor=0403, idProduct=6015
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: Product: kt_magr_idtech_sp
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: Manufacturer: FTDI
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: SerialNumber: FT5KV04L
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: new full-speed USB device number 8 using xhci_hcd
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: ftdi_sio 1-3:1.0: FTDI USB Serial Device converter detected
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-3: Detected FT-X
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-3: FTDI USB Serial Device converter now attached to ttyUSB0
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: ftdi_sio 1-5:1.0: FTDI USB Serial Device converter detected
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-5: Detected FT232BM
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-5: FTDI USB Serial Device converter now attached to ttyUSB1
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: ftdi_sio 1-6:1.0: FTDI USB Serial Device converter detected
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-6: Detected FT232BM
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-6: FTDI USB Serial Device converter now attached to ttyUSB2
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: ftdi_sio 1-8.2.1:1.0: FTDI USB Serial Device converter detected
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: Detected FT-X
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: FTDI USB Serial Device converter now attached to ttyUSB3
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: New USB device found, idVendor=0403, idProduct=6001
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: Product: kt_keyb_stern_4x11
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: Manufacturer: FTDI
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: SerialNumber: FT6GXB8R
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: ftdi_sio 1-8.2.3:1.0: FTDI USB Serial Device converter detected
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: Detected FT232RL
Nov 29 10:54:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: FTDI USB Serial Device converter now attached to ttyUSB4
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: usb 1-8: USB disconnect, device number 5
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: usb 1-8.2: USB disconnect, device number 6
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: USB disconnect, device number 7
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: ftdi_sio 1-8.2.1:1.0: device disconnected
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: USB disconnect, device number 8
Nov 30 03:51:47 BowmanvilleBulkOutbound kernel: ftdi_sio 1-8.2.3:1.0: device disconnected
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8: new high-speed USB device number 9 using xhci_hcd
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8: New USB device found, idVendor=0424, idProduct=2514
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: hub 1-8:1.0: USB hub found
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: hub 1-8:1.0: 4 ports detected
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8.2: new high-speed USB device number 10 using xhci_hcd
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8.2: New USB device found, idVendor=0424, idProduct=2514
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: hub 1-8.2:1.0: USB hub found
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: hub 1-8.2:1.0: 4 ports detected
Nov 30 03:51:48 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: new full-speed USB device number 11 using xhci_hcd
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: New USB device found, idVendor=0403, idProduct=6015
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: Product: kt_magr_idtech_sp
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: Manufacturer: FTDI
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: SerialNumber: FT5KV04L
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: ftdi_sio 1-8.2.1:1.0: FTDI USB Serial Device converter detected
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: Detected FT-X
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.1: FTDI USB Serial Device converter now attached to ttyUSB5
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: new full-speed USB device number 12 using xhci_hcd
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: New USB device found, idVendor=0403, idProduct=6001
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: Product: kt_keyb_stern_4x11
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: Manufacturer: FTDI
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: SerialNumber: FT6GXB8R
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: ftdi_sio 1-8.2.3:1.0: FTDI USB Serial Device converter detected
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: Detected FT232RL
Nov 30 03:51:49 BowmanvilleBulkOutbound kernel: usb 1-8.2.3: FTDI USB Serial Device converter now attached to ttyUSB6


root@BowmanvilleBulkOutbound:/home/remote> 






Here is the link to the full journalctl -b
https://susepaste.org/28464214

Simon

Use UPS, monitor voltage, check chip temperature, use another device, etc. …

Hi

We already use a UPS and we are having an electrician go over the entire site looking for issues such as a floating ground etc. We have a technician going to replace the PC and USB cables. We will see if this fixes the issue.

You’re using Leap 15.2 with kernel from Leap 15.1. For what? :question:
Make clean install with Leap 15.3, update it, and test again.

Hi

I have no idea how it got a different kernel. However, we did put a new PC with 15.3 at the site. So we will see if the problem disappears.

Hi

I have been using Leap 15.3 with new PCs for some time now and this issues occurs less frequently but it does still occur. It happened twice in that last 2 weeks. The udev rules do not prevent the device from being renamed.

As 15.3 is now out of support, you can not await any changes here anymore.

Also, this is a very old thread which not many people will check anymore.

Better start a new thread to draw fresh attention. And of course, better upgrade to 15.4 for a lot of reasons, including the chance that your problem is gone.