About "hv_vmbus: probe failed for device vmbus_0_17 (-22)" messages.

Issue

• The following message appears in our customer's messages.

kernel: hv_vmbus: probe failed for device vmbus_0_17 (-22)
kernel: hv_util: probe of vmbus_0_17 failed with error -22

• logs in normal

Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_1 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_2 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_3 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_4 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_5 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_6 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_7 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_8 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_9 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_10 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_11 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_12 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_13 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_14 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_15 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: child device vmbus_0_16 registered
Mar 25 04:38:27 server10 kernel: hv_vmbus: registering driver hv_storvsc
Mar 25 04:38:27 server10 kernel: hv_vmbus: registering driver hyperv_fb
Mar 25 04:38:27 server10 kernel: hv_utils: Registering HyperV Utility Driver
Mar 25 04:38:27 server10 kernel: hv_vmbus: registering driver hv_util
Mar 25 04:38:27 server10 kernel: hv_vmbus: registering driver hv_netvsc
Mar 25 04:38:27 server10 kernel: hv_netvsc: hv_netvsc channel opened successfully
Mar 25 04:38:27 server10 kernel: hv_netvsc vmbus_0_14: Device MAC 00:1d:d8:b7:1c:0f link state up
Mar 25 04:38:27 server10 kernel: hv_netvsc: hv_netvsc channel opened successfully
Mar 25 04:38:27 server10 kernel: hv_netvsc vmbus_0_15: Device MAC 00:1d:d8:b7:1c:0e link state up
Mar 25 04:38:27 server10 kernel: hv_netvsc: hv_netvsc channel opened successfully
Mar 25 04:38:27 server10 kernel: hv_netvsc vmbus_0_16: Device MAC 00:1d:d8:b7:1c:13 link state up
Mar 25 04:38:27 server10 kernel: hv_vmbus: registering driver hid_hyperv
Mar 25 04:38:27 server10 kernel: hv_vmbus: registering driver hv_balloon

• logs in trouble

Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_1 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_2 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_3 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_4 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_5 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_6 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_7 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_8 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_9 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_10 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_11 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_12 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_13 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_14 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_15 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_16 registered
Mar 31 04:12:36 server10 kernel: hv_vmbus: registering driver hv_storvsc
Mar 31 04:12:36 server10 kernel: hv_vmbus: registering driver hyperv_fb
Mar 31 04:12:36 server10 kernel: hv_utils: Registering HyperV Utility Driver
Mar 31 04:12:36 server10 kernel: hv_vmbus: registering driver hv_util
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_9 unregistered
Mar 31 04:12:36 server10 kernel: hv_vmbus: registering driver hv_netvsc
Mar 31 04:12:36 server10 kernel: hv_netvsc: hv_netvsc channel opened successfully
Mar 31 04:12:36 server10 kernel: hv_netvsc vmbus_0_14: Device MAC 00:1d:d8:b7:1c:0f link state up
Mar 31 04:12:36 server10 kernel: hv_netvsc: hv_netvsc channel opened successfully
Mar 31 04:12:36 server10 kernel: hv_netvsc vmbus_0_15: Device MAC 00:1d:d8:b7:1c:0e link state up
Mar 31 04:12:36 server10 kernel: hv_netvsc: hv_netvsc channel opened successfully
Mar 31 04:12:36 server10 kernel: hv_netvsc vmbus_0_16: Device MAC 00:1d:d8:b7:1c:13 link state up
Mar 31 04:12:36 server10 kernel: hv_vmbus: registering driver hid_hyperv
Mar 31 04:12:36 server10 kernel: hv_vmbus: registering driver hv_balloon
Mar 31 04:12:36 server10 kernel: hv_vmbus: probe failed for device vmbus_0_17 (-22)
Mar 31 04:12:36 server10 kernel: hv_util: probe of vmbus_0_17 failed with error -22
Mar 31 04:12:36 server10 kernel: hv_vmbus: child device vmbus_0_17 registered

• How reproducible:

  • sometimes.

• Steps to Reproduce:

  • system reboot.