Date: Thu, 3 Oct 2019 10:57:23 +0200 From: Johan Hendriks <joh.hendriks@gmail.com> To: "mms.vanbreukelingen@gmail.com" <mms.vanbreukelingen@gmail.com>, FreeBSD <freebsd-current@freebsd.org> Subject: Re: Kernel panic after rebuilding CURRENT Message-ID: <CAOaKuAUX0LxcQxr%2B88ze-3_3u2ZGd4ahKzUgAPWoR0bebWyy=w@mail.gmail.com> In-Reply-To: <1332716122.92456.1569583378388@mail.yahoo.com> References: <427109546.8526663.1569425410318.ref@mail.yahoo.com> <427109546.8526663.1569425410318@mail.yahoo.com> <CAOaKuAVgNJowMigN062OnLM%2BPsi%2B6YBOrX_qp9dzfkfPdTia3A@mail.gmail.com> <1332716122.92456.1569583378388@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes for me too. Op vr 27 sep. 2019 om 13:23 schreef mms.vanbreukelingen@gmail.com < mms.vanbreukelingen@gmail.com>: > Works again, just 'svn up' to the latest release, rebuuld, nothing to > do with virtualization but a serious kernel problem - IMO having too little > userspace and too much right winged here. > > Miranda > > On Fri, 27 Sep 2019 at 11:48, Johan Hendriks > <joh.hendriks@gmail.com> wrote: > Just a me too, for me it is a standard FreeBSD running on virtualbox. > > regards, > Johan > > > Op wo 25 sep. 2019 om 17:30 schreef mms.vanbreukelingen@gmail.com < > mms.vanbreukelingen@gmail.com>: > > Had verbose on and got the following kernel error on 2900000: > taskqgroup_adjust_if_config_tqg: panic: sched_pickcpu: failed to find a cpu > Looked for device tqg, isn't available in a slightly changing GENERIC > custom. I know what this personally means to me, incompatibility and a > lack of social integration, but what's the reason for BSD telling me: > "thank you, that's it!" I have LOCK_PROFILING as option for building, but > this had nothing to do with that kinda problem. > Reversion from this morning, as a lack of Inet at the moment, I had to > 'svn up' from within Linux with ufs write enabled and gave root to the > rescue CD for fsck'ing the /dev/ada0p7. The hashkey terror stops and when > unmounted without flags -fl on arch. They're doing well together simple > because if unification purpose against monopoly. > Had to rebuild without SMP, so virtualization is problematic. #ing the > ule_scheduler shouldn't be "unticked", as this causes severe compile > errors. > I think she just wants a backward development at this age, nostalgia > electronica should be a study tribe on universities like history in > school! Anyone able to get 2nd CPU up again? > > _______________________________________________ > 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 > " > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOaKuAUX0LxcQxr%2B88ze-3_3u2ZGd4ahKzUgAPWoR0bebWyy=w>