Re: r350484 and ASLR enabled - init died (signal 6, exit 0)

From: Vladimir Zakharov <zakharov.vv_at_gmail.com>
Date: Thu, 8 Aug 2019 09:35:23 +0300
On Mon, Aug 05, 2019, Konstantin Belousov wrote:
> On Mon, Aug 05, 2019 at 08:10:43PM +0200, Trond Endrestøl wrote:
> > On Mon, 5 Aug 2019 06:02-0700, David Wolfskill wrote:
> > 
> > > On Mon, Aug 05, 2019 at 02:53:04PM +0200, Trond Endrestøl wrote:
> > > > Hi,
> > > > 
> > > > Has anyone else noticed the kernel being unable to spawn init lately?
> > > > 
> > > > All I get is:
> > > > 
> > > > init died (signal 6, exit 0)
> > > > panic: Going nowhere without my init!
> > > > 
> Try r350608. There was a mis-merge in the committed patch (more serious
> part), and some limits were not applied, which I did not see in my
> testing due to the mismatch between stock FreeBSD and my testing
> environment.

The issue persists still at r350713 on HP Probook after clean rebuild.

root_at_# uname -a
FreeBSD vzakharov 13.0-CURRENT FreeBSD 13.0-CURRENT r350713 GENERIC-NODEBUG  amd64

root_at_# grep aslr /boot/loader.conf
#kern.elf32.aslr.enable=1
#kern.elf64.aslr.enable=1

-- 
Regards,                 | "In theory there is no difference between theory
  Vladimir Zakharov      | and practice. In practice there is."- Yogi Berra

Received on Thu Aug 08 2019 - 04:35:27 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:21 UTC