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 >> reorders drives on a f

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 like

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 > regressed. I'd like to b

!EARLY_AP_STARTUP and -CURRENT

2017-08-30 Thread Kevin Bowling
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 like to be able to run w/o EARLY_AP_STARTUP right quick so I can take a mor