5.8.0-52 in proposed works for me. Thanks!
But why wait more than 2 weeks to resolve it?
Thousands of computers are directly impacted and unusable and not everyone know
how they can change his kernel version on boot. Only around me, 4 people are
impacted and also myself on 2 computers.
--
You
Is ok for me, 4.8.0-55-generic #58~16.04.1-Ubuntu SMP
No more flood with this kernel version.
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
@Joseph Salisbury (jsalisbury)
I installed your patched kernel on my Desktop today and it run now from
3 hours without problem, no more cifs flood.. :)
So, i will continue my test today, but apparently this bug is fixed in
your patched kernel.
If is confirmed, can you tell me approximatively
@Joseph Salisbury (jsalisbury)
Can you please tell me from which version of ubuntu kernel this is
applied. I tried also the last 4.4 on Ubuntu 16.04 (4.4.0-78-generic
#99-Ubuntu SMP) and i have the same problem.
Thanks
--
You received this bug notification because you are a member of Kernel
4.8.0-52-generic #55~16.04.1-Ubuntu released today (2017-05-16) not ok -
The bug is still here too! Please fix this quickly because my company
network are overloaded because of this bug. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is
I have 5 desktop on Ubuntu 16.04 with various official kernel 4.4, 4.8,
4.10. All this desktop are connected via CIFS to a Windows Server 2008
R2 for a simple shared folder.
After some minutes of activity i got a high CIFS flood traffic between
desktop and server. Many giga per desktop are
6 matches
Mail list logo
