Re: !EARLY_AP_STARTUP and -CURRENT

2017-08-31 Thread Gary Jennejohn
On Wed, 30 Aug 2017 16:54:07 -0700 Kevin Bowling wrote: > I'm dealing with a shit sandwich right now where the mps(4) or cam_da > reorders drives on a few thousand legacy MBR machines I have (and I > can't easily install glabel ATM), and !EARLY_AP_STARTUP seems to have

Re: !EARLY_AP_STARTUP and -CURRENT

2017-08-31 Thread John Baldwin
On Wednesday, August 30, 2017 04:54:07 PM Kevin Bowling wrote: > I'm dealing with a shit sandwich right now where the mps(4) or cam_da > reorders drives on a few thousand legacy MBR machines I have (and I > can't easily install glabel ATM), and !EARLY_AP_STARTUP seems to have > regressed. I'd

Re: How to know the address ranges of kernel stacks, for user processes and kernel threads?

2017-08-31 Thread Eugene Grosbein
On 29.01.2015 07:54, Yue Chen wrote: > It seems that each kernel stack has two pages (IA-32) to use. Does x86_64 > still have two pages or more? One can change number of kernel stack pages for i386 and amd64 platforms by means of /boot/loader.conf without need to rebuild a kernel using

Re: !EARLY_AP_STARTUP and -CURRENT

2017-08-31 Thread Kevin Bowling
panic: mutex sched lock 0 not owned at /d0/kev/freebsd/sys/kern/sched_ule.c:2379 On Thu, Aug 31, 2017 at 7:38 AM, John Baldwin wrote: > On Wednesday, August 30, 2017 04:54:07 PM Kevin Bowling wrote: >> I'm dealing with a shit sandwich right now where the mps(4) or cam_da >>