From owner-freebsd-arm@freebsd.org Sun May 24 16:46:29 2020 Return-Path: Delivered-To: freebsd-arm@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 8E1B92CA94C for ; Sun, 24 May 2020 16:46:29 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out0.migadu.com (out0.migadu.com [IPv6:2001:41d0:2:267::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49VR2C4Nvbz4J8T for ; Sun, 24 May 2020 16:46:27 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1590338785; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=f+76Ff4a4IFDNUOZCbsj0jJAgs/dcYpmGWSn60V8dJY=; b=YBXkIJVd67cAqX8jRHIwCvSWRBGsxsXlc7GeNrECMH0YEj/dRHvRu2PtK+ICkqNozbVBuA zPo+xnJSGK/BbDbaqJVv3/OA6N7po3HW7OfzbinPeMT9Tl34yr+LvAn38QJ1bLCnwmLuaV 38iUKUgtt8wlf9VJPOcbVqUJ1uVk50w= Date: Sun, 24 May 2020 16:46:23 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: "Dan Kotowski" Cc: "freebsd-arm" In-Reply-To: References: <3e81db774e0fc1a3c2251c89b7629e1b@unrelenting.technology> <86119565e5927716a9feebabcb611871@unrelenting.technology> <37858865a8ebddd3fe1e3a228a19ef62@unrelenting.technology> <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> <664db38a87ea8803be72af9738534994@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49VR2C4Nvbz4J8T X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=YBXkIJVd; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:267:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.82 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.06)[-1.058]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:267::]; NEURAL_HAM_LONG(-0.97)[-0.974]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-0.79)[-0.791]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2020 16:46:29 -0000 May 24, 2020 6:11 PM, "Dan Kotowski" wro= te:=0A=0A>> I also looked more closely at mps, and actually "just polling= I/O" does work. We see:=0A>> mps0: IOCCapabilities: 1285c=0A>> and that mean= s mps_request_sync (called by mps_get_iocfacts) has worked.=0A>> And the = command completion actually seems to come from interrupts.=0A>> I've hear= d something about MSI(X) not working for the Linux people (not NetBSD tho= ugh!),=0A>> so I guess the next thing to try would be booting with hw.pci= .enable_msi=3D0 hw.pci.enable_msi=3D1=0A>> =0A>> lol, I mean, hw.pci.enab= le_msi=3D0 hw.pci.enable_msix=3D0=0A> =0A> Still roughly the same: https:= //gist.github.com/agrajag9/9cb79fe1e53dd6e8f7dc09fe5f6236e9=0A> =0A> And = NVMe still panics during boot, so pulled that at least for now.=0A=0AI wo= nder if PCIe devices are just not getting interrupts and if that's relate= d to AHCI not being able to configure interrupts.=0A=0AAdded some debug l= ogging for interrupts:=0A=0Ahttps://send.firefox.com/download/828468ac751= f8f69/#P1xKgL6IIqFOD-JBQFHnAw=0A=0A(test with mps, don't disable msi I gu= ess since it didn't help)=0A=0AAlso, to rule out firmware bugs, would be = good to test Linux and NetBSD with the same firmware.=0A(with NVMe, it's = something that would definitely get attempted at boot)=0A=0ANetBSD -CURRE= NT: http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/images/NetBSD-9.= 99.63-evbarm-aarch64.iso=0AThey don't have memstick images for arm, unfor= tunately -- idk whether dd'ing an iso image to a usb drive=0Awould boot, = probably not, try tools like rufus maybe.=0AOr assemble your own memstick= with what I assume is just the root filesystem image:=0Ahttp://nycdn.net= bsd.org/pub/NetBSD-daily/HEAD/latest/evbarm-aarch64/binary/gzimg/arm64.im= g.gz=0Aplus the boot loader you'd have to place on the EFI partition manu= ally=0Ahttp://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/evbarm-aarch6= 4/installation/misc/bootaa64.efi