Hi Steve, We've been running the newer kernel - upgraded from 4.15.0 to 5.0.0 using Ubuntu 18.04's LTS Enablement Stack - for several days, and it has certainly solved the frequent reconnection problem, so thanks for letting me know about the reconnection fixes that went in almost a year ago. The only negative we are experiencing since the upgrade is that our VMs sometimes become unresponsive - appearing to require a reboot - with kernel messages like this: [74146.705917] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [74146.716713] rcu: (detected by 0, t=285034 jiffies, g=15795253, q=11) [74146.718805] rcu: All QSes seen, last rcu_sched kthread activity 285035 (4313428844-4313143809), jiffies_till_next_fqs=1, root ->qsmask 0x0 [74146.723702] rcu: rcu_sched kthread starved for 285036 jiffies! g15795253 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=0 [74146.727649] rcu: RCU grace-period kthread stack dump: [74160.609964] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [cifsd:2854] [74172.594002] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [cifsd:2441] I wonder if this could be a different symptom of the same underlying problem? Of course we would prefer not to have production VMs becoming unresponsive, but maybe this way, we are detecting and containing the problem earlier, so we can take the required action (reboot), instead of waiting for our CIFS service providers or authentication service providers to complain about the frequent reconnections? Cheers, James
