I need to make a retraction from my statement in #8. I think I was mistaken about 3.7 not working and confused connection refusal for some other reason (perhaps a timeout from a previous connection, windows does not give very descriptive prompts) with the sys_setgroups failed issue because I wasn't diligent about checking timestamps in logs. Before I tested the 3 kernels you listed I first tested (again) that 3.2 was working and 3.5/3.7 did not. It seems that 3.7 does work as well as all three mainline kernels you put in #10.
I am reminded about how in the upstream bug I posted the poster mentions that the connection issues might not crop up right away but I am absolutely sure that every attempt I have made while the server was running 3.5.0-17/18 has always resulted in a sys_setgroups panic. The fact that it does not occur in any of the other kernels seems to suggest this might be due to some ubuntu carried patch? Sorry for the confusion. ** Tags removed: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075670 Title: samba panics with sys_setgroups failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
