From owner-freebsd-current@freebsd.org Tue Aug 22 18:09:13 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 195A9DD920D for ; Tue, 22 Aug 2017 18:09:13 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id ED63B6E98B for ; Tue, 22 Aug 2017 18:09:12 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: by mailman.ysv.freebsd.org (Postfix) id ECC9FDD920B; Tue, 22 Aug 2017 18:09:12 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC6CEDD920A for ; Tue, 22 Aug 2017 18:09:12 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 694C86E989; Tue, 22 Aug 2017 18:09:12 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann ([77.179.73.221]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M3j17-1dSxm002Rl-00rInk; Tue, 22 Aug 2017 20:09:01 +0200 Date: Tue, 22 Aug 2017 20:08:57 +0200 From: "Hartmann, O." To: David Wolfskill Cc: Konstantin Belousov , current@freebsd.org, Dimitry Andric Subject: Re: SIGSEGV in /bin/sh after r322740 -> r322776 update Message-ID: <20170822200841.180f633b@hermann> In-Reply-To: <20170822133836.GQ1130@albert.catwhisker.org> References: <20170822114627.GC1130@albert.catwhisker.org> <20170822115923.GC1700@kib.kiev.ua> <20170822122836.GH1130@albert.catwhisker.org> <20170822123449.GD1700@kib.kiev.ua> <20170822124617.GN1130@albert.catwhisker.org> <20170822131958.GE1700@kib.kiev.ua> <20170822133836.GQ1130@albert.catwhisker.org> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:sCZmJXvE9YxDkxZhS4YB+cDjm7tOZAtEIoP8wOphPYtBFU05QKt ohoPx3W0CpX9ED+1DYj8xZo9ahX7mgzNVbZ+nyITFwuRfjE/F73XYzfcV186QgrrN1wSOoY TYDdF9KbNimvt5ZZDSSDSil/Ojvnw0S8wdQyRgJj9UTvNeW7Yxzav5AK4A/k9hokHcOCORm eiEXGbvnX4hut3c44TcTQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:3OPZKKRgguA=:niQmefuQYB/DyxpDLOSETi 1DtYAI6XDz8MVC60H6yICmZPGhQGCbx3Rauszcj2375eoBgJLDNHzkWeNFFLj4ZTNwfAN/fzL TcakaOcOCcOS42bIIsdaf4yn93RkiL1vRxJfYaZJWpk9GPJvLBdYnu5oHLfWFssg0oDNva28B XI7zFOAy6KBWd21zvcXdHDqr9tP68oTh2gaXry3ktUkede/O9Lr893mHUZlUcJvXs9pR+kh0G Le9vec9lRMGK+bJgumpR7egVFNBDwJhhqEVRgoP+QJUXFJw4eU+VmECsPhA8HWjxMwfjGRjBn LXUdEILJdd3WvoZJtcOlNBonQN16wh64RFrUVuZk9tCGLsqH+CAjA/v02KW97qrvvwuLNXZaI tzTK92X15xHfWaCMlvaHgkBfGVsTIUod+SNOLVCtLlt++ie75/I+sQMuflb3rFU6K5klSnEkM 9M5EjPul//iR+rPtCLfGuMwUMja3SDg18zYLYIUseSwonBf/su25TrcvIb8klOz2kG7YGIwKj bOQPjjURqj6rQW3e3zGaA2UVBUNtga1359WP+eXH0q+LDieOhOntAAisMvnANxmVS9BqWd8Qj 4fPaorgQPPvLBuenMmQwlvSGnpu1ygG4s7D15FEdH6KjG5ajjHi6qNwNsrDYapTAo5mTdcjAm hVLDcxZSoH+ZlxMfoLDv2e++qjzginfmWMLl5GDiA9ydXi9vW4F7oyWbY3w/PbzlMn1rkRQio vi5CtQpqwTntuHsrZf1UuumOnK8WXsd5M2Das+nNwtg2B8aWcKgHgLzB5pQNFghWqEvDlihSP 6i/deaIURdrB2vsjHSkDXcI0hjC4+NBZ8KKooL1O/t+lV8SZCM= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Aug 2017 18:09:13 -0000 On Tue, 22 Aug 2017 06:38:36 -0700 David Wolfskill wrote: I also ran into this problem after "upgrading" to r322769 and now I have on ALL systems, I did this "upgrade", a wrecked system which isn't even capable of compiling a new kernel or world. I can understand that something weird and havoc can happen on systems running CURRENT with customised kernels, also some hidden problems, but this serious problem occurs even on vanilla GENERIC systems up to r322798! I just tried to cleandir everything and rebuild world and kernel which is on some slow boxes a pain in the arse (and I always thought LLVM/CLANG's goal was to shorten compile cycles ... the opposite seems the fact, by the way). The arising question is with view to GENERIC: do those changes even get tested on real hardware or is it all theory/virtual when commited? Just a question. I'm awaiting this patch in the hope I can rebuild everything to normal. Thanks, oh > On Tue, Aug 22, 2017 at 04:19:58PM +0300, Konstantin Belousov wrote: > > ... > > > > Ok, can you rebuild kernel and libc from scratch ? I.e. remove > > > > your object directories. > > > > > > I think I'll need a working /bin/sh to do that. As noted, I could > > > try the stable/11 /bin/sh; on the other hand, if it's dying in a > > > library, that's not likely to help a whole lot. :-} > > I highly suspect that this is not /bin/sh at all. Backtrace > > strongly suggests that the malloc() has issues, but again I suspect > > that the reason is not an issue in malloc, but its use of TLS. > > I think I hope that this use of "TLS" is not the one associated with > (say) SSL.... :-} > > > The amd64 changes were to the TLS base register handling. So you > > might try to boot previous kernel. If this works out without > > replacing libc then it is definitely TLS, but I still do not know > > what is wrong. .... > > OK; we have a bit of progress, then: > * When I tried to rename the kernel directories in /boot, I got more > segfaults. So I figured I'd use the boot menu to select > kernel.old, and just tried "sudo shutdown -r now" -- and got a > segfault. "sudo reboot" did, as well. So did "sudo kill 1". On a > whim, I tried "sudo halt"; that actually worked. > > * After the (successful) reboot from kernel.old, I was able to rename > kernel directories without issue. This may be useflu evidence. > > * Flushed with that success, I have started a fresh clean build of > r322776. (I had managed to clear /usr/obj prior to the reboot.) > > * I should be able to provide updated status within about 30 minutes. > > Thanks again for all your help! > > Peace, > david