From nobody Mon Aug 23 14:56:46 2021 X-Original-To: freebsd-ppc@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9CFEF17741F0 for ; Mon, 23 Aug 2021 14:57:03 +0000 (UTC) (envelope-from alfredo@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Gtb1W424Sz4lPK for ; Mon, 23 Aug 2021 14:57:03 +0000 (UTC) (envelope-from alfredo@freebsd.org) Received: from mail-pg1-f176.google.com (mail-pg1-f176.google.com [209.85.215.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: alfredo) by smtp.freebsd.org (Postfix) with ESMTPSA id 669A2E905 for ; Mon, 23 Aug 2021 14:57:03 +0000 (UTC) (envelope-from alfredo@freebsd.org) Received: by mail-pg1-f176.google.com with SMTP id e7so16889625pgk.2 for ; Mon, 23 Aug 2021 07:57:03 -0700 (PDT) X-Gm-Message-State: AOAM5328FarAkCEV798IYr1b/zFI5jmRYGkHFNR7MvyqMaw9jMkQxuXM FczQiMhmPnQg1I1uDHZyJLa+I9BvCojqCJkmZQw= X-Google-Smtp-Source: ABdhPJwreT8dbRQ0MKbZdaxxe1CZq8uwv5aBpKLPrwTRI32/4W2hlV5fqKArtdP+I6g8vltjTP5/Zoiynv8idE4q0dY= X-Received: by 2002:a05:6a00:2d6:b0:3e2:e023:c6cd with SMTP id b22-20020a056a0002d600b003e2e023c6cdmr28835646pft.19.1629730622277; Mon, 23 Aug 2021 07:57:02 -0700 (PDT) List-Id: Porting FreeBSD to the PowerPC List-Archive: https://lists.freebsd.org/archives/freebsd-ppc List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Alfredo_Dal=27Ava_J=C3=BAnior?= Date: Mon, 23 Aug 2021 11:56:46 -0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Segfaults everywhere on stable/13 after recent upgrade To: Julio Merino Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset="UTF-8" X-ThisMailContainsUnwantedMimeParts: N Hi Julio, Sorry for the trouble. The problem was caused by some kind of regression introduced by LLVM12. The root cause is not well determined and the PPC team is working on simplifying the test case. There's a workaround being discussed here: https://reviews.freebsd.org/D31646. Thanks, Alfredo On Sun, Aug 15, 2021 at 3:28 PM Julio Merino wrote: > > Hi all, > > I have a G5 running stable/13. A couple of weeks ago, I did the regular > fetch, rebuild world, and reinstall... and almost all new userland binaries > started crashing.I thought the crashes would be due to a kernel/userland > incompatibility, but after rebooting with the new kernel, the problem > persisted. > > It took me some effort to recover the machine into a usable state. I had to > revert the source tree to right before clang was updated to 12.0.1 on June > 13th, as I think this is the problematic change, and rebuild + reinstall > from there. > > I just updated the tree again to the most recent stable/13, done another > buildworld, and I have confirmed that most binaries are still broken in the > same way: > > root@g5:/usr/obj/usr/src/powerpc.powerpc64 # ./bin/echo/echo > Segmentation fault (core dumped) > root@g5:/usr/obj/usr/src/powerpc.powerpc64 # gdb ./bin/echo/echo > ... > Reading symbols from ./bin/echo/echo... > Reading symbols from > /usr/obj/usr/src/powerpc.powerpc64/bin/echo/echo.debug... > (gdb) run > Starting program: /usr/obj/usr/src/powerpc.powerpc64/bin/echo/echo > > Program received signal SIGSEGV, Segmentation fault. > 0x0000000010011058 in main (argc=1, argv=0xfffffbfffeab8) at > /usr/src/bin/echo/echo.c:77 > 77 { > (gdb) > > The stacktraces I get out of the binaries are meaningless. You can see echo > crashing upon entering main. ls crashes on a local variable assignment. But > cp gets further along and is able to print its own usage message before > crashing. > > Anybody knows what might be going on? > > Thanks! > > -- > jmmv.dev