[Bug 215649] New: all usb devices stop working and forced to reboot the system

* [Bug 215649] New: all usb devices stop working and forced to reboot the system
@ 2022-03-01 15:08 bugzilla-daemon
  2022-03-01 15:18 ` [Bug 215649] " bugzilla-daemon
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: bugzilla-daemon @ 2022-03-01 15:08 UTC (permalink / raw)
  To: linux-usb

https://bugzilla.kernel.org/show_bug.cgi?id=215649

            Bug ID: 215649
           Summary: all usb devices stop working and forced to reboot the
                    system
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.16.11
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: ricciare@libero.it
        Regression: No

Created attachment 300513
  --> https://bugzilla.kernel.org/attachment.cgi?id=300513&action=edit
this is the huge kernel configuration used by slackware64-current

Hi, I use slackware64-current and using the kernel 5.16.11-huge, included in
the distro. When I try to plug and mount 2 usb pendrives suddenly all usb
devices stop working (keyboard and mouse are the main ones for further pc usage
nomore working). The unique option is to turn off/on the power cable, or do a
reset. When rebooted this problem is going to happen again when repeatign the
same operation, also using other usb pendrives (kingston 32GB usb3.0).

I tried using different usb mouses (Logitech M330 Silent and Logitech M705), I
have a Logitech G213 keyboard and I was connecting a 64GB Toshiba usb3.0
pendrive and a Lexar 16GB usb3.0 pendrive. Sometimes it disconnect and than
reconnects the mouse, it happens testing both of them, and when moving
documents from/to usb3 external devices the system partially locks, and all
that are situations I not experienced with my previous computers. I've 2
desktop pc: first one has Ryzen9 3900X , Gygabyte Aorus Lite x570 motherboard ,
32GB Crucial ddr4 , Samsung 870 Pro nvme 1TB , WD Black 500GB nvme ; the second
one I'm using for tests, has Ryzen7 3800X , Gygabyte Aorus Lite b450
motherboard , 16GB Crucial ddr4 , Samsung 870 Evo nvme 1TB. Both pc using
slackware64-current, both have the described usb problem. I tried using my sis
pc and the problem happened again (her one has an AMD A4-6300 cpu , MSI A78-G41
motherboard, 16GB ddr3 Kingston ram, dual booting (windows10 and MXLinux).

At the end of this message I paste the end of dmesg command, showing the
unexpected stop of all usb devices. Attached you can find the complete dmesg
output named "errore_usb.txt" and I attach you the configuration kernel file
used to compile the slackware huge kernel. If need further infos I'm at your
disposal, ask me. Nicola

Mar 1 12:33:05 casa kernel: usb 6-2: new SuperSpeed USB device number 3 using
xhci_hcd
Mar 1 12:33:05 casa kernel: usb 6-2: New USB device found, idVendor=0930,
idProduct=6545, bcdDevice= 1.10
Mar 1 12:33:05 casa kernel: usb 6-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
Mar 1 12:33:05 casa kernel: usb 6-2: Product: TransMemory
Mar 1 12:33:05 casa kernel: usb 6-2: Manufacturer: TOSHIBA
Mar 1 12:33:05 casa kernel: usb 6-2: SerialNumber: C03FD5F76D5BE2C140005C54
Mar 1 12:33:05 casa kernel: usb-storage 6-2:1.0: USB Mass Storage device
detected
Mar 1 12:33:05 casa kernel: scsi host9: usb-storage 6-2:1.0
Mar 1 12:33:06 casa kernel: scsi 9:0:0:0: Direct-Access TOSHIBA TransMemory
PMAP PQ: 0 ANSI: 6
Mar 1 12:33:06 casa kernel: sd 9:0:0:0: [sde] 121995264 512-byte logical
blocks: (62.5 GB/58.2 GiB)
Mar 1 12:33:06 casa kernel: sd 9:0:0:0: [sde] Write Protect is off
Mar 1 12:33:06 casa kernel: sd 9:0:0:0: [sde] Write cache: disabled, read
cache: enabled, doesn't support DPO or FUA
Mar 1 12:33:08 casa kernel: sde: sde1
Mar 1 12:33:08 casa kernel: sd 9:0:0:0: [sde] Attached SCSI removable disk
Mar 1 12:33:12 casa kernel: usb 2-4: reset SuperSpeed USB device number 3 using
xhci_hcd
Mar 1 12:33:13 casa kernel: usb 2-3: New USB device found, idVendor=21c4,
idProduct=a838, bcdDevice=11.00
Mar 1 12:33:13 casa kernel: usb 2-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
Mar 1 12:33:23 casa kernel: usb 2-3: USB disconnect, device number 4
Mar 1 12:33:23 casa kernel: usb 1-6: USB disconnect, device number 2
Mar 1 12:33:23 casa kernel: usb 2-4: USB disconnect, device number 3
Mar 1 12:33:23 casa kernel: usb 1-7: USB disconnect, device number 3
Mar 1 12:33:23 casa kernel: obex-check-devi[1882]: segfault at 0 ip
00007fc63189dd3c sp 00007ffd47999c30 error 4 in
libc-2.35.so[7fc631880000+186000]
Mar 1 12:33:23 casa kernel: Code: 53 48 83 ec 28 49 8b 40 08 48 89 74 24 08 89
d6 85 c9 0f 85 96 02 00 00 83 fe 01 0f 84 85 01 00 00 83 fe 24 0f 87 7c 01 00
00 <49> 0f be 45 00 49 8b 50 68 4c 89 eb 49 89 c7 f6 44 42 01 20 74 19
Mar 1 12:33:23 casa mtp-probe: checking bus 6, device 3:
"/sys/devices/pci0000:00/0000:00:08.1/0000:0d:00.3/usb6/6-2"
Mar 1 12:33:23 casa mtp-probe: bus: 6, device: 3 was not an MTP device
Mar 1 12:33:24 casa mtp-probe: checking bus 6, device 3:
"/sys/devices/pci0000:00/0000:00:08.1/0000:0d:00.3/usb6/6-2"
Mar 1 12:33:24 casa mtp-probe: bus: 6, device: 3 was not an MTP device
Mar 1 12:33:49 casa kernel: usb 6-2: USB disconnect, device number 3
Mar 1 12:35:25 casa syslogd[1011]: syslogd v2.3.0: restart.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 6+ messages in thread