From owner-freebsd-arm@freebsd.org Fri Apr 5 14:15:25 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3E7E15782FD for ; Fri, 5 Apr 2019 14:15:24 +0000 (UTC) (envelope-from marcel@brickporch.com) Received: from mail.brickporch.com (mail.brickporch.com [52.33.181.202]) by mx1.freebsd.org (Postfix) with ESMTP id 8E35B933BF; Fri, 5 Apr 2019 14:15:23 +0000 (UTC) (envelope-from marcel@brickporch.com) Received: from twill.home.brickporch.com (unknown [69.84.7.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.brickporch.com (Postfix) with ESMTPSA id 31472108B05; Fri, 5 Apr 2019 14:15:57 +0000 (UTC) From: Marcel Flores Message-Id: Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: Restore broken ThunderX support in 12 by MFCing r343764? Date: Fri, 5 Apr 2019 07:15:14 -0700 In-Reply-To: <3996B352-ABFB-4CA5-A897-6C6CD1D2A132@brickporch.com> To: freebsd-arm@freebsd.org References: <20190218022911.72261m7v5l6g1i7b@webmail.omc.net> <3996B352-ABFB-4CA5-A897-6C6CD1D2A132@brickporch.com> X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: 8E35B933BF X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of marcel@brickporch.com designates 52.33.181.202 as permitted sender) smtp.mailfrom=marcel@brickporch.com X-Spamd-Result: default: False [-0.29 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.982,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MIME_TRACE(0.00)[0:+,1:+]; DMARC_NA(0.00)[brickporch.com]; URI_COUNT_ODD(1.00)[11]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; IP_SCORE(-0.59)[ipnet: 52.32.0.0/14(-1.58), asn: 16509(-1.32), country: US(-0.06)]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MX_GOOD(-0.01)[mail.brickporch.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.01)[-0.013,0]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:16509, ipnet:52.32.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Apr 2019 14:15:25 -0000 > On Apr 3, 2019, at 10:16 PM, Marcel Flores = wrote: >=20 >=20 >=20 >> On Apr 3, 2019, at 6:55 AM, Ed Maste wrote: >>=20 >> On Sun, 17 Feb 2019 at 20:29, wrote: >>>=20 >>> Not being a developer though, I cannot judge if [r343764] cannot be = MFC'd >>> into 12-STABLE due to making invasive changes or if it simply never >>> was because it was thought to be an improvement for 13 only and not = an >>> actually pretty vital fix for 12. >>=20 >> I suspect jchandra@ just didn't realize it's needed also on ThunderX, >> and I did not encounter any trouble with the ThunderX systems I have. >> It could just be that our (older) ThunderX reference firmware has >> fewer regions in its ACPI info and so works fine without r343764. >> Anyhow I've now merged the change to stable/12. >>=20 >> With respect to vt_efifb the tunable is a simple workaround, but we >> really need this to work out-of-the-box. Do you have any further >> details on the failure when vt_efifb is enabled? >>=20 >> Also, if you're aware of any other ThunderX issues please let me = know.] >=20 > stable/12 now works. In fact, the hw.syscons.disable tuneable is no = longer needed either =E2=80=94 a fresh build stable/12 appears to be = working with GENERIC out of the box. Based on this thread, that = doesn=E2=80=99t totally make sense to me, but I=E2=80=99m not sure what = all else has made it into stable/12. >=20 > The same can=E2=80=99t be said for 13, which, as of about 2 weeks ago = (I can confirm later this week if that would be worthwhile), behaves as = described here without it: > = https://lists.freebsd.org/pipermail/freebsd-arm/2018-December/019130.html = > >=20 > Since the serial console essentially hangs, I=E2=80=99m not sure how = to get any additional information, but happy to try any suggestions. >=20 >=20 > The only other issues I=E2=80=99ve had with the ThunderX Gigabyte = board I have is getting the onboard NIC to work (Seems to be about like = this, looking at dmesg: = https://lists.freebsd.org/pipermail/freebsd-arm/2018-April/017865.html = ),= but I imagine this is a driver question for the Gigabyte portions, = rather than an issue with the ThunderX itself. >=20 Correction to the above =E2=80=94 just tried to boot current/13 r345863 = via USB installer, it actually gets further, sans tuneable, but gets stuck = somewhere.=20 Boot output attached. https://hastebin.com/xeteyuhome -m