From owner-freebsd-arm@freebsd.org Sun May 24 15:11:32 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 5951C2C8437 for ; Sun, 24 May 2020 15:11:32 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49VNwg3lmCz4B1H for ; Sun, 24 May 2020 15:11:31 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Sun, 24 May 2020 15:11:24 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1590333088; bh=5RxXBlwv22xPlUe+tpwqPeyBmw87tw9cMJAYKsDaVKE=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=SE6wxmUTIqa8sreZxEv8IKGx1uHBc1ieUhDz2H59puWL4me28XmALQOOA79JSo89G /FVDk2Hg4HXg3athIUpo4hy+6QoNi5SDTgg6oUBoHX9IRL3dIwVBz7IUUMbLRs5ZVf 2S966DAJBVHE+KatYrj70ZyQq9gFlkixEpreUM+s= To: "greg@unrelenting.technology" From: Dan Kotowski Cc: Warner Losh , freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: <664db38a87ea8803be72af9738534994@unrelenting.technology> References: <3e81db774e0fc1a3c2251c89b7629e1b@unrelenting.technology> <86119565e5927716a9feebabcb611871@unrelenting.technology> <37858865a8ebddd3fe1e3a228a19ef62@unrelenting.technology> <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> <664db38a87ea8803be72af9738534994@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49VNwg3lmCz4B1H X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=SE6wxmUT; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.22 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-3.83 / 15.00]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.987]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.22:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-0.68)[-0.683]; NEURAL_HAM_MEDIUM(-1.06)[-1.061]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.22:from] 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 15:11:32 -0000 > > I also looked more closely at mps, and actually "just polling I/O" does= work. We see: > > mps0: IOCCapabilities: 1285c > > and that means mps_request_sync (called by mps_get_iocfacts) has worked= . > > And the command completion actually seems to come from interrupts. > > I've heard something about MSI(X) not working for the Linux people (not= NetBSD though!), > > so I guess the next thing to try would be booting with hw.pci.enable_ms= i=3D0 hw.pci.enable_msi=3D1 > > lol, I mean, hw.pci.enable_msi=3D0 hw.pci.enable_msix=3D0 Still roughly the same: https://gist.github.com/agrajag9/9cb79fe1e53dd6e8f7= dc09fe5f6236e9 And NVMe still panics during boot, so pulled that at least for now.