On 03/08/17 08:12, Andriy Gapon wrote:
> On 08/03/2017 14:55, Michael Butler wrote:
>> My laptop usually starts like this ..
>>
>> FreeBSD 12.0-CURRENT #21 r314812M: Mon Mar  6 19:34:51 EST 2017
>>     i...@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)
>> VT(vga): resolution 640x480
>> info: [drm] Initialized drm 1.1.0 20060810
>> CPU: Intel(R) Core(TM)2 CPU         T7600  @ 2.33GHz (2327.56-MHz
>> K8-class CPU)
>>  [ .. ]
>>
>> This morning, I get this :-(
>>
>> FreeBSD 12.0-CURRENT #27 r314889M: Tue Mar  7 19:55:25 EST 2017
>>     i...@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?
> 
> Were messages replaced by the second '[..]' really so useless?

Just the CPU number, then it halts :-(

With no log, I typed what I could remember.

With a verbose start-up, I can see that it gets through parsing the ACPI
tables but fails shortly after. When I get home this evening, I'll take
a screenshot,

        imb


_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to