Date: Mon, 25 May 2020 03:22:52 +0000 From: Dan Kotowski <dan.kotowski@a9development.com> To: "greg@unrelenting.technology" <greg@unrelenting.technology> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <YiC-gGTtYsFIsTF2yu50rV2tnPhzc5GdfbpnvBBXFm9Nqxi03FfRf38uXTUwUddwwXyK4s3PUpPQqO2xuORPLkiSBiMYC8I9JwxfUZSanoM=@a9development.com> In-Reply-To: <426b58bbea73305c52732e023ca2163c@unrelenting.technology> References: <PU1LOeii6s2eANBCYcXjsjv1XBLzoJxkbcciN4pIsjWI1B9ENZWSOGIGIYCvWtzg7YSvWnYoVL2CBjf-gBorqo3ju85HYX8YVVZk2a6j6w0=@a9development.com> <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> <xoiJF1ZUP3-rgbxC8ZmJGQNpsJSyK4zsAXhbLl8Ml96Da1lBPGwPqn0ANf7q-GgthPAWePSR9QDCM5vKysd_3e2aGtp-0egUXu6AW3bhLDg=@a9development.com> <CANCZdfqbd_u35toFYKr4LKkCBwnRhutM5knjnVcGR018Jfo1Vw@mail.gmail.com> <664db38a87ea8803be72af9738534994@unrelenting.technology> <b5105ce888b7a91eff50ec9118a910a8@unrelenting.technology> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <426b58bbea73305c52732e023ca2163c@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Booted with NetBSD -current > > > What was the panic? How about with the NVMe drive? > > (is your mail client eating quote levels sometimes? these shouldn't be bo= th >>) > > > > I've sent a link to a known firmware build before: > > > https://drive.google.com/file/d/1yXSS1O1U8CmtwaIPfxNDkzhAClJGvErK/vie= w > > > Have you tried it? Any difference in FreeBSD/NetBSD, with NVMe? > > > > Okay, lots of stuff here... > > https://gist.github.com/agrajag9/7a1164387994cecea50170e2d93e257e > > > > 1. The latest build didn't get far at all, no matter what hardware com= bo I threw at it. Something > > about the GIC... > > > > Sorry, silly error (missed {}) when inserting debug prints all over the p= lace. > > Could've tried the previous build with that firmware already ;) but new b= uild, should be fixed: > > https://send.firefox.com/download/8b82b78a44456587/#KVNvzEyBbiZJkJdhiPfbD= g https://gist.github.com/agrajag9/37e7dddeef75eb9af66856e5b75c1c12 Back to panicking at NVMe. I tried the 2 other firmware images you provided, but no luck with either. = I didn't see any noticible differences in dmesg.out, but I did notice that = the 2 linked emitted a lot of DPAAC errors during boot and the CPU fan ran = at 100% the whole time the system was one (typically it only runs at 100% f= or a second before dialing back). > > 2. NetBSD was... non-deterministic? The first time I tried booting it = died real quick: > > > > But it sees the NVMe stick AND both the root sd card and the firmware s= d card! And I was able to at > > least read their geometries with fdisk! Progress! > > Okay so first of all: > > does NetBSD's ability to work with NVMe change when you swap firmware bet= ween your build and the linked one? > > (repeat the experiment a couple times, we're doing Science here :D) NVMe worked fine with all 3 firmwares - mine and the 2 linked. > UEFI supports MBR, generally (there is an MBR partition type). > Actually the current FreeBSD/aarch64 images on Amazon EC2 are MBR (for no= good reason lol) > > And Linux kernels often have the EFISTUB option on, which means you can d= irectly run the kernel as an EFI binary.. > though an "LSDK" build might've turned that off. Also I'm not sure how th= at works with the initramfs stuff that linux distros use. TIL :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YiC-gGTtYsFIsTF2yu50rV2tnPhzc5GdfbpnvBBXFm9Nqxi03FfRf38uXTUwUddwwXyK4s3PUpPQqO2xuORPLkiSBiMYC8I9JwxfUZSanoM=>