From owner-freebsd-arm@freebsd.org Sun May 24 17:52:05 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 8648A2CCA25 for ; Sun, 24 May 2020 17:52:05 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (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 49VSTw4rGxz4P2B for ; Sun, 24 May 2020 17:52:04 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Sun, 24 May 2020 17:51:59 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1590342721; bh=6f3Msvo05JDprYohAL8FF1/as0o5OfIsq5m74MBkRZg=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=qAMT99GIwcrTvCr41IJAE94/rl7fBHituel0PoVRp21fk6+mAtYrQrbQRIKIp9/fY KDQw0VPJTo2THW8Wgois6gP2iA042oL3jz5ZncOwDILKzFl07SsaaZFD9NGRzaqYnq vnji+Ov4MpYYG71BmjnaQaKoW9UFax2Y5BX5fhKg= To: "greg@unrelenting.technology" From: Dan Kotowski Cc: freebsd-arm Reply-To: Dan Kotowski Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: In-Reply-To: References: <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: 49VSTw4rGxz4P2B X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=qAMT99GI; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.131 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-4.03 / 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)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-0.99)[-0.988]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; NEURAL_HAM_SHORT(-0.95)[-0.953]; NEURAL_HAM_MEDIUM(-0.99)[-0.986]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[185.70.40.131:from]; 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.131: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 17:52:05 -0000 > > > I also looked more closely at mps, and actually "just polling I/O" do= es work. We see: > > > mps0: IOCCapabilities: 1285c > > > and that means mps_request_sync (called by mps_get_iocfacts) has work= ed. > > > And the command completion actually seems to come from interrupts. > > > I've heard something about MSI(X) not working for the Linux people (n= ot NetBSD though!), > > > so I guess the next thing to try would be booting with hw.pci.enable_= msi=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/9cb79fe1e53dd6= e8f7dc09fe5f6236e9 > > And NVMe still panics during boot, so pulled that at least for now. > > I wonder if PCIe devices are just not getting interrupts and if that's re= lated to AHCI not being able to configure interrupts. > > Added some debug logging for interrupts: > > https://send.firefox.com/download/828468ac751f8f69/#P1xKgL6IIqFOD-JBQFHnA= w > > (test with mps, don't disable msi I guess since it didn't help) > > Also, to rule out firmware bugs, would be good to test Linux and NetBSD w= ith the same firmware. > (with NVMe, it's something that would definitely get attempted at boot) > > NetBSD -CURRENT: http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/ima= ges/NetBSD-9.99.63-evbarm-aarch64.iso > They don't have memstick images for arm, unfortunately -- idk whether dd'= ing an iso image to a usb drive > would boot, probably not, try tools like rufus maybe. > Or assemble your own memstick with what I assume is just the root filesys= tem image: > http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/evbarm-aarch64/binar= y/gzimg/arm64.img.gz > plus the boot loader you'd have to place on the EFI partition manually > http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/evbarm-aarch64/insta= llation/misc/bootaa64.efi https://gist.github.com/agrajag9/2e07426702d46aa086348b70be942397 Flashing NetBSD to a new card now...