On Tue, Sep 13, 2016 at 11:03:19PM +0200, Aurelien Jarno wrote: ...
> > If all of that makes no difference, what would be the next step? > > What would be interesting would be to try to reproduce the issue in > qemu or virtualbox, with as many things as possible close to your > system. > Just to clarify - you mean try to run the installer using a qemu VM as the target for installation? I can certainly try that. More details. The target system is pxe booted and next-server takes it to a (debian) system running tftpd-hpa. The defaults.cfg has lots of boot targets but the one I have been testing with is the netboot image, in manual install mode. The only boot options it is given are 'append vga=normal initrd=yadayada' It also falls over if I feed it a preseed file, where we use 'append auto=true priority=critical vga=normal initrd=yadayda url=blahdeblah' > Also you might want to use the console (alt+f2) to run wget by hand and > see if the issue happen with all hosts or only some of them. I tried to wget pages from a few web sites from the alt+f2 console. It segfaulted every time when I used a DNS name in the URL, but worked if I used an IP address in the URL. ping does the same thing; segfaults only when using domain names. If I put an entry in /etc/hosts and try to access that hostname, wget and ping also segfault, until I add this line to nsswitch.conf: hosts: files dns Then they both work for that hostname. The only other nsswitch.conf lines are for passwd, group & shadow. > > My concern is there's a segfault still lurking in the stretch > > version. If we can squash it here that fix could be forward-ported. > > This is very unlikely, as both debian-installer and glibc are quite > different in stretch and do not use the shared library reduction > anymore. Ok that's good to know.
