Per Hans .. this should fix it: r314953 | hselasky | 2017-03-09 04:17:43 -0500 (Thu, 09 Mar 2017) | 9 lines Changed paths: M /head/sys/compat/linuxkpi/common/src/linux_work.c Don't create any threads before SI_SUB_INIT_IF in the LinuxKPI. Else kthread_add() will assert it is called too soon. This fixes a startup issue when COMPAT_LINUXKPI is in enabled the kernel configuration file. imb On 3/8/17 6:02 PM, Michael Butler wrote: > The difference between a kernel that boots and another that won't is .. > > imb_at_toshi:/home/imb> diff -cw /sys/amd64/conf/TOSHI~ /sys/amd64/conf/TOSHI > *** /sys/amd64/conf/TOSHI~ Wed Mar 8 10:05:09 2017 > --- /sys/amd64/conf/TOSHI Wed Mar 8 17:33:25 2017 > *************** > *** 373,379 **** > # Enable Linux ABI emulation > #options COMPAT_LINUX32 > # Enable Linux KPI > ! #options COMPAT_LINUXKPI > > # Enable the linux-like proc filesystem support (requires COMPAT_LINUX > # and PSEUDOFS) > --- 373,379 ---- > # Enable Linux ABI emulation > #options COMPAT_LINUX32 > # Enable Linux KPI > ! options COMPAT_LINUXKPI > > # Enable the linux-like proc filesystem support (requires COMPAT_LINUX > # and PSEUDOFS) > > Seems to point at something in SVN r314843 :-( > > imb > > > On 03/08/17 17:10, Eric Camachat wrote: >> I have the same issue on Dell Precision M4800. >> >> On Wed, Mar 8, 2017 at 6:26 AM, David Wolfskill <david_at_catwhisker.org> wrote: >>> On Wed, Mar 08, 2017 at 07:55:44AM -0500, Michael Butler wrote: >>>> My laptop usually starts like this .. >>>> >>>> FreeBSD 12.0-CURRENT #21 r314812M: Mon Mar 6 19:34:51 EST 2017 >>>> imb_at_toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/TOSHI amd64 >>>> FreeBSD clang version 4.0.0 (branches/release_40 296509) (based on LLVM >>>> 4.0.0) >>>> ... >>>> >>>> This morning, I get this :-( >>>> >>>> FreeBSD 12.0-CURRENT #27 r314889M: Tue Mar 7 19:55:25 EST 2017 >>>> imb_at_toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/TOSHI >>>> FreeBSD clang version 4.0.0 (branches/release_40 296509) (based on LLVM >>>> 4.0.0) >>>> VT(vga): resolution 640x480 >>>> panic: kthread_add called too soon >>>> [ .. ] >>>> >>>> Any thoughts? >>>> .... >>> "uname -vp" output from my last several (successful) build/smoke-tests >>> for head: >>> >>> FreeBSD 12.0-CURRENT #274 r314653M/314653:1200023: Sat Mar 4 06:46:18 PST 2017 root_at_g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 >>> >>> FreeBSD 12.0-CURRENT #275 r314700M/314700:1200023: Sun Mar 5 07:45:20 PST 2017 root_at_g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 >>> >>> FreeBSD 12.0-CURRENT #276 r314770M/314770:1200023: Mon Mar 6 05:45:44 PST 2017 root_at_g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 >>> >>> FreeBSD 12.0-CURRENT #277 r314842M/314842:1200023: Tue Mar 7 05:55:58 PST 2017 root_at_g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 >>> >>> FreeBSD 12.0-CURRENT #278 r314906M/314906:1200024: Wed Mar 8 06:05:49 PST 2017 root_at_g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 >>> >>> Sorry it's not more help. >>> >>> Peace, >>> david >>> -- >>> David H. Wolfskill david_at_catwhisker.org >>> How could one possibly "respect" a misogynist, racist, bullying con-man??!? >>> >>> See http://www.catwhisker.org/~david/publickey.gpg for my public key. >> >> > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"Received on Thu Mar 09 2017 - 12:58:57 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:10 UTC