Tested the latest upstream 4.4 stable kernel. All seems well in upstream. It is the current LTS kernel version that seems to have the glitch.
To summarize:
4.4.17 : no problem. (Commit: 133cec911c639d2cdf544ed602442951f702e08c)
4.4.15 : no problem. (Commit: 35467dc7630af60abacc330f64029d081f160530)
4.4.14 : no problem. (Commit: 9ca1d50fa959cda1f04f43275f7930a70f1a631e)
Packaged LTS (xenial) versions:
4.4.0-34 #53: problem with cifs.
4.4.0-21 #37: no problem, everything is Dandy.
Dear reader,
Tested the latest upstream 4.4 stable kernel. All seems well in upstream. It is the current LTS kernel version that seems to have the glitch.
To summarize: cdf544ed6024429 51f702e08c) abacc330f64029d 081f160530) 1f04f43275f7930 a70f1a631e)
4.4.17 : no problem. (Commit: 133cec911c639d2
4.4.15 : no problem. (Commit: 35467dc7630af60
4.4.14 : no problem. (Commit: 9ca1d50fa959cda
Packaged LTS (xenial) versions:
4.4.0-34 #53: problem with cifs.
4.4.0-21 #37: no problem, everything is Dandy.
Cheers, Chris