Summary: | ixgbe continuously complains about unsupported SFP | ||
---|---|---|---|
Product: | Base System | Reporter: | babak |
Component: | kern | Assignee: | Eric Joyner <erj> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Many People | CC: | bz, hiren, olivier, sbruno |
Priority: | --- | Keywords: | IntelNetworking |
Version: | 10.2-STABLE | ||
Hardware: | Any | ||
OS: | Any |
Description
babak
2015-08-04 07:27:14 UTC
Are you using unsupported SFP modules? Yes. I use Cisco SFPs. (In reply to Sean Bruno from comment #1) This looks like the "sfp_probe" function firing every 3 seconds and noticing that you have "unsupported" SFP modules. Wow, that's spammy. You can use the tuneable "hw.ix.unsupported_sfp" to turn this off, hopefully. Doesn't setting hw.ix.unsupported_sfp=0 disable my SFP then? I actually need that setting to be enabled, and as I mentioned in original PR, this behavior just happened after commit r283620. In older builds I just see the message once during the interface activation. Eric, Can you please take a look at this regression? It is super annoying to have the console getting spammed like this. :-) Thanks in advance. This behavior is very annoying: Can you fix this regression ? I think the proper (and acceptable) behaviour would be to log it once on driver attach (SPF insert) but not continuously. I did see it on every ifconfig up for a while in the past, which was already super-annoying with a 3rd party SPF. Lazy fix if it's really bothering you would be to redefine EWARN in ixgbe_osdep.h to print out nothing. You won't get any messages though, but I'm sure you'll know at this point if you're using an unsupported SFP or not. :p I'll work on getting EWARN to only fire once on attach(), since EWARN is only ever used to print out the message complaining about an unsupported SFP module. batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed. |