USB 2.0 ports doesn´t works after suspend mode

Linux Mint
19

@01101111,
you’re right. I have some errors related to the USB port after suspending

Before suspending:
dmesg --level=err
[ 2.769543] Couldn’t get size: 0x800000000000000e
[ 2.769552] MODSIGN: Couldn’t get UEFI db list
[ 2.769622] Couldn’t get size: 0x800000000000000e

After suspending:
dmesg --level=err
[ 2.769543] Couldn’t get size: 0x800000000000000e
[ 2.769552] MODSIGN: Couldn’t get UEFI db list
[ 2.769622] Couldn’t get size: 0x800000000000000e
[ 836.062810] ohci-pci 0000:00:12.0: frame counter not updating; disabled
[ 836.062813] ohci-pci 0000:00:12.0: HC died; cleaning up
[ 840.894748] dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -22
[ 840.894767] PM: Device 3-1 failed to resume async: error -22

Here’s my conclusion from my latest tests:
The bus used for the mouse uses the driver ohci-pci and I think this driver is related to USB 1.1
but when I use a USB Pen in the same USB physical port, the bus used is a different one and uses the driver echi-pci:

  • Bus used for the mouse:
    /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/4p, 12M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M

  • Bus used for the USB Pen:
    /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M
    |__ Port 1: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M

When I did the first tests to unbind and bind the USB port I used these commands so restart the drivers:
echo ‘3-1’ > /sys/bus/usb/drivers/usb/unbind
echo ‘3-1’ > /sys/bus/usb/drivers/usb/bind

Today, after seeing the error message with dmesg, I tried reseting the controller after suspending the laptop with the commands below and I’ve realized that the mouse started working again:
echo ‘0000:00:12.0’ > /sys/bus/pci/drivers/ohci-pci/unbind
echo ‘0000:00:12.0’ > /sys/bus/pci/drivers/ohci-pci/bind

I’m still trying to figure out more about this matter but so far I only found two possible causes for the controller error:

  • Could be hardware fault;
  • Could be kernel bug.

Now, I guess I’ve reached my limit and I don’t know what more I can do to try to solve this problem before reporting it as a kernel bug

I haven’t given up yet, does anyone have any ideas?

I’d like to thank all of you for your support, reply’s and input on this matter, because it allowed me to learn more about linux to troubleshoot this problem

2 Likes