[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #8 from Eugene Grosbein --- Created attachment 192172 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=192172=edit some debug info for snmpd from the crashdump Note that snmpd is hung on sx_xlock()

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #10 from Mark Knight --- As suggested, I just tried commenting out vm.defer_swapspace_pageouts=1. Commenting it out from /etc/sysctl.conf didn't make any difference, 10.4 still deadlocks. -- You are

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #11 from Eugene Grosbein --- (In reply to Mark Knight from comment #9) What is UID 104 here? It seems it is used for some perl process that may be triggering the problem and not snmpd. -- You are receiving

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #9 from Mark Knight --- You asked: > What do you use vm.defer_swapspace_pageouts=1 for? After moving existing disks to a new chassis I have more RAM than swap and repartitioning would be a pain - I really

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #13 from Mark Knight --- I just tried disabling logitechmediaserver and restarting. Didn't help. Then I disabled mrtg and restarted. Still didn't help. Here's a fresh dump with neither running. Same repo

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #12 from Mark Knight --- UID 104 is: slimserv:*:104:104:Slim Devices SlimServer pseudo-user:/nonexistent:/usr/sbin/nologin ps (on a working kernel), shows: slimserv1117 0.0 0.9 253920 147596 - Ss

kern.sched.quantum: Creepy, sadistic scheduler

Occasionally I noticed that the system would not quickly process the tasks i need done, but instead prefer other, longrunning tasks. I figured it must be related to the scheduler, and decided it hates me. A closer look shows the behaviour as follows (single CPU): Lets run an I/O-active task,