From owner-freebsd-current@freebsd.org Mon Jan 27 02:25:15 2020 Return-Path: Delivered-To: freebsd-current@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 A1CF522C870 for ; Mon, 27 Jan 2020 02:25:15 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.oetec.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 485YVy2Nphz3HLc for ; Mon, 27 Jan 2020 02:25:13 +0000 (UTC) (envelope-from dclarke@blastwave.org) X-Spam-Status: No X-oetec-MailScanner-From: dclarke@blastwave.org X-oetec-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1.199, required 6, autolearn=not spam, ALL_TRUSTED -1.00, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, DKIM_VALID_EF -0.10, URIBL_BLOCKED 0.00) X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-ID: 00R2P1gD000951 X-oetec-MailScanner-Information: Please contact oetec for more information Received: from [172.16.35.3] (CPEf81d0f84cb23-CMf81d0f84cb20.cpe.net.cable.rogers.com [99.253.169.68]) (authenticated bits=0) by mail.oetec.com (8.15.2/8.15.2/Debian-8) with ESMTPSA id 00R2P1gD000951 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sun, 26 Jan 2020 21:25:02 -0500 Subject: Re: r356776 breaks kernel for powerpc64 users To: freebsd-current@freebsd.org References: <2EEA029D-2C24-42F2-A347-69813B928BC4.ref@yahoo.com> <2EEA029D-2C24-42F2-A347-69813B928BC4@yahoo.com> From: Dennis Clarke Message-ID: <6f8b8c41-b712-ccb0-1655-0a2e1cfc8bf7@blastwave.org> Date: Sun, 26 Jan 2020 21:25:01 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Thunderbird/72.0 MIME-Version: 1.0 In-Reply-To: <2EEA029D-2C24-42F2-A347-69813B928BC4@yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 485YVy2Nphz3HLc X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.17 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; NEURAL_HAM_MEDIUM(-0.75)[-0.755,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.94)[-0.938,0]; IP_SCORE(0.52)[asn: 812(2.68), country: CA(-0.09)]; DKIM_TRACE(0.00)[blastwave.org:+]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; RECEIVED_SPAMHAUS_PBL(0.00)[68.169.253.99.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 27 Jan 2020 02:25:15 -0000 On 2020-01-26 19:27, Mark Millard wrote: > Piotr Kubaj listy at anongoth.pl wrote on > Thu Jan 16 19:56:11 UTC 2020 : > >> revision 356776 breaks booting for powerpc64 users. It reportedly works fine on POWER8, but I get kernel panic on POWER9 (Talos II) right after the usual warning: WITNESS enabled. Kernel panic is uploaded to https://pastebin.com/s8ZaUNS2. >> >> >> @jeff >> Since you commited this patch, can you fix this issue or revert this commit? >> > > Is this still a problem for powerpc64? I've not seen > anything looking like a direct response or like a > status update for this. > > I do see arm report(s) of problems that they also > attributed to head -r356776 . But I've no clue how > good the evidence is generally. An example message > is: > > https://lists.freebsd.org/pipermail/freebsd-arm/2020-January/021069.html > > But one part of that is for specifically for going > from -r356767 to the next check-in to head: -r356776 . > That problem likely has good evidence for the > attribution to -r356776 . > I will give current a try and report back. However I am hesitant to do so as I have a working G5 right now. For science ... I will do the experiment. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional