Re: start-up failure at SVN r314889

2017-03-10 Thread Eric Camachat
It works, thank you!

On Thu, Mar 9, 2017 at 5:58 AM, Michael Butler
 wrote:
> 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@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 
>>> 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
>  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)
> ...
>
> 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?
> 

 "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 r...@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 r...@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 r...@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 r...@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 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY
 amd64

 Sorry it's not more help.

 Peace,
 david
 --
 David H. Wolfskill  da...@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@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
>
> ___
> 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"



-- 
☀Eric
___
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"

Re: start-up failure at SVN r314889

2017-03-09 Thread Michael Butler

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@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  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
 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)
...

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?


"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 r...@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 r...@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 r...@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 r...@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 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  amd64

Sorry it's not more help.

Peace,
david
--
David H. Wolfskill  da...@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@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


___
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"


Re: start-up failure at SVN r314889

2017-03-08 Thread Michael Butler
The difference between a kernel that boots and another that won't is ..

imb@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  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
>>> 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)
>>> ...
>>>
>>> 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?
>>> 
>>
>> "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 r...@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 r...@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 r...@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 r...@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 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  amd64
>>
>> Sorry it's not more help.
>>
>> Peace,
>> david
>> --
>> David H. Wolfskill  da...@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@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: start-up failure at SVN r314889

2017-03-08 Thread Eric Camachat
I have the same issue on Dell Precision M4800.

On Wed, Mar 8, 2017 at 6:26 AM, David Wolfskill  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
>> 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)
>> ...
>>
>> 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?
>> 
>
> "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 r...@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 r...@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 r...@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 r...@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 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  amd64
>
> Sorry it's not more help.
>
> Peace,
> david
> --
> David H. Wolfskill  da...@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.



-- 
☀Eric
___
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"

Re: start-up failure at SVN r314889

2017-03-08 Thread David Wolfskill
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
> 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)
> ...
> 
> 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?
> 

"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 r...@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 r...@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 r...@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 r...@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 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  amd64

Sorry it's not more help.

Peace,
david
-- 
David H. Wolfskill  da...@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.


signature.asc
Description: PGP signature


Re: start-up failure at SVN r314889

2017-03-08 Thread Michael Butler
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"


Re: start-up failure at SVN r314889

2017-03-08 Thread Andriy Gapon
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?


-- 
Andriy Gapon
___
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"


start-up failure at SVN r314889

2017-03-08 Thread Michael Butler
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?

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"