From owner-freebsd-ppc@freebsd.org Sun May 3 15:38:10 2020 Return-Path: Delivered-To: freebsd-ppc@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 74B8B2E05C6 for ; Sun, 3 May 2020 15:38:10 +0000 (UTC) (envelope-from nonameless@ukr.net) Received: from frv190.fwdcdn.com (frv190.fwdcdn.com [212.42.77.190]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.ukr.net", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49FVW53T4Hz3KvT for ; Sun, 3 May 2020 15:38:09 +0000 (UTC) (envelope-from nonameless@ukr.net) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-Id: References:In-Reply-To:Cc:To:Subject:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=tt42P0Zvr9+bApZvWbmXDXeXrA2RJyFe70eK+5ctp9o=; b=TFeKlFmSnuzfx5sN4ShdwhRQlR FV6a8zSPK4MCmPgnS5lw9I2butpPo1GW8pQopLG6DLCvErOd9ZelUf6trmgY9xhBAvy+V9nBwe4xV 9cEUqNZc1Lg93JqeRRGaiB2iLebjCW9E3b8WQrHpfHkgf+fgcTtViVYVcxUATlkyfGX8=; Received: from [10.10.80.23] (helo=frv55.fwdcdn.com) by frv190.fwdcdn.com with smtp ID 1jVGgr-000DWF-8K for freebsd-ppc@freebsd.org; Sun, 03 May 2020 18:38:01 +0300 Date: Sun, 03 May 2020 18:38:01 +0300 From: nonameless@ukr.net Subject: Re[2]: svn commit: r360233 - in head: contrib/jemalloc . . . : This partially breaks a 2-socket 32-bit powerpc (old PowerMac G4) based on head -r360311 To: Mark Millard Cc: svn-src-head@freebsd.org, FreeBSD Current , FreeBSD Hackers , FreeBSD PowerPC ML Received: from nonameless@ukr.net by frv55.fwdcdn.com; Sun, 03 May 2020 18:38:01 +0300 In-Reply-To: <922FBA7C-039D-4852-AC8F-E85A221C2559@yahoo.com> References: <1588493689.54538000.et1xl2l8@frv55.fwdcdn.com> <922FBA7C-039D-4852-AC8F-E85A221C2559@yahoo.com> X-Reply-Action: reply Message-Id: <1588519871.700235000.j9rwguqu@frv55.fwdcdn.com> X-Mailer: mail.ukr.net 5.0 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary X-Rspamd-Queue-Id: 49FVW53T4Hz3KvT X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ukr.net header.s=ffe header.b=TFeKlFmS; dmarc=pass (policy=none) header.from=ukr.net; spf=pass (mx1.freebsd.org: domain of nonameless@ukr.net designates 212.42.77.190 as permitted sender) smtp.mailfrom=nonameless@ukr.net X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[ukr.net:s=ffe]; IP_SCORE(0.00)[ipnet: 212.42.77.0/24(-4.88), asn: 8856(-3.91), country: UA(0.07)]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[ukr.net]; R_SPF_ALLOW(-0.20)[+ip4:212.42.77.0/24:c]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_FIVE(0.00)[5]; DWL_DNSWL_LOW(-1.00)[ukr.net.dwl.dnswl.org : 127.0.5.1]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[ukr.net:+]; DMARC_POLICY_ALLOW(-0.50)[ukr.net,none]; FROM_NO_DN(0.00)[]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[ukr.net]; ASN(0.00)[asn:8856, ipnet:212.42.77.0/24, country:UA]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 May 2020 15:38:10 -0000 --- Original message --- From: "Mark Millard"  Date: 3 May 2020, 17:38:14 > > > On 2020-May-3, at 01:26, nonameless at ukr.net wrote: > > > > > > --- Original message --- > > From: "Mark Millard" > > Date: 3 May 2020, 04:47:14 > > > > > > > >> [I'm only claiming the new jemalloc is involved and that > >> reverting avoids the problem.] > >> > >> I've been reporting to some lists problems with: > >> > >> dhclient > >> sendmail > >> rpcbind > >> mountd > >> nfsd > >> > >> getting SIGSEGV (signal 11) crashes and some core > >> dumps on the old 2-socket (1 core per socket) 32-bit > >> PowerMac G4 running head -r360311">360311. > >> > >> Mikaël Urankar sent a note suggesting that I try > >> testing reverting head -r360233">360233 for my head -r360311">360311 > >> context. He got it right . . . > >> > >> > >> Context: > >> > >> The problem was noticed by an inability to have > >> other machines do a: > >> > >> mount -onoatime,soft OLDPOWERMAC-LOCAL-IP:/... /mnt > >> > >> sort of operation and to have succeed. By contrast, on > >> the old PowerMac G4 I could initiate mounts against > >> other machines just fine. > >> > >> I do not see any such problems on any of (all based > >> on head -r360311): > >> > >> powerpc64 (old PowerMac G5 2-sockets with 2 cores each) > >> armv7 (OrangePi+ 2ed) > >> aarch64 (Rock64, RPi4, RPi3, > >> OverDrive 1000">1000, > >> Macchiatobin Double Shot) > >> amd64 (ThreadRipper 1950X) > >> > >> So I expect something 32-bit powerpc specific > >> is somehow involved, even if jemalloc is only > >> using whatever it is. > >> > >> (A kyua run with a debug kernel did not find other > >> unexpected signal 11 sources on the 32-bit PowerMac > >> compared to past kyua runs, at least that I noticed. > >> There were a few lock order reversals that I do not > >> know if they are expected or known-safe or not. > >> I've reported those reversals to the lists as well.) > >> > >> > >> Recent experiments based on the suggestion: > >> > >> Doing the buildworld, buildkernel and installing just > >> the new kernel and rebooting made no difference. > >> > >> But then installing the new world and rebooting did > >> make things work again: I no longer get core files > >> for the likes of (old cores from before the update): > >> > >> # find / -name "*.core" -print > >> /var/spool/clientmqueue/sendmail.core > >> /rpcbind.core > >> /mountd.core > >> /nfsd.core > >> > >> Nor do I see the various notices for sendmail > >> signal 11's that did not leave behind a core file > >> --or for dhclient (no core file left behind). > >> And I can mount the old PowerMac's drive from > >> other machines just fine. > >> > >> > >> Other notes: > >> > >> I do not actively use sendmail but it was left > >> to do its default things, partially to test if > >> such default things are working. Unfortunately, > >> PowerMacs have a problematical status under > >> FreeBSD and my context has my historical > >> experiments with avoiding various problems. > >> > >> === > >> Mark Millard > >> marklmi at yahoo.com > >> ( dsl-only.net went > >> away in early 2018">2018-Mar) > >> > > > > Hi Mark, > > > > It should be fixed, but not by reverting to old version. We can't stuck on old version because of ancient hardware. I think upstream is not interested in support such hardware. So, it have to patched locally. > > Observing and reporting the reverting result is an initial > part of problem isolation. I made no request for FreeBSD > to give up on using the updated jemalloc. (Unfortunately, > I'm not sure what a good next step of problem isolation > might be for the dual-socket PowerMac G4 context.) > > Other than reverting, no patch is known for the issue at > this point. More problem isolation is needed first. > > While I do not have access, https://wiki.freebsd.org/powerpc > lists more modern 32-bit powerpc hardware as supported: > MPC85XX evaluation boards and AmigaOne A1222 (powerpcspe). > (The AmigaOne A1222 seems to be dual-ore/single-socket.) > > So folks with access to one of those may want to see > if they also see the problem(s) with head -r360233 or > later. > > Another interesting context to test could be single-socket > with just one core. (I might be able to do that on another > old PowerMac, booting the same media after moving the > media.) > > If I understand right, the most common 32-bit powerpc > tier 2 hardware platforms may still be old PowerMac's. > They are considered supported and "mature", instead of > just "stable". See https://wiki.freebsd.org/powerpc . > However, the reality is that there are various problems > for old PowerMacs (32-bit and 64-bit, at least when > there is more than one socket present). The wiki page > does not hint at such. (I'm not sure about > single socket/multi-core PowerMacs: no access to > such.) > > It is certainly possible for some problem to happen > that would lead to dropping the supported-status > for some or all old 32-bit PowerMacs, even as tier 2. > But that has not happened yet and I'd have no say in > such a choice. > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > Just don't want to see again previous situation when jemalloc was committed, then reverted and was forgotten for six months.