Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Sep 2019 15:30:10 +0000 (UTC)
From:      "mms.vanbreukelingen@gmail.com" <mms.vanbreukelingen@gmail.com>
To:        "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject:   Kernel panic after rebuilding CURRENT
Message-ID:  <427109546.8526663.1569425410318@mail.yahoo.com>
References:  <427109546.8526663.1569425410318.ref@mail.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help

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?  



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?427109546.8526663.1569425410318>