r350583 - init died (signal 6, exit 0)

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! /sbin/init hasn't had any changes in 4 months, and is present in /sbin in the new BE. I've tried and failed in VBox at home this weekend,

Re: r350583 - init died (signal 6, exit 0)

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! > > /sbin/init hasn't had any changes in 4 months, and is p

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

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 with

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

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? > > > > > >

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

On Mon, 5 Aug 2019 22:23+0300, Konstantin Belousov wrote: > On Mon, Aug 05, 2019 at 08:10:43PM +0200, Trond Endrestøl wrote: > > > I'm going home and see if VBox 6.0.10 exhibits the same behaviour. > > Try r350608. There was a mis-merge in the committed patch (more serious > part), and some limi