Very long boot time with Chelsio T320 10GBASE-R RNIC adapter

[Corsaire]

I have a Chelsio T320 10GBASE-R RNIC in my machine apparently triggering a very long boot time.

I initially thought about a USB problem as I wrote in ticket #1704614 but new tests showed me otherwise.

booting with this parameters yield some interesting things:
GRUB_CMDLINE_LINUX_DEFAULT="--verbose nosplash debug"

[ 4.772733] hid-generic 0003:046D:C22D.0009: input,hiddev0,hidraw8: USB HID v1.11 Device [Logitech G510 Gaming Keyboard] on usb-0000:00:1d.0-1.8.1.2.2/input1
[ 4.877277] usb 2-1.8.1.3.4: New USB device found, idVendor=046d, idProduct=c069
[ 4.877360] usb 2-1.8.1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.877440] usb 2-1.8.1.3.4: Product: USB Laser Mouse
[ 4.877504] usb 2-1.8.1.3.4: Manufacturer: Logitech
[ 4.883052] input: Logitech USB Laser Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8.1/2-1.8.1.3/2-1.8.1.3.4/2-1.8.1.3.4:1.0/0003:046D:C069.000A/input/input12
[ 4.883391] hid-generic 0003:046D:C069.000A: input,hidraw9: USB HID v1.10 Mouse [Logitech USB Laser Mouse] on usb-0000:00:1d.0-1.8.1.3.4/input0
[ 62.501496] systemd-udevd[110]: seq 1103 '/devices/pci0000:00/0000:00:01.1/0000:02:00.0/net/eth0' is taking a long time
[ 91.836493] systemd-udevd[131]: error changing net interface name 'eth0' to 'enp2s0': File exists
[ 91.836583] systemd-udevd[131]: could not rename interface '3' from 'eth0' to 'enp2s0': File exists
[ 91.908818] raid6: sse2x1 gen() 5176 MB/s
[ 91.976808] raid6: sse2x1 xor() 5202 MB/s
[ 92.044810] raid6: sse2x2 gen() 10397 MB/s
[ 92.112810] raid6: sse2x2 xor() 8718 MB/s
[ 92.180800] raid6: sse2x4 gen() 15554 MB/s
[ 92.248797] raid6: sse2x4 xor() 11584 MB/s
[ 92.248872] raid6: using algorithm sse2x4 gen() 15554 MB/s

systemd-udevd seems to get stuck quite a long time here.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1736947

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Corsaire (stranche)]

For several reasons I had to scrap the machine and rebuild with different hardware, I couldn't afford such long boot time, so I can't run the apport-collect command.

I had those reports sitting for quite some time before I made the present ticket.
However the information in ticket #1704614 are relevant.

[Corsaire (stranche)]

could this be related ?

https://www.spinics.net/lists/linux-rdma/msg57490.html

[Benjamin Drung (bdrung)]

The patch mentioned in https://www.spinics.net/lists/linux-rdma/msg57490.html is part of the 16.0 release.

[Corsaire (stranche)]

what is "16.0 release" ?
you mean something like Ubuntu 16.04 or 16.10 ?

the patch described is from november 2017 so it's very unlikely.

[Benjamin Drung (bdrung)]

To clarify: The patch mentioned in https://www.spinics.net/lists/linux-rdma/msg57490.html is part of the rdma-core 16.0 release. Therefore this fix will be included in Ubuntu 18.04 (bionic).

[Christian Ehrhardt  (paelzer)]

rdma-core is on 17.0-1 in latest Debian and Ubuntu Bionic 18.04.
This includes there fix as also outlined by bdrung.

Therefore setting this to fix released.