Quote:
Originally Posted by jb_daefo
# out snd_pcm_load="YES"
# out snd_acm_load="YES"
# out kern.msgbufsize="130000"
# out kern.ipc.shmmni="1024"
# out kern.ipc.shmseg="1024"
# out hw.snd.maxautovchans="4"
# out hw.snd.targetirqrate="36"
# out hint.pcm.0.buffersize="65536"
# out hw.snd.verbose="3"
# out kern.ipc.semmns="240"
# out kern.ipc.semume="40"
# out kern.ipc.semmnu="120"
# out vfs.read_max="128"
# out kern.randompid="1"
# out kern.ipc.shmmax="67108864"
# out kern.ipc.shmall="32768"
# out vm.kmem_size="700M"
# out vm.kmem_size_max="700M"
# out vfs.zfs.arc_max="250M"
# out kern.sched.preempt_thresh="224"
# out vfs.usermount="1"
# out kern.geom.part.check_integrity="0"
# out vm.overcommit="1"
# out kern.maxfilesperproc="65536"
# out kern.ipc.somaxconn="1024"
# out kern.ipc.nmbclusters="81920"
# out kern.fallback_elf_brand="3"
# out vfs.write_behind="0"
Removed those (about half of what was there) from
loader.conf... custom kernel restored and working fine.
...................
Remains to be seen which is problematic and/or has
a wrong value assigned to it...
So solved almost completely for now.
And learned a few tricks...
|
.................................................. ................
and now nfe0 seems to drop out randomly after a few hours. I emailed
the freebsd-current list [another person had similar issues]... perchance
someone knows of an MTU , duplex, nfe sysctl, one of those
sysctls above that was removed, another add-in card, a second card
that may work after the first drops out [ sort of like lagg0 ], or some
other workaround [ a more stable driver/chipset to use... ]
[ slight chance it is due to many areas of this local area switching
from [redacted] to [ redacted ], but that is not the broadband provider here,
so it would be some hop upstream... and works again upon reboot
so doubtful...