Re: snapshot of april 12th wont boot at all

On Tue, Apr 17, 2018 at 10:52:40PM +, Beeblebrox wrote: > My proposed plan did not work anyway, as both MINIMAL and GENERIC fail to > build. > I'll have to clone the FreeBSD repo unless Shawn has something to comment on > this. Due to our changing of certain kernel structures, GENERIC likely

Re: snapshot of april 12th wont boot at all

My proposed plan did not work anyway, as both MINIMAL and GENERIC fail to build. I'll have to clone the FreeBSD repo unless Shawn has something to comment on this. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/fr

Re: snapshot of april 12th wont boot at all

I am sorry i sent a blank email, I didn't know better so i changed it to text only. the problem i have is during the boot from the cd-rom is I just get a big black screen with a cursor and that's all, not even an attempt to install, nothing my machine is running freebsd 11.1-STABLE currently bu

Re: Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed)

On Tuesday, April 17, 2018 10:15:53 PM Vitalij Satanivskij wrote: > Dear John > > I'm try patch with no success > > http://hell.ukr.net/panic/recorder_patch165.webm > > Also I'm enable verbose boot and record boot process (hpet was disabled so > crash in another driver atach) > http://hell.ukr.

Re: snapshot of april 12th wont boot at all

Hello Ed. > If this is reproducible on stock FreeBSD can you submit a PR with CPU details? I don't have a cloned repo of FreeBSD, but AFAIK it's the "options PAX_*" related knobs in the kernel that, if eliminated, would revert the system to a FreeBSD one for all intents and purposes? I can jus

Re: Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed)

Dear John I'm try patch with no success http://hell.ukr.net/panic/recorder_patch165.webm Also I'm enable verbose boot and record boot process (hpet was disabled so crash in another driver atach) http://hell.ukr.net/panic/recorder_patch_verbose.webm root@test:/usr/src # svnlite diff Index: sys/

Re: snapshot of april 12th wont boot at all

On 17 April 2018 at 11:17, Shawn Webb wrote: > > HardenedBSD enables PTI regardless of underlying CPU by default. We've > found that some older AMD CPUs have issues with PTI as currently > implemented. The oldest AMD CPU I have is a FX-6100, and FreeBSD-CURRENT works fine there with PTI enabled.

Re: panic: VM object not locked in vm_page_ps_test()

On Tue, Apr 17, 2018 at 10:03:55AM -0700, John Baldwin wrote: > On Tuesday, April 17, 2018 10:01:41 AM John Baldwin wrote: > > My laptop running recent head panicked this morning, apparently from hitting > > a key to stop the screensaver (at which point xscreensaver prompts for a > > password to un

panic: VM object not locked in vm_page_ps_test()

My laptop running recent head panicked this morning, apparently from hitting a key to stop the screensaver (at which point xscreensaver prompts for a password to unlock). -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebs

Problem compiling rust

I have the folloing error while compiling rust on i386 current of April the 9th rust_error Description: Binary data ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: panic: VM object not locked in vm_page_ps_test()

On Tuesday, April 17, 2018 10:01:41 AM John Baldwin wrote: > My laptop running recent head panicked this morning, apparently from hitting > a key to stop the screensaver (at which point xscreensaver prompts for a > password to unlock). (Sorry, buggy mail client sent this early) panic: Lock vm obj

Re: Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed)

On Monday, April 16, 2018 10:12:13 PM Vitalij Satanivskij wrote: > > igb0@pci0:1:0:0:class=0x02 card=0x152115d9 chip=0x15218086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > device = 'I350 Gigabit Network Connection' > class = network > subclass =

Re: snapshot of april 12th wont boot at all

On Tue, Apr 17, 2018 at 11:13:51AM -0400, Beeblebrox wrote: > Hey Shawn, > > > What happens when you set vm.pmap.pti=0 at the loader prompt? > Yep, that fixed it. Booted into MYKERN without problem. > Assuming Page Table Isolation still a bit buggy? > > FreeBSD 12.0-CURRENT #3 5b8586c22aa(hardene

Re: snapshot of april 12th wont boot at all

Hey Shawn, > What happens when you set vm.pmap.pti=0 at the loader prompt? Yep, that fixed it. Booted into MYKERN without problem. Assuming Page Table Isolation still a bit buggy? FreeBSD 12.0-CURRENT #3 5b8586c22aa(hardened/current/master): Tue Apr 17 08:11:53 EDT 2018 Regards. -- HardenedBSD

Re: snapshot of april 12th wont boot at all

On Tue, Apr 17, 2018 at 9:47 AM, Beeblebrox wrote: > I have (possibly) similar problem, running kernel from March 29 as > fall-back (older kernel, latest world). > > * OS: HardenedBSD-12 on amd64 Athlon II X3 460 > * Kernels built yesterday: MYKERN & HARDENEDBSD (GENERIC with Debug). > Both kern

Re: snapshot of april 12th wont boot at all

On Tue, Apr 17, 2018 at 10:47:00AM -0400, Beeblebrox wrote: > I have (possibly) similar problem, running kernel from March 29 as > fall-back (older kernel, latest world). > > * OS: HardenedBSD-12 on amd64 Athlon II X3 460 > * Kernels built yesterday: MYKERN & HARDENEDBSD (GENERIC with Debug). >

snapshot of april 12th wont boot at all

I have (possibly) similar problem, running kernel from March 29 as fall-back (older kernel, latest world). * OS: HardenedBSD-12 on amd64 Athlon II X3 460 * Kernels built yesterday: MYKERN & HARDENEDBSD (GENERIC with Debug). Both kernels fail. No errors encountered during buildworld/kernel. Wor

Re: snapshot of april 12th wont boot at all

On Tue, 17 Apr 2018, at 02:17, Wes wrote nothing. Wes, Can you share some info? Which architecture boot method uefi mbr … Which iso / img specifically Fresh install or upgrade? Relevant loader.conf settings Your dmesg on a prior snapshot Expand on won’t boot - start at system POST and explain