"device not accepting address" and "couldn't allocate usb_device" during shutdown

[Freeze]

Hi guys,

I have a problem with my cardreader during shutdown
It seems, something tries to set a new address though the device is already shut down.
And unfortunately this leads to unnecessary timeouts which slows down the shutdown process.

Futhermore there is a long pause after "systemd-journald: Received SIGTEM from PID 1 (systemd-shutdown)" and also directly before the really shut off.

[  2045.691439] usb 4-3: device not accepting address 2, error -108
[  2046.311436] usb 4-3: device not accepting address 2, error -108
[  2046.931439] usb 4-3: device not accepting address 2, error -108
[  2047.551437] usb 4-3: device not accepting address 2, error -108
[  2047.569727] usb 4-3: USB disconnect, device number 2
[  2047.755706] usb usb4-port3: couldn't allocate usb_device
[  2054.180555] ACPI: Preparing to enter system sleep state S5

It's a Chieftec CRD-901H.
Do you have any idea how I could debug this problem?

lsusb -t

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
    |__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M

usb-devices

T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=10000 MxCh= 4
D:  Ver= 3.10 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev=05.10
S:  Manufacturer=Linux 5.10.0-10-amd64 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:2a:00.3
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=04 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#=  2 Spd=5000 MxCh= 0
D:  Ver= 3.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs=  1
P:  Vendor=05e3 ProdID=0748 Rev=12.03
S:  Manufacturer=Generic
S:  Product=USB Storage
S:  SerialNumber=000000001203
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=896mA
I:  If#=0x0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

T:  Bus=04 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#=  3 Spd=5000 MxCh= 4
D:  Ver= 3.20 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=05e3 ProdID=0620 Rev=93.91
S:  Manufacturer=GenesysLogic
S:  Product=USB3.2 Hub
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

I have no clue where these interruptions are coming from.

Maybe you can help me

Thank you very much in advance!

 

[KGIII]

What happens if you run:

sudo rmmod ehci_hcd && sudo reboot

(Which will, obviously, also reboot the system.)

 

[Freeze]

Thank you very much for the proposal.

I also had to disable ehci_pci since this module was using ehci_hcd.
But the shutdown behavior didn't change.

Then I tried the same with xhci_hcd: Now the messages concerning the USB addressing are gone and the shutdown was much faster, though there is still a long time after the "Received SIGTERM" message:

 

[KGIII]

though there is still a long time after the "Received SIGTERM" message:

Hopefully someone else has an idea or two. That was all I could think of.

 

[Freeze]

Hopefully someone else has an idea or two. That was all I could think of.

Yes, hopefully.
But I think, your suggestion is no solution to my problem, yet, right?

 

[KGIII]

From your reply, it looks like it helped with part of your issue but you're still having other related issues.

Is that a correct assessment?

 

[Freeze]

From your reply, it looks like it helped with part of your issue but you're still having other related issues.

Is that a correct assessment?

Uhm, disabling the kernel module means, that the USB devices are not working anymore. So I think this is no real solution?

 

[KGIII]

Ah, yeah, it's supposed to still work after that. There's a speed incompatibility issue that I'm not sure how to fix. I'd hoped the previous command would do so - while still keeping your USB functional, of course.

 

[Freeze]

Ah, yeah, it's supposed to still work after that. There's a speed incompatibility issue that I'm not sure how to fix. I'd hoped the previous command would do so - while still keeping your USB functional, of course.

Ah, okay. I just assumed it won't function any more. I will give it a second try, thank you.

 

[KGIII]

Yeah, it should still work - it should just be at the proper speed at that point - as is my understanding. If not, I'm pretty well baffled. From what you wrote, it seemed like it added/exacerbated another problem. So, we don't really want that.

 

[Freeze]

Yeah, it should still work - it should just be at the proper speed at that point - as is my understanding. If not, I'm pretty well baffled. From what you wrote, it seemed like it added/exacerbated another problem. So, we don't really want that.

So, I tried it.

$ sudo rmmod xhci_hcd
rmmod: ERROR: Module xhci_hcd is in use by: xhci_pci
$ sudo rmmod xhci_pci

After disabling xhci_pci, none of the USB devices is working anymore.

Don't unterstand me wrong: The additional interruptions during shutdown were not caused by disabling xhci_pci and xhci_hcd.
These are independent of this USB topic.
You already see them in the OP.

 

[KGIII]

I can't think of what else I'd look for with that error message. Nobody else seems to have any idea either, or they'd have chimed in.

 

[Freeze]

I did some more research. My assumption was, the issue might be associated with the driver of my Adaptec 8405 RAID controller called aacraid. And indeed, after unmounting all RAID disks, stopping the stor_redfishserver and stor_tomcat servers and removing the aacraid kernel module, the shutdown was pretty normal:

There are no more of these "USB device not accepting address" errors and also there is no interruption at the very end any more. But of course it's no solution to unmount all disks, stop the services and remove the kernel module before every shutdown...

In general: What the heck has this aacraid driver to do with USB?

I also tried only to unmount the disks and stop the StorMan servers. This didn't change anything.
So I really needed to unload the kernel module.

I already tried different driver versions:
aacraid-1.2.1-52011-Debian8.1-x86_64.deb
aacraid-1.2.1-53005-Debian8.1-x86_64.deb
aacraid-1.2.1-54013-Debian8.1-x86_64.deb
All with the same behavior.

/edit:
o.. I noticed, installing these drivers doesn't change anything, because these drivers are compiled for kernel 3.16 and are installed into /usr/lib/modules/3.16.0-4-amd64 ...

That means, during all my tries the original aacraid driver which is coming with the kernel 5.10.0-10 was used:

# modinfo /usr/lib/modules/5.10.0-10-amd64/kernel/drivers/scsi/aacraid/aacraid.ko | grep version

version:        1.2.1[50983]-custom
srcversion:     5CEEEEA81EA6A7810FCAE8C
vermagic:       5.10.0-10-amd64 SMP mod_unload modversions

Seems the driver is buggy somehow, since it's working fine with disabled aacraid module?! Would you agree?

/edit #2:
I've found these DKMS drivers now: https://storage.microsemi.com/en-us...e/productid=asr-8405&dn=adaptec+raid+8405.php
Unfortunately I'm not able to install them. Tried versions 60001, 59002 and 58012.
All failed during build with different errors.. totally buggy.

$ sudo dpkg -i Downloads/aacraid-dkms_1.2.1.60001_all.deb
Vormals nicht ausgewähltes Paket aacraid-dkms wird gewählt.
(Lese Datenbank ... 326008 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../aacraid-dkms_1.2.1.60001_all.deb ...
Entpacken von aacraid-dkms (1.2.1.60001) ...
aacraid-dkms (1.2.1.60001) wird eingerichtet ...
Loading new aacraid-1.2.1.60001 DKMS files...
Building for 5.10.0-10-amd64
Building for architecture amd64
Building initial module for 5.10.0-10-amd64
Error! Bad return status for module build on kernel: 5.10.0-10-amd64 (amd64)
Consult /var/lib/dkms/aacraid/1.2.1.60001/build/make.log for more information.
dpkg: Fehler beim Bearbeiten des Paketes aacraid-dkms (--install):
 »installiertes aacraid-dkms-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück
Fehler traten auf beim Bearbeiten von:
 aacraid-dkms

See logs attached.

 

[Freeze]

In the meantime I start believing that these USB errors are not caused by the aacraid module, but that the shutdown just takes more time if the aacraid module is enabled and only because of this I can see these errors. They just don't appear with disabled aacraid because the shutdown process finishes earlier?!