Date: Wed, 20 Jan 2021 13:21:27 +0000 From: Rafal Lukawiecki <raf@rafal.net> To: Rafal Lukawiecki <raf@rafal.net> Cc: Colin Percival <cperciva@tarsnap.com>, freebsd-cloud@freebsd.org Subject: Re: FreeBSD on AWS Graviton (t4g) Message-ID: <430D4E7C-7D3A-4A86-ADC2-D323F8C3FDB3@rafal.net> In-Reply-To: <30C35A29-17E2-481D-A335-5B1FBB9FB22C@rafal.net> References: <01000176816d1718-26a08928-e08c-466a-8550-552bc746d81f-000000@email.amazonses.com> <C4D2ACA9-BFFE-49C1-B8AA-72E32C9DB6C9@rafal.net> <30C35A29-17E2-481D-A335-5B1FBB9FB22C@rafal.net>
index | next in thread | previous in thread | raw e-mail
> On 20 Jan 2021, at 13:12, Rafal Lukawiecki via freebsd-cloud <freebsd-cloud@freebsd.org> wrote: > > 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? Ah, I just noticed a commit from Sept 2020 https://github.com/freebsd/freebsd-src/commit/1fc1a22868264f3a59074fe90cb2ac39309d63d5 <https://github.com/freebsd/freebsd-src/commit/1fc1a22868264f3a59074fe90cb2ac39309d63d5>; that mentions pl061 use on EC2. I suppose that is likely to end up in 13.0, am I right? Perhaps there is more work that needs to happen before this leads to a shutdown and in turn rc.d running scripts. Rafal -- Rafal Lukawiecki Data Scientist Project Botticelli Ltdhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?430D4E7C-7D3A-4A86-ADC2-D323F8C3FDB3>