Date: Wed, 20 Jan 2021 13:12:25 +0000 From: Rafal Lukawiecki <raf@rafal.net> To: Colin Percival <cperciva@tarsnap.com> Cc: freebsd-cloud@freebsd.org Subject: Re: FreeBSD on AWS Graviton (t4g) Message-ID: <30C35A29-17E2-481D-A335-5B1FBB9FB22C@rafal.net> In-Reply-To: <C4D2ACA9-BFFE-49C1-B8AA-72E32C9DB6C9@rafal.net> References: <01000176816d1718-26a08928-e08c-466a-8550-552bc746d81f-000000@email.amazonses.com> <C4D2ACA9-BFFE-49C1-B8AA-72E32C9DB6C9@rafal.net>
index | next in thread | previous in thread | raw e-mail
Colin, I am only slowly realising the impact of the points you have made. :) >> On 20 Dec 2020, at 18:33, Colin Percival <cperciva@tarsnap.com> wrote: >> >> * The EC2 API "shutdown" / "reboot" message is sent via a pl061 GPIO device >> and we're dropping it on the floor; consequently "reboot" does nothing at >> all, while "shutdown" does nothing until EC2 times out and does a hard >> poweroff (without filesystems being unmounted etc). I have noticed a bunch of artefacts left over from unclean shutdowns, which I assume are caused by the above not calling the shutdown rc.d scripts. Do you know if this is likely to get implemented any time soon, or are you aware of a simple workaround? I have to say that in general I am finding FreeBSD 12.2 on t4g pretty good and surprisingly stable. The CPU utilisation is different in terms of metrics, and I cannot quite put my finger on it, but the web apps seem to run faster. Of course, it is nice that it is also cheaper. Thanks, Rafal -- Rafal Lukawiecki Data Scientist Project Botticelli Ltdhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?30C35A29-17E2-481D-A335-5B1FBB9FB22C>