Date: Thu, 8 Aug 2019 19:48:40 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Vladimir Zakharov <zakharov.vv@gmail.com> Cc: Trond =?utf-8?Q?Endrest=C3=B8l?= <trond.endrestol@ximalas.info>, freebsd-current@freebsd.org Subject: Re: r350484 and ASLR enabled - init died (signal 6, exit 0) Message-ID: <20190808164840.GH2731@kib.kiev.ua> In-Reply-To: <20190808063523.hftl7v76lo6y46dv@vzakharov> References: <alpine.BSF.2.21.99999.352.1908051436050.31116@enterprise.ximalas.info> <20190805130255.GA1121@albert.catwhisker.org> <alpine.BSF.2.21.99999.352.1908051947580.31116@enterprise.ximalas.info> <20190805192305.GC2731@kib.kiev.ua> <20190808063523.hftl7v76lo6y46dv@vzakharov>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 08, 2019 at 09:35:23AM +0300, Vladimir Zakharov wrote: > 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@# uname -a > FreeBSD vzakharov 13.0-CURRENT FreeBSD 13.0-CURRENT r350713 GENERIC-NODEBUG amd64 > > root@# grep aslr /boot/loader.conf > #kern.elf32.aslr.enable=1 > #kern.elf64.aslr.enable=1 I was able to reproduce it, try r350758.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190808164840.GH2731>