Problems with the operation of the USB hub

alexanderzhirov

Reinstalled the system from Solus Mate (old version) to Solus Budgie 4.5. There was a problem when working with the USB hub. Previously, there were no such problems. When connecting a USB device, the following messages appear in the log:

янв 28 19:01:35 solus kernel: usb 6-4.1: new SuperSpeed USB device number 3 using xhci_hcd
янв 28 19:01:35 solus kernel: usb 6-4.1: New USB device found, idVendor=0781, idProduct=5583, bcdDevice= 1.00
янв 28 19:01:35 solus kernel: usb 6-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
янв 28 19:01:35 solus kernel: usb 6-4.1: Product:  SanDisk 3.2Gen1
янв 28 19:01:35 solus kernel: usb 6-4.1: Manufacturer:  USB
янв 28 19:01:35 solus kernel: usb 6-4.1: SerialNumber: 040198cdcb23853a72d7183dbbb5fc8ebdf34e2b13075526dbb31f3122cc098eb9b50000000000000000000000f3e5d7ff9584188355810786ac7a15
янв 28 19:01:35 solus kernel: usb-storage 6-4.1:1.0: USB Mass Storage device detected
янв 28 19:01:35 solus kernel: scsi host4: usb-storage 6-4.1:1.0
янв 28 19:01:35 solus mtp-probe[2313]: checking bus 6, device 3: "/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb6/6-4/6-4.1"
янв 28 19:01:35 solus mtp-probe[2313]: bus: 6, device: 3 was not an MTP device
янв 28 19:01:35 solus mtp-probe[2314]: checking bus 6, device 3: "/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb6/6-4/6-4.1"
янв 28 19:01:35 solus mtp-probe[2314]: bus: 6, device: 3 was not an MTP device
янв 28 19:01:36 solus kernel: scsi 4:0:0:0: Direct-Access      USB      SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
янв 28 19:01:36 solus kernel: sd 4:0:0:0: [sdd] 120164352 512-byte logical blocks: (61.5 GB/57.3 GiB)
янв 28 19:01:36 solus kernel: sd 4:0:0:0: [sdd] Write Protect is off
янв 28 19:01:36 solus kernel: sd 4:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
янв 28 19:01:36 solus kernel:  sdd: sdd1
янв 28 19:01:36 solus kernel: sd 4:0:0:0: [sdd] Attached SCSI removable disk
янв 28 19:01:48 solus nemo[2319]: Current gtk theme is not known to have nemo support (Materia-compact) - checking...
янв 28 19:01:52 solus kernel: FAT-fs (sdd1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
янв 28 19:01:52 solus udisksd[641]: Mounted /dev/sdd1 at /run/media/alexader/D728-1A01 on behalf of uid 1000
янв 28 19:01:52 solus kernel: DMAR: DRHD: handling fault status reg 2
янв 28 19:01:52 solus kernel: DMAR: [DMA Read NO_PASID] Request device [03:00.0] fault addr 0xfff96000 [fault reason 0x06] PTE Read access is not set
янв 28 19:02:27 solus kernel: hub 6-4:1.0: hub_ext_port_status failed (err = -110)
янв 28 19:02:28 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:29 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:30 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:31 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:32 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:32 solus kernel: usb 6-4-port1: Cannot enable. Maybe the USB cable is bad?
янв 28 19:02:33 solus kernel: usb 6-4-port1: cannot disable (err = -110)
янв 28 19:02:38 solus kernel: hub 6-4:1.0: hub_ext_port_status failed (err = -110)
янв 28 19:02:39 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:41 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:42 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:43 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:44 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:44 solus kernel: usb 6-4-port1: Cannot enable. Maybe the USB cable is bad?
янв 28 19:02:45 solus kernel: usb 6-4-port1: cannot disable (err = -110)
янв 28 19:02:50 solus kernel: hub 6-4:1.0: hub_ext_port_status failed (err = -110)
янв 28 19:02:51 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:52 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:52 solus systemd-udevd[416]: sdd1: Worker [2353] processing SEQNUM=3835 is taking a long time
янв 28 19:02:53 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:54 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:55 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:02:55 solus kernel: usb 6-4-port1: Cannot enable. Maybe the USB cable is bad?
янв 28 19:02:56 solus kernel: usb 6-4-port1: cannot disable (err = -110)
янв 28 19:03:01 solus kernel: hub 6-4:1.0: hub_ext_port_status failed (err = -110)
янв 28 19:03:02 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:03:03 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:03:04 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:03:05 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:03:06 solus kernel: usb 6-4-port1: cannot reset (err = -110)
янв 28 19:03:06 solus kernel: usb 6-4-port1: Cannot enable. Maybe the USB cable is bad?
янв 28 19:03:07 solus kernel: usb 6-4-port1: cannot disable (err = -110)
янв 28 19:03:08 solus kernel: usb 6-4-port1: cannot disable (err = -110)
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=76s
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 09 08 00 00 f8 00
янв 28 19:03:08 solus kernel: I/O error, dev sdd, sector 2312 op 0x0:(READ) flags 0x80700 phys_seg 248 prio class 2
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 10 00 00 00 08 00
янв 28 19:03:08 solus kernel: I/O error, dev sdd, sector 4096 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 0a 08 00 00 26 00
янв 28 19:03:08 solus kernel: I/O error, dev sdd, sector 2568 op 0x0:(READ) flags 0x80700 phys_seg 38 prio class 2
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 10 00 00 00 08 00
янв 28 19:03:08 solus kernel: I/O error, dev sdd, sector 4096 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 2
янв 28 19:03:08 solus kernel: Buffer I/O error on dev sdd1, logical block 2048, async page read
янв 28 19:03:08 solus kernel: Buffer I/O error on dev sdd1, logical block 2049, async page read
янв 28 19:03:08 solus kernel: Buffer I/O error on dev sdd1, logical block 2050, async page read
янв 28 19:03:08 solus kernel: Buffer I/O error on dev sdd1, logical block 2051, async page read
янв 28 19:03:08 solus kernel: Buffer I/O error on dev sdd1, logical block 2052, async page read
янв 28 19:03:08 solus kernel: Buffer I/O error on dev sdd1, logical block 2053, async page read
янв 28 19:03:08 solus kernel: Buffer I/O error on dev sdd1, logical block 2054, async page read
янв 28 19:03:08 solus kernel: Buffer I/O error on dev sdd1, logical block 2055, async page read
янв 28 19:03:08 solus systemd[844]: Created slice User Background Tasks Slice.
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 09 08 00 00 01 00
янв 28 19:03:08 solus kernel: I/O error, dev sdd, sector 2312 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
янв 28 19:03:08 solus kernel: FAT-fs (sdd1): FAT read failed (blocknr 264)
янв 28 19:03:08 solus kernel: sdd: detected capacity change from 120164352 to 0
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: I/O error, dev sdd, sector 2312 op 0x0:(READ) flags 0x80700 phys_seg 248 prio class 2
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: I/O error, dev sdd, sector 2568 op 0x0:(READ) flags 0x80700 phys_seg 38 prio class 2
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: I/O error, dev sdd, sector 2312 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
янв 28 19:03:08 solus kernel: FAT-fs (sdd1): FAT read failed (blocknr 264)
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: I/O error, dev sdd, sector 2312 op 0x0:(READ) flags 0x80700 phys_seg 248 prio class 2
янв 28 19:03:08 solus systemd[844]: Starting Cleanup of User's Temporary Files and Directories...
янв 28 19:03:08 solus nemo.desktop[2319]: Couldn't get disk full info for: Произошла ошибка при получении сведений о файловой системе /run/media/alexader/D728-1A01: Ошибка ввода/вывода
янв 28 19:03:08 solus systemd[844]: Finished Cleanup of User's Temporary Files and Directories.
янв 28 19:03:08 solus nemo.desktop[2319]: Couldn't get disk full info for: Произошла ошибка при получении сведений о файловой системе /run/media/alexader/D728-1A01: Ошибка ввода/вывода
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: I/O error, dev sdd, sector 2568 op 0x0:(READ) flags 0x80700 phys_seg 38 prio class 2
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: FAT-fs (sdd1): FAT read failed (blocknr 264)
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: FAT-fs (sdd1): FAT read failed (blocknr 1708)
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus nemo.desktop[2319]: Couldn't get disk full info for: Произошла ошибка при получении сведений о файловой системе /run/media/alexader/D728-1A01: Ошибка ввода/вывода
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: FAT-fs (sdd1): FAT read failed (blocknr 264)
янв 28 19:03:08 solus udisksd[641]: Partitions found on device '/dev/sdd' but couldn't read partition table signature: Failed to assign the new context to disk '/dev/sdd': No medium found
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: FAT-fs (sdd1): FAT read failed (blocknr 264)
янв 28 19:03:08 solus udisksd[641]: Cleaning up mount point /run/media/alexader/D728-1A01 (device 8:49 no longer exists)
янв 28 19:03:08 solus kernel: sd 4:0:0:0: [sdd] tag#0 access beyond end of device
янв 28 19:03:08 solus kernel: Buffer I/O error on dev sdd1, logical block 0, lost sync page write
янв 28 19:03:08 solus systemd[1]: run-media-alexader-D728\x2d1A01.mount: Deactivated successfully.
янв 28 19:03:13 solus kernel: hub 6-4:1.0: hub_ext_port_status failed (err = -110)

alexanderzhirov

The USB hub is connected to the ORICO-PVU3-4P device

alexanderzhirov

Booted from Live (Linux solus 6.6.9-269.current) - USB hub is working:

Jan 28 22:29:13 solus kernel: usb 6-4.2: new SuperSpeed USB device number 3 using xhci_hcd
Jan 28 22:29:13 solus kernel: usb 6-4.2: New USB device found, idVendor=0781, idProduct=5583, bcdDevice= 1.00
Jan 28 22:29:13 solus kernel: usb 6-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 28 22:29:13 solus kernel: usb 6-4.2: Product:  SanDisk 3.2Gen1
Jan 28 22:29:13 solus kernel: usb 6-4.2: Manufacturer:  USB
Jan 28 22:29:13 solus kernel: usb 6-4.2: SerialNumber: 040198cdcb23853a72d7183dbbb5fc8ebdf34e2b13075526dbb31f3122cc098eb9b50000000000000000000000f3e5d7ff9584188355810786ac7a15
Jan 28 22:29:13 solus kernel: usb-storage 6-4.2:1.0: USB Mass Storage device detected
Jan 28 22:29:13 solus kernel: scsi host5: usb-storage 6-4.2:1.0
Jan 28 22:29:13 solus mtp-probe[1660]: checking bus 6, device 3: "/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb6/6-4/6-4.2"
Jan 28 22:29:13 solus mtp-probe[1660]: bus: 6, device: 3 was not an MTP device
Jan 28 22:29:13 solus mtp-probe[1661]: checking bus 6, device 3: "/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb6/6-4/6-4.2"
Jan 28 22:29:13 solus mtp-probe[1661]: bus: 6, device: 3 was not an MTP device
Jan 28 22:29:14 solus kernel: scsi 5:0:0:0: Direct-Access      USB      SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
Jan 28 22:29:14 solus kernel: sd 5:0:0:0: [sde] 120164352 512-byte logical blocks: (61.5 GB/57.3 GiB)
Jan 28 22:29:14 solus kernel: sd 5:0:0:0: [sde] Write Protect is off
Jan 28 22:29:14 solus kernel: sd 5:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jan 28 22:29:14 solus kernel:  sde: sde1
Jan 28 22:29:14 solus kernel: sd 5:0:0:0: [sde] Attached SCSI removable disk
Jan 28 22:29:27 solus kernel: FAT-fs (sde1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Jan 28 22:29:27 solus kernel: FAT-fs (sde1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jan 28 22:29:27 solus udisksd[825]: Mounted /dev/sde1 at /run/media/live/D728-1A01 on behalf of uid 1000
Jan 28 22:29:56 solus systemd[1]: run-media-live-D728\x2d1A01.mount: Deactivated successfully.
Jan 28 22:29:56 solus udisksd[825]: Cleaning up mount point /run/media/live/D728-1A01 (device 8:65 is not mounted)
Jan 28 22:29:56 solus udisksd[825]: Unmounted /dev/sde1 on behalf of uid 1000

Something is broken in the latest version of the updated kernel 6.6.12-271.current

P.S. USB 3.0 is also falling off on the front panel PC

TraceyC

alexanderzhirov

If you're seeing this with the latest kernel (6.6.12-271.current), please open an issue on our bug tracker for this. By opening an issue, it will allow our developers to look into the problem and keep track of progress. Thanks.

Also, what do you mean by "USB 3.0 is also falling off on the front panel PC" ?

alexanderzhirov

TraceyC Yes, the issues has already been created. About the fact that USB 3.0 (the connector on the front panel) stops working after kernel errors. Most likely, the problem extends to all ports that the kernel affects.

TraceyC

Thanks for opening the issue. I see ermo was able to reproduce it. We'll dig into it!