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 [email protected] < [email protected]>: > 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? > _______________________________________________ > [email protected] mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[email protected]" > _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[email protected]"
