Bug#843128: partially solved

[Ricardo Fabian Peliquero <zhana@lasampa.com.ar>]

On Fri, Dec 09, 2016 at 01:03:44PM +0000, Ben Hutchings wrote:
> On Fri, 2016-12-09 at 01:18 -0300, Ricardo Fabian Peliquero wrote:
> >  from: linux-image-4.8.0-1-amd64-unsigned:amd64 (4.8.5-1)
> >    to: linux-image-4.9.0-rc8-amd64-unsigned:amd64 (4.9~rc8-1~exp1)
> > and installing mingetty(8)
> > the system is booting well (e.g. without kernel panic).
> > 
> > But the following errors appeared for ttys using these lines in /etc/inittab:
> > 
> > 2:23:respawn:/sbin/fgetty tty2
> > # Produces error. Output:
> >  [   14.741345] fgetty[1309] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffcb7dbade0 ax:ff[   14.753469] fgetty[1309]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffcb7dbade0 error 15
> > ...
> >  INIT: Id "2" respawning too fast: disabled for 5 minutes
> > 
> > 3:23:respawn:/sbin/ngetty 3
> > # Produces error. Output:
> >  [   14.670134] ngetty-helper[1311] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffca011e1a[   14.684298] ngetty-helper[1311]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffca011e1a0 error 15
> 
> fgetty uses dietlibc, and the stable version of dietlibc still uses the
> vsyscall feature which is now disabled by default.  You can make it
> work again by adding 'vsyscall=emulate' to the kernel command line.
> 
> I'll have to reconsider whether to revert the configuration change now
> that I know dietlibc is a problem.

Your suggestion worked here.

I will be using vsyscall emulation option appended to lilo.conf until better resolution.

Thank you!

Ricardo