View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0016495 | CentOS-7 | kernel | public | 2019-09-30 10:39 | 2021-07-29 16:27 |
Reporter | kadafax | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Product Version | 7.7-1908 | ||||
Summary | 0016495: ixgbe and kernel 3.10.0-1062.1.1.el7.x86_64 spam "Warning firmware error detected FWSM: 0x00000000" message every seconds | ||||
Description | Centos 7.7 fully updated On kernel 3.10.0-1062.1.1.el7.x86_64 the following message is spamming logs every second: Warning firmware error detected FWSM: 0x00000000 The network seems to be working. The server is a Dell PowerEdge R510 (fully firmwares updated) and the NIC: Intel Corporation 82599 10 Gigabit TN Network Connection (rev 01) Reverting to 3.10.0-957.12.1.el7.x86_64 make this problem disappears. | ||||
Steps To Reproduce | Use a system with this NIC, upgrade to 3.10.0-1062.1.1.el7.x86_64 and watch the logs. | ||||
Tags | No tags attached. | ||||
abrt_hash | |||||
URL | |||||
has duplicate | 0018261 | acknowledged | Issue Tracker | ixgbe 0000:81:00.1: Warning firmware error detected FWSM: 0xFFFFFFFF |
Not a CentOS user, but searched for this on Google because it happened today to me on Debian. Suddenly network was down and that dmesg spam, soft reboot has resolved the problem. I find it a weird coincidence. Linux kernel 5.0.21-1-pve, but I think the kernel version is unrelated here. |
|
Which firmware version in those ixgbe? I've found that certain driver require certain specific firmware versions... |
|
Here it is: driver: ixgbe version: 5.1.0-k-rh7.6 firmware-version: 0x800001a5, 16.5.20 |
|
Same here # ethtool -i enp5s0f0 driver: ixgbe version: 5.1.0-k firmware-version: 0x000118b3 expansion-rom-version: bus-info: 0000:05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes |
|
Hello Team, We are facing the same issue please help on that |
|
According to https://access.redhat.com/solutions/5068871 , the solution is to upgrade the Ixgbe NIC firmware to the latest. | |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-09-30 10:39 | kadafax | New Issue | |
2019-09-30 22:13 | nixma | File Added: Screenshot from 2019-09-30 22-08-42.png | |
2019-09-30 22:13 | nixma | Note Added: 0035271 | |
2019-09-30 22:53 | pgreco | Note Added: 0035272 | |
2019-10-01 10:37 | kadafax | Note Added: 0035279 | |
2019-10-01 13:19 | nixma | Note Added: 0035285 | |
2021-07-28 11:37 | vslknsgr | Note Added: 0038551 | |
2021-07-29 16:25 | toracat | Relationship added | has duplicate 0018261 |
2021-07-29 16:26 | toracat | Status | new => acknowledged |
2021-07-29 16:27 | toracat | Note Added: 0038555 |