Update ena to 2.10.x or later

[Paul Gear]

Please update the ena driver in the default AWS images to 2.10.x or later. This is to enable use of the PTP hardware clock (PHC) for high resolution timekeeping. https://github.com/amzn/amzn-drivers/tree/master/kernel/linux/ena#ptp-hardware-clock-phc

Ideally it would be accompanied with a configuration which sets `option phc_enable 1` in `/etc/modprobe.d/`, reads the error bound from `/sys/devices/pci0000:00/0000:00:05.0/phc_error_bound` and adds an appropriate chrony config snippet to `/etc/chrony/conf.d/` to use this as a source per https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html#ptp-hardware-clock-requirements, but just making the driver available for users to configure would be a good step.

This is only relevant on r7g instances in ap-northeast-1 (Tokyo) at the moment, but is apparently rolling out to other instances and regions. https://aws.amazon.com/about-aws/whats-new/2023/11/amazon-time-sync-service-microsecond-accurate-time/

[Philip Cox (philcox)]

I am looking in to this.

[Philip Cox (philcox)]

Hi @paulgear, I didn't see it listed in the launchpad bug at all, but what version of ubuntu are you using, and which kernel?

I wanted to check if the jammy (22.04) 6.8 based kernel (jammy:linux-aws-6.8) or the noble (24.04) 6.8 based kernel (noblel:inux-aws) solve this problem for you?

They both have updated versions of the ena driver.

[Paul Gear (paulgear)]

Thanks for following up @philcox. At the time I was using the default jammy image available in the AWS marketplace. I'll check the latest ones this week to see what they're showing.

[Philip Cox (philcox)]

Hi @paulgear,

If this issue happens again, please re-open the ticket.