Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Jan 2019 21:39:59 +0300
From:      Greg V <greg@unrelenting.technology>
To:        Martin Karrer <martin@bmalum.com>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: ARM Graviton AWS Processor (AMI Image)
Message-ID:  <1548182399.2864.0@smtp.migadu.com>
In-Reply-To: <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazo nses.com>
References:  <79CC79B9-81AF-4563-BABE-429E6A57F476@bmalum.com> <010201686fe5047f-ed14af85-2b25-4480-a62a-a893f062eedd-000000@eu-west-1.amazonses.com>

index | next in thread | previous in thread | raw e-mail



On Mon, Jan 21, 2019 at 1:11 PM, Martin Karrer <martin@bmalum.com> 
wrote:
> Hello,
> This is my first message on the mailing list, please forgive me for 
> making mistakes 😉
> 
> My question is if there are any plans yet to support the Graviton ARM 
> instances of AWS?
> 
> We have a heavy load on FreeBSD and would also use the ARM instances. 
> Are there any other interested parties?
> 
> I would be happy to donate my time and help.

I have tried this. It should work very well in theory, e.g. the network 
card driver (if_ena) compiles with no changes for aarch64, and in fact 
NetBSD has ported this driver and is up and running on these instances: 
https://dmesgd.nycbug.org/index.cgi?do=view&id=4623

But my result with FreeBSD was: nothing on the console after loader.efi 
hands control to the kernel.

My build patches: https://reviews.freebsd.org/D18372 & 
https://reviews.freebsd.org/D18371

Unfortunately, AWS still has a read-only serial console (WTF?!), so 
debugging systems there is a very frustrating experience of "stop 
instance, detach disk, attach it to a running instance, do changes, 
reattach back, start". And it feels like each of these steps runs 
sleep(10000) when handling requests.

I probably didn't see anything because the serial port wasn't 
configured. Seems like AWS in their infinite wisdom have decided to 
only provide their fancy PCIe based serial port. I have tried adding 
its PCI ID to various places, configuring various boot variables with 
the memory address that Linux/ACPI shows for that device, etc. but that 
didn't help.




home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1548182399.2864.0>