I have installed AlmaLibux 8.5 and latest 8.10 (different fresh builds for diagnostics purposes) on a HPE ProLiant ML30 Gen11 E 2414 server. Have also patched up server bios/ firmware to latest service pack. However, on both builds when left idle when logged in as the root user the below error message appears. Any ideas what this would indicate? Looks like something the kernel is not liking. How can I resolve this? Thanks in advance.
ālocal-tunnel.serviceā is a bepoke service in which automatically runs up an ssh connection to a remote server using public/ private key authencation with the following execution:
[Unit]
Description=āSetup a local tunnelā
After=network.target
Looks like Broadcom makes the Linux driver for BCM5719 available for personal use. If this is distributable to the public, ELRepo can package it is as a kmod.
Can you test-install the latest mainline kernel to see if the current version of the tg3 driver works better? You can find kernel-ml-6.10.0-0.rc3.el8.elrepo.x86_64 here:
Thank you for this. I have installed as per request. I will bench test for the next few days and let you know how it goes. Thanks for your help.
rpm -ivh kernel-ml-6.10.0-0.rc3.el8.elrepo.x86_64.rpm
error: Failed dependencies:
kernel-ml-core-uname-r = 6.10.0-0.rc3.el8.elrepo.x86_64 is needed by kernel-ml-6.10.0-0.rc3.el8.elrepo.x86_64
kernel-ml-modules-uname-r = 6.10.0-0.rc3.el8.elrepo.x86_64 is needed by kernel-ml-6.10.0-0.rc3.el8.elrepo.x86_6
I have conducted bench testing for over a 24-hour period and can confirm that the issue has not resurfaced. Typically, this issue would occur within an hour of the unit being powered on.
Will this be included into a new release? Thanks for your help, much appreciated.
Thatās good news. At this point I suggest you file a request for a kmod package for the tg3 driver with ELRepo ( My View - ELRepo Bugs ) . Providing a link to this forum thread will be helpful.
I would like to mention that this is the first HPE ProLiant ML30 Gen11 E 2414 on which we have installed AlmaLinux 8.x. However, itās important to note that we used the exact same installation process on another server of the same model (out the box, with no patches/ software mention in this thread), and that server does not experience the issue. I have contacted HPE and provided the relevant hardware-level logs. They confirmed that the hardware is functioning correctly, even though the issue persists with this particular server.