Date: Tue, 18 Jun 2024 22:48:23 +0200 From: JMT Sihvola <jsihv@gmx.com> To: John F Carr <jfc@mit.edu> Cc: "freebsd-riscv@freebsd.org" <freebsd-riscv@freebsd.org> Subject: Re: JH7110 dwc MAC support Message-ID: <trinity-87ca3865-8675-4ccb-8a41-71416175c902-1718743703530@3c-app-mailcom-bs16> In-Reply-To: <00D2F480-7703-4DE5-BC80-9E69D3B4E4D0@mit.edu> References: <7E28ED97-DD4B-40AA-91FB-DB3982042265@mit.edu> <trinity-e7a78d45-28c3-4905-9504-37475fb12770-1718379639909@3c-app-mailcom-bs01> <AA50117A-8C29-4FD2-BCFD-FBC87ECC57CC@mit.edu> <trinity-2bf96660-359f-49f1-967e-da3cfea8e00c-1718395200970@3c-app-mailcom-bs13> <00D2F480-7703-4DE5-BC80-9E69D3B4E4D0@mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
John F Carr wrote: > All is forgiven. Almost all. The main problem was the failure of the k= ernel to > set up network configuration to mount / over NFS. With root on a memory > disk (load -t md_image) I can use ifconfig to set up the interface. > It at least passes a smoke test, reading files over NFS. > > However, the driver has offended WITNESS by trying to hold "eqos lock" > and "Clock topology lock" at the same time. Nice to hear that you got forward. There's now a review process in which that lock order reversal is mentione= d. https://reviews.freebsd.org/D45600 (No matter what I wrote there that LOR may not be linked to softclock after all) Jari S.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?trinity-87ca3865-8675-4ccb-8a41-71416175c902-1718743703530>