Date: Sun, 12 Sep 2021 21:27:55 -0700 From: bob prohaska <fbsd@www.zefox.net> To: bob prohaska <fbsd@www.zefox.net> Cc: Free BSD <freebsd-arm@freebsd.org> Subject: Re: Python2.7 seemingly stuck on RPI3 Message-ID: <20210913042755.GA74280@www.zefox.net> In-Reply-To: <B57CC732-C87C-4779-895F-CC8412D11236@yahoo.com> References: <B57CC732-C87C-4779-895F-CC8412D11236.ref@yahoo.com> <B57CC732-C87C-4779-895F-CC8412D11236@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 11, 2021 at 07:37:32PM -0700, Mark Millard wrote: > > >From what is presented, I'd guess that da0s2b is on spinning rust. Correct. > My expectation is that da0 is spending much of its time > seeking and the system does not have much to do during the > seek activity. So the sum of the latencies is adding significant > time for any given amount of progress. > The system (running -current) was last compiled in mid-July, so I decided to update world and kernel. To my surprise, it got stuck in a similar way. Eventually I enabled an absurd excess of swap, 3.5 Gb on each of da0s2b and mmcsd0s2b, and buildworld seems to be making good progress. I'll post a note if anything interesting happens. Thanks for writing! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210913042755.GA74280>