I'm seeing similar behaviour too - on a Ubuntu 14.04.4 box, completely up to date. I just had it freeze, which marks the third or fourth time I've either had to Magic-SysRq it, or pull the power, since the Badlock date.
The box has "plenty" of RAM (it was recently upgraded from 8GB to 16GB in fact, some time in March) but I don't believe this issue ever happened with 8GB and Samba 4.1.6. It acts as a file server for a small office of 12 people, which I think would count as lightly loaded in terms of Samba installations? All I have so far is a snippet from /var/log/kernel.log of the call trace which I've attached. If there is more information that would be useful next time this happens, let me know what you need and I'll get it. Unfortunately there is (currently) no load monitoring on this box, so I don't know whether we're getting a similar increase in iowait time before the crash - although the box is logging soft lockup errors, from a user perspective the box is working perfectly fine until it freezes altogether and stops responding to pings or console activity. ** Attachment added: "Sample smb lockup error - there are many more of these before the box froze" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1572608/+attachment/4661413/+files/octanesmb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572608 Title: Samba 2:4.3.8+dfsg-0ubuntu0.14.04.2 Reversion: CPU Soft Lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1572608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
