Could the problem with the USB port possibly cause a problem with an
attempt to reboot the system ?
On 19 Aug 2020 11:30, "Mick Ab" <recoverymail123...@gmail.com> wrote:

> There have been problems recently in trying to use the USB 3 port on a
> desktop running Debian.
>
> The kernel doesn't recognise either a new portable hard drive or a new
> flash drive when each have, in turn, be plugged into that port. Neither
> device shows up with fdisk  -l, lsusb or lsblk commands.
>
> Now the following has been done :-
>
> (1) The new flash drive was unplugged from the port
>
> (2) As root, the following command was run :
>
> dmesg  |  tail
>
> The output was as follows :
>
> [3974120.938338] usb 1-1: new high-speed USB device number 66 using
> xhci_hcd
> [3974126.430777] usb 1-1: new high-speed USB device number 67 using
> xhci_hcd
> [3974131.923271] usb 1-1: new high-speed USB device number 68 using
> xhci_hcd
> [3974137.415713] usb 1-1: new high-speed USB device number 69 using
> xhci_hcd
> [3974142.908184] usb 1-1: new high-speed USB device number 70 using
> xhci_hcd
>
> The above sequence continued up to device number 75
>
> (3) The flash drive was plugged back into the USB 3 port
>
> (4) After a few seconds the following command was run as root :
>
> dmesg  |  tail  -50
>
> The output was as follows :
>
> [3973945.175272] usb 1-1: new high-speed USB device number 34 using
> xhci_hcd
> [3973950.667736] usb 1-1: new high-speed USB device number 35 using
> xhci_hcd
> [3973956.164234] usb 1-1: new high-speed USB device number 36 using
> xhci_hcd
> [3973961.660705] usb 1-1: new high-speed USB device number 37 using
> xhci_hcd
> [3973967.153175] usb 1-1: new high-speed USB device number 38 using
> xhci_hcd
> [3973972.645644] usb 1-1: new high-speed USB device number 39 using
> xhci_hcd
> [3973978.138108] usb 1-1: new high-speed USB device number 40 using
> xhci_hcd
>
> The above sequence continued until device number 83
>
> Clearly something is wrong with the port. Can anyone say what is causing
> the problem and how it can be fixed.  Thank you.
>

Reply via email to