Date: Fri, 22 Apr 2016 07:30:29 -0700 (PDT) From: "Jeffrey Bouquet" <jbtakk@iherebuywisely.com> To: "jbtakk" <jbtakk@iherebuywisely.com> Cc: "current" <current@freebsd.org> Subject: Re: new content: [ buildworld fixed ] now network drops out daily Message-ID: <E1atc6H-00028i-Ne@rmm6prod02.runbox.com> In-Reply-To: <E1atb24-0000qj-4G@rmm6prod02.runbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 22 Apr 2016 06:22:04 -0700 (PDT), "Jeffrey Bouquet" <jbtakk@iherebu= ywisely.com> wrote: >=20 >=20 > ----- Start Forwarded Message ----- > Sent: Thu, 21 Apr 2016 14:10:40 -0700 (PDT) > From: "Jeffrey Bouquet" <jbtakk@iherebuywisely.com> > To: "current" <current@freebsd.org> > Subject: Re: Re: Installworld, BW, IK fixed, here are the in > out > loader.conf lines >=20 >=20 >=20 > On Thu, 21 Apr 2016 13:29:59 -0700 (PDT), "Jeffrey Bouquet" <jbtakk@ihere= buywisely.com> wrote: >=20 > >=20 > >=20 > > On Wed, 20 Apr 2016 18:37:45 -0700 (PDT), "Jeffrey Bouquet" <jbtakk@ihe= rebuywisely.com> wrote: > >=20 > > >=20 > > >=20 > > > On Wed, 20 Apr 2016 17:37:16 -0700 (PDT), "Jeffrey Bouquet" <jbtakk@i= herebuywisely.com> wrote: > > >=20 > > > >=20 > > > >=20 > > > > On Wed, 20 Apr 2016 12:28:29 -0400, Allan Jude <allanjude@freebsd.o= rg> wrote: > > > >=20 > > > > > On 2016-04-20 12:06, Jeffrey Bouquet wrote: > > > > > > unistd > > > > > >=20 > > > > > >=20 > > > > > > /usr/src/lib/libc/../../include/unistd.h:330:45: error: expecte= d function body after function declarator > > > > > > int execl( ................................. > > > > > > 332:46= :=20=20=20=20 > > > > > > same... > > > > > >=20 > > > > > > stops libc > > > > > > otherwise clang36 seems to be building so far, if it builds uns= ure about installworld > > > > > > _______________________________________________ > > > > > > freebsd-current@freebsd.org mailing list > > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@f= reebsd.org" > > > > > >=20 > > > > >=20 > > > > > The mailing list strips attachments. Can you upload it somewhere = and > > > > > provide a link > > > > >=20 > > > > > --=20 > > > > > Allan Jude > > > > > _______________________________________________ > > > > > freebsd-current@freebsd.org mailing list > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@fre= ebsd.org" > > > >=20 > > > >=20 > > > > Well, it is now r298350 Wed Apr 20... > > > > However several problems > > > >=20 > > > > SINGLE-USER BOOT PROBLEMS > > > > 1... usual boot fails, this is single-user adjusted, but I cannot a= dd swap (swapon? swapctl?) > > > > 1a... the last time, it was fixed with using the old /kernel ...=20 > > > >=20 > > > > multi-user boot problems > > > >=20 > > > > 2... the last usual boot dumped with vm_pager or something, verbos= e boot times out with xpt_config not completing. > > > > 2a.... could be a wrong setting is loader.conf, the nvidia.ko not y= et updated (which it now is ) for the latter > > > > case I have yet to reboot to test > > > > 2b... Reboot to test takes longer, /rescue/mount each filesyste= m individually...=20 > > > >=20 > > > >=20 > > > > As one might surmise, I'd rather see buildworld made more foolproof= than other recent improvements=20 > > > > (pkg, zfs, ...) > > >=20 > > > From backup, I have r288246 kernel and nvidia.ko (v11) > > > from source, I have world and all except those TWO files at r298350 )= (v11), nvidia (newer) won't load with older kernel > > > A few at-boot scripts no longer work as expected... but no other majo= r problems (swap is present again) > > > (multi-user boot works)=20 > > >=20 > > > Best practice maybe to update the kernel? It is a custom one from wa= y back in 2004 initially > > > without sound drivers and without debug symbols... and many esoteric= lines added which I cobbled > > > together at first then changed per diffs of GENERIC over the years... > > >=20 > > > Thanks for any known methods > > >=20 > > > J. Bouquet > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd= .org" > >=20 > >=20 > > Updated to a slightly-less-than-full GENERIC. Still dumped core. Move= d loader.conf out of > > the way, works fine. What will take some time now is moving loader.con= f back piece by piece > > [until/if there is/ever was a utility to do it for us... ] to find the = problematic line or two, then > > resume testing of the install of the custom kernel that also is 'fail' = status at this point... unless/until > > I decide to also test it, THEN resume the loader.conf line-by-line back= in... > >=20 > > tl;dr loader.conf problematic line and maybe an additional unknown in= either kernel text file. > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 >=20 > Half of loader.conf removed. (as below). Custom kernel restored and worki= ng. > # out snd_pcm_load=3D"YES" > # out snd_acm_load=3D"YES" > # out kern.msgbufsize=3D"130000" > # out kern.ipc.shmmni=3D"1024" > # out kern.ipc.shmseg=3D"1024" > # out hw.snd.maxautovchans=3D"4" > # out hw.snd.targetirqrate=3D"36"=20=20=20=20 > # out hint.pcm.0.buffersize=3D"65536"=20 > # out hw.snd.verbose=3D"3" > # out kern.ipc.semmns=3D"240" > # out kern.ipc.semume=3D"40" > # out kern.ipc.semmnu=3D"120" > # out vfs.read_max=3D"128"=20=20=20=20 > # out kern.randompid=3D"1" > # out kern.ipc.shmmax=3D"67108864"=20 > # out kern.ipc.shmall=3D"32768" > # out vm.kmem_size=3D"700M"=20=20=20=20 > # out vm.kmem_size_max=3D"700M"=20=20 > # out vfs.zfs.arc_max=3D"250M" > # out kern.sched.preempt_thresh=3D"224" > # out vfs.usermount=3D"1"=20=20=20 > # out kern.geom.part.check_integrity=3D"0"=20=20 > # out vm.overcommit=3D"1" > # out kern.maxfilesperproc=3D"65536" > # out kern.ipc.somaxconn=3D"1024" > # out kern.ipc.nmbclusters=3D"81920" > # out kern.fallback_elf_brand=3D"3" > # out vfs.write_behind=3D"0" >=20 > Quite a lot, as one may see. There is an equal amount non-kern (net...) r= emaining in. > Perchance someone sees an obvious problem in a value, and/or is an expert= in=20 > most of them and knows which can be safely restored for furtther testing,= and/or > which are most useful in a FreeBSD system. >=20 > Thanks. > OTOH this may help others if they also encounter the same problem, and co= uld be > included in a future wiki or UPDATING or 'man sysctl' type file somewhere= ... >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >=20 >=20 >=20 > ----- End Forwarded Message ----- >=20 > the network nfe0 seems to disappear requiring a reboot. "service netif r= estart" does not > help nor the ifconfig manually. > Is there maybe an MTU or ifconfig variable that would fix it; of one of t= he sysctls I removed > above, or is it similar to the "shaky network stability" very recent thre= ad?=20=20=20=20=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Don't wish to appear to be spamming the list, but I've learned some things = about the sysctls above [ beta ] that may be useful to others. I decided to set them after boot... ...........................................................................= .............. approx. 7 are loader.conf only approx. 15 have no problem so far, and are loaded via CLI as of now kern.randompid=3D"1" gives a result of 0 > 0 [ maybe does not work after b= oot? or a bug ] ...........................................................................= ............... three are unknown and may have been the main installkernel problem, unsure = [unless typos...] vfs.zfs.arc_max hw.snd.targetirqrate [ though it may only appear after and _load that wa= s removed ] hint.pcm.0.buffersize [ditto] ...........................................................................= ................ This is all hastily typed, so pardon misspellings... If nfe0 stays up until shutdown within an hour or two, that would be [maybe= ] a good sign... for those sysctls anyway. OTOH I am now *not* loading ten or so other sysctls = right at bringing the network up, so a lot of testing would be due here ... So progress at least.=20=20=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1atc6H-00028i-Ne>