Re: UEFI GOP: screen goes blank during boot after loader is finished

On Fri, Nov 16, 2018 at 8:03 AM Warner Losh wrote: > > > > On Thu, Nov 15, 2018 at 12:10 PM Rebecca Cran wrote: >> >> On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote: >> >> > What is the ConOut evifar look like? We set serial when the UEFI env says >> > to do so. >> >> Booting

FreeBSD 12.0-RC1 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The first RC build of the 12.0-RELEASE release cycle is now available. Installation images are available for: o 12.0-RC1 amd64 GENERIC o 12.0-RC1 i386 GENERIC o 12.0-RC1 powerpc GENERIC o 12.0-RC1 powerpc64 GENERIC64 o 12.0-RC1 powerpcspe

Re: UEFI GOP: screen goes blank during boot after loader is finished

> On 17 Nov 2018, at 18:29, Subbsd wrote: > > On Fri, Nov 16, 2018 at 8:03 AM Warner Losh > wrote: >> >> >> >> On Thu, Nov 15, 2018 at 12:10 PM Rebecca Cran wrote: >>> >>> On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote: >>> What is the ConOut

Re: UEFI GOP: screen goes blank during boot after loader is finished

On Saturday, 17 November 2018 09:29:34 MST Subbsd wrote: > Thus, perhaps the root of this problem should be sought in > uefi-edk2-bhyve the package. Latest CBSD release (12.0.1) fixed this > problem by disabling serial console. However, CBSD uses an alternative > boot method for bhyve (

building release images broken?

Any clues as to what's broken here? I'm trying to build a CD and/or DVD image. My tree is at SVN r340525. -- >>> Kernel build for GENERIC completed on Sat Nov 17 22:19:48 UTC 2018

Ryzen Threadripper 1950X based on head -r340287: sysctl dev.cpu: 0-30 but no 31? (top shows all 31 "CPU"s)

For some reason there is no .dev.cpu.31 listed for the 1950X that I use. This is a native boot, not use under Hyper-V. For illustration I list: # sysctl dev.cpu | grep "desc" dev.cpu.30.%desc: ACPI CPU dev.cpu.29.%desc: ACPI CPU dev.cpu.28.%desc: ACPI CPU dev.cpu.27.%desc: ACPI CPU

Re: Ryzen Threadripper 1950X based on head -r340287: sysctl dev.cpu: 0-30 but no 31? (top shows all 0-31 "CPU"s) [subject corrected]

[Fixing dumb, confusing subject typo. No change below.] On 2018-Nov-17, at 12:54, Mark Millard wrote: > For some reason there is no .dev.cpu.31 listed for the 1950X that > I use. This is a native boot, not use under Hyper-V. For > illustration I list: > > # sysctl dev.cpu | grep "desc" >

Re: Panic on kern_event.c

On Fri, Nov 16, 2018 at 05:56:54PM +0100, Sylvain GALLIANO wrote: > Le ven. 16 nov. 2018 à 16:42, Mark Johnston a écrit : > > > On Fri, Nov 16, 2018 at 03:47:39PM +0100, Sylvain GALLIANO wrote: > > > Le jeu. 15 nov. 2018 à 23:10, Mark Johnston a écrit > > : > > > > > > > On Thu, Nov 08, 2018 at