Release Notes

ip link/ifconfig displays RX dropped packets for
QL41xxx based interfaces
Description: On RHEL 7.4 system with QL41xxx devices connected, ip link -s or ifconfig displays the following
dropped packets:
ip -s link show dev p1p1
6: p1p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
mode DEFAU LT qlen 1000
link/ether 00:0e:1e:f0:fc:9c brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
31553072 415678 0 162 0 19646
TX: bytes packets errors dropped carrier collsns
7973881196 5395340 0 0 0 0
Applies to: Red Hat Enterprise Linux 7.4
Cause: There is no cause that is currently available for this issue.
Workaround: This error message can be ignored because there is no functionality loss.
dmesg displays debug messages for QL41xxx devices
Description:
On RHEL 7.4 system with QL41xxx devices connected, following qed driver debug messages are
displayed:
● [61531.866397] [qed_dbg_dump:6797(p1p1)]Collecting a debug feature
["idle_chk"]
● [61531.869558] [qed_dbg_dump:6797(p1p1)]Collecting a debug feature
["idle_chk"]
● [61531.872769] [qed_dbg_dump:6797(p1p1)]Collecting a debug feature
["reg_fifo"]
●
[61531.872789] [qed_dbg_dump:6797(p1p1)]Collecting a debug feature
["igu_fifo"]
Applies to: Red Hat Enterprise Linux 7.4
Cause: By default, debug messages are displayed in system log. These messages inform about the progress of
the probe.
Workaround: This error message can be ignored because there is no functionality loss.
Drivers available in OEMDRV drive is not installed
during the OS installation
Description:
Sometimes during OS installation, RHEL cannot enumerate the USB drive at the stage of driver disk
probing. Because of this, drivers from LC/OEMDRV cannot be installed.
Applies to: Red Hat Enterprise Linux 7.4
Cause: OEMDRV drive is not detected because the probing of drivers or kickstart in OEMDRV happens so fast
that the OEMDRV partition is enumerated after probing is completed. This USB drive enumeration is slow
due to race condition between several peripherals to be enumerated.
Workaround: Run the kernel boot parameter command inst.dd=LABEL=OEMDRV. OS booting will be on hold until the
USB is detected.
Known issues 29