You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] sof-kernel-log-check: filter out IGB issues #617
Looking at drivers/net/ethernet/intel/igb/igb_main.c this error message is printed when and only when a watchdog found SR_1000T_REMOTE_RX_STATUS a.k.a Remote receiver OK to be repeatedly wrong 20 times over 2 seconds. Really not good.
How often do you get this message and what other igb messages are around it? It could have been just a temporary glitch because of some bad contact or bent cable or temporary interference.
I think we really need this custom sof-test config file where anyone can add any particular error they have. Of course CI would never use such custom additions but only the default and common set of ignored errors. Using such a file would print a warning at the start of the test. It's one thing to ignore network or other glitches at home when you can just stand up, give the system a kick, re-run the tests without even looking at what went wrong and forget about it. It's a totally different story to ignore network glitches in a distant lab, especially during COVID. @fredoh9 and others have already spent many days in the lab troubleshooting various storage and network issues and hiding warning signs is really not a good idea. Ignoring storage and network errors is not like ignoring wifi or keyboard errors.
Activity
marc-hb commentedon Mar 5, 2021
igb= Intel Gigabit Ethernet.I searched this message in the source code and on the Internet and it could be a cable issue, can you try a different cable?
Ignoring bad cables and similar network issues sounds like a bad idea.
plbossart commentedon Mar 5, 2021
It's not a cable issue, I use the same with other interfaces (RTL or USB dongles) and they work fine.
marc-hb commentedon Mar 5, 2021
Gigabit Ethernet uses all 4 pairs both ways. 100Mb/s uses only 2 pairs one-way each.
plbossart commentedon Mar 5, 2021
I have only Gigabit stuff and 935Mbs/s all the way to my devices over Google Fiber. Cables are not the problem
plbossart commentedon Mar 5, 2021
PING:
6.0 ms
DOWNLOAD
936 Mbps
UPLOAD
816 Mbps
marc-hb commentedon Mar 5, 2021
Looking at
drivers/net/ethernet/intel/igb/igb_main.cthis error message is printed when and only when a watchdog foundSR_1000T_REMOTE_RX_STATUSa.k.aRemote receiver OKto be repeatedly wrong 20 times over 2 seconds. Really not good.How often do you get this message and what other
igbmessages are around it? It could have been just a temporary glitch because of some bad contact or bent cable or temporary interference.I think we really need this custom sof-test config file where anyone can add any particular error they have. Of course CI would never use such custom additions but only the default and common set of ignored errors. Using such a file would print a warning at the start of the test. It's one thing to ignore network or other glitches at home when you can just stand up, give the system a kick, re-run the tests without even looking at what went wrong and forget about it. It's a totally different story to ignore network glitches in a distant lab, especially during COVID. @fredoh9 and others have already spent many days in the lab troubleshooting various storage and network issues and hiding warning signs is really not a good idea. Ignoring storage and network errors is not like ignoring wifi or keyboard errors.
(even funnier, ignoring audio errors: thesofproject/sof#2686)
plbossart commentedon Mar 15, 2021
I get this with a different board and different cables
sof-kernel-log-check: filter out IGB messages
sof-kernel-log-check: filter out IGB messages
marc-hb commentedon Mar 19, 2021
@plbossart closed by #631?