Hi @philcox, Sorry for the delay circling back to this. I can't see any evidence that the ena driver has been updated on the latest images. Here's the output from a test I did on t3a.micro instances in the ap-southeast-2 (Sydney) region.
Ubuntu 24.04 ============ root@ip-10-0-11-213:~# uname -r 6.8.0-1021-aws root@ip-10-0-11-213:~# journalctl --dmesg|grep -iw ena Feb 04 10:14:12 ip-10-0-11-213 kernel: ena: unknown parameter 'phc_enable' ignored Feb 04 10:14:12 ip-10-0-11-213 kernel: ena 0000:00:05.0: ENA device version: 0.10 Feb 04 10:14:12 ip-10-0-11-213 kernel: ena 0000:00:05.0: ENA controller version: 0.0.1 implementation version 1 Feb 04 10:14:12 ip-10-0-11-213 kernel: ena 0000:00:05.0: LLQ is not supported Fallback to host mode policy. Feb 04 10:14:12 ip-10-0-11-213 kernel: ena 0000:00:05.0: Elastic Network Adapter (ENA) found at mem 80400000, mac addr 02:0e:04:f8:df:35 Feb 04 10:14:12 ip-10-0-11-213 kernel: ena 0000:00:05.0 ens5: renamed from eth0 Amazon Linux 2023 ================= [root@ip-10-0-2-197 ~]# uname -r 6.1.124-134.200.amzn2023.x86_64 [root@ip-10-0-2-197 ~]# journalctl --dmesg|grep -iw ena Feb 04 10:06:56 ip-10-0-2-197.ap-southeast-2.compute.internal kernel: ena 0000:00:05.0: Elastic Network Adapter (ENA) v2.13.2g Feb 04 10:06:57 ip-10-0-2-197.ap-southeast-2.compute.internal kernel: ena 0000:00:05.0: ENA device version: 0.10 Feb 04 10:06:57 ip-10-0-2-197.ap-southeast-2.compute.internal kernel: ena 0000:00:05.0: ENA controller version: 0.0.1 implementation version 1 Feb 04 10:06:57 ip-10-0-2-197.ap-southeast-2.compute.internal kernel: ena 0000:00:05.0: LLQ is not supported Fallback to host mode policy. Feb 04 10:06:57 ip-10-0-2-197.ap-southeast-2.compute.internal kernel: ena 0000:00:05.0: Elastic Network Adapter (ENA) found at mem 80400000, mac addr 02:fa:e6:6f:d9:97 Feb 04 10:06:57 ip-10-0-2-197.ap-southeast-2.compute.internal kernel: ena 0000:00:05.0 ens5: renamed from eth0 Feb 04 10:06:58 ip-10-0-2-197.ap-southeast-2.compute.internal kernel: ena 0000:00:05.0 ens5: Local page cache is disabled for less than 16 channels Both instances had a file /etc/modprobe.d/ena.conf present with the contents: options ena phc_enable=1 As you can see, the AL2023 kernel includes ena driver v2.13.2g, while Ubuntu 24.04's kernel includes ena driver v0.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2054688 Title: Update ena to 2.10.x or later Status in linux-aws package in Ubuntu: New Bug description: 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/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2054688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
