Hi again, Frank Gard <frank.gard@exirius.de> (2019-05-02): > On Thu, 2 May 2019 08:55:54 +0200 Cyril Brulebois <kibi@debian.org> wrote: > > OK. What does /etc/shadow look like? > > Its content is: > > installer::1:0:99999:7::: OK, thanks. That confirms at least the echo instruction I quoted is executed, but gen-crypt didn't do its job… > > […] > > echo "installer:$(gen-crypt $PASSWORD):1:0:99999:7:::" >> /etc/shadow > > > > with gen-crypt reading some tiny amount of data from /dev/urandom. I'd > > be happy to see a syslog of an affected system (please compress it when > > attaching it to the bug report). > > > > I did a "dmesg", and the two very last lines are quite interesting, I think: > […] > [ 1.069070] sd 2:0:0:0: [sda] Attached SCSI disk > [ 1.583116] random: crng init done > [ 15.103655] usbcore: registered new interface driver usb-storage > [ 16.247345] ISO 9660 Extensions: Microsoft Joliet Level 3 > [ 16.248981] ISO 9660 Extensions: RRIP_1991A > [ 55.531147] virtio_net virtio3 ens18: renamed from eth0 > [ 102.052912] gen-crypt[3815]: segfault at ffffffff88e3d260 ip 00007f36154b2206 sp 00007ffcd3b4bbe8 error 5 in libc.so.6[7f361543c000+148000] > [ 102.052917] Code: 0f 1f 40 00 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 6a <f3> 0f 6f 20 66 0f 74 e0 > 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83 … which is understandable given the segfault. > Let me know, if you need the full log or anything else. Please mention at the very least your architecture and the target device, in case the segfault is hardware/architecture-dependent. This could be some trivial bug, but let's see what you're running d-i on. Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature