Date: Mon, 4 Feb 2019 15:23:16 -0500 From: Ed Maste <emaste@freebsd.org> To: "Jayachandran C." <jchandra@freebsd.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: ThunderX2 support in FreeBSD/arm64 Message-ID: <CAPyFy2D8oqg%2BAH=VCj0G==WZzMAoncVi8MmO_v1oCM4mpHXucw@mail.gmail.com> In-Reply-To: <CA%2B7sy7CGqEPpZ5LMcB7iy-m=hOiH6waauO9GPESicJc=kTnGMg@mail.gmail.com> References: <CA%2B7sy7BWtSi5uDgusf-sEHd06EGXwnUxo9cr8A9gLh1L_YJoXw@mail.gmail.com> <CAPyFy2DXHvAudezY9TUjnADO4FAbeKthxGyEOvow89iXmXa9ig@mail.gmail.com> <CA%2B7sy7CGqEPpZ5LMcB7iy-m=hOiH6waauO9GPESicJc=kTnGMg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 3 Jan 2019 at 15:52, Jayachandran C. <jchandra@freebsd.org> wrote: > > There seems to be 2 issues here - both of them happen when the AMI > firmware is used. > The first issue is that the efi framebuffer does not work, and I am > not able to select the serial console with AMI firmware. The second > issue is that the on-chip SATA controller is not setup correctly by > the AMI firmware and can cause a 'NBU BAR error' failure. > > I have uploaded a test firmware and instructions to > https://people.freebsd.org/~jchandra/testfw/ which should boot FreeBSD > fine. This is an internal build which does not have both the problems > above. Let me know if this works, and I will try to push the fixes to > AMI. Thanks, with the test firmware I'm able to make progress and the kernel boots fine. It's now hanging while trying to mount root over NFS; final console output is: Trying to mount root from nfs:10.0.0.1:/tank/export-root/arm64/ [rw]... taskqgroup_attach_cpu_deferred: setaffinity failed: 3
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2D8oqg%2BAH=VCj0G==WZzMAoncVi8MmO_v1oCM4mpHXucw>