Hide Forgot
Unable to install RPM for the be2net kernel module. SRC RPM builds without errors however when trying to install the binary RPM the following error comes up: [root@localhost ~]# rpm -ihv /usr/src/redhat/RPMS/x86_64/kmod-be2net-2.101.171-12.x86_64.rpm error: Failed dependencies: ksym(lro_vlan_hwaccel_receive_frags) = 2f2b8561 is needed by kmod-be2net-2.101.171-12.x86_64 ksym(lro_flush_all) = 565e52cc is needed by kmod-be2net-2.101.171-12.x86_64 ksym(lro_receive_frags) = caded5d7 is needed by kmod-be2net-2.101.171-12.x86_64 [root@localhost ~]# This issue occurs because the the lro symbols are not on the Red Hat whitelist. Please update whitelist.
I'm assuming running the script from: http://driverupdateprogram.com/downloads/abi_check.py will yield the same results for identifying the offending symbols?
Yes. # ./abi_check.py /lib/modules/2.6.18-128.el5/extra/be2net.ko Red Hat Enterprise Linux 5 ABI Checker -------------------------------------- ABI Checker version: 1.2 Module: be2net.ko Kernel: 2.6.18-128.el5 Whitelist: /usr/src/kernels/2.6.18-128.el5-x86_64/kabi_whitelist WARNING: The following symbols are used by your module WARNING: and are not on the ABI whitelist. symbol: lro_flush_all symbol: lro_receive_frags symbol: lro_vlan_hwaccel_receive_frags [root@kettle extra]#
Thanks Vaios - just wanted to double check to make sure the tool output matches what you were seeing when you tried to install the kernel.
Emulex: Any reason why LSO is being used to begin? GRO was added in RHEL 5.4 and upstream be2net is GRO I believe as well...
You are right Andrius. Unlike be2net in RH 5.4, this be2net driver uses GRO instead of LRO and this is not an issue for be2net. We can close this bug. Thanks. Subbu
Will do - I'm assuming this is also the case as well upstream for RHEL 6, correct? May close those as well?
Yes, GRO in upstream and RH6 also. Subbu