Solarflare driver trips an assert when LACP is used
Insta-panic when trying to configure a solarflare 10Gbe car for LACP.
#1 Updated by Sean Fagan over 5 years ago
- Assignee changed from Sean Fagan to Josh Paetzel
Well, that panic is apparently due to:
EFSYS_ASSERT3U(enp->en_mod_flags, &, EFX_MOD_PORT);
That seems to be due to a failed initialization.
There's a dtrace probe:
DTRACE_PROBE1(fail1, int, rc)
but I'm not sure what probe that actually maps to.
After the initialization fails, trying to use it results in the panic.
(Alternately, the driver was unloaded -- the bit is set in efx_port_init, and cleared on failure there; it's also cleared in efx_port_fini. It's also possible something is stomping it, but that seems less likely, doesn't it?)
I don't know how LAGG works; could it be trying to use an interface that has been unloaded or reset, or whose initialization failed?
#3 Updated by aurf alien over 5 years ago
I had time to really sit to find out whats going on. Using the card in any fashion, LACP or individual ports causes the system to core.
Using FreeNAS 9.1.1 yields no such issues in either LACP or individual ports mode. In other words, 9.1.1 works as expected were as 184.108.40.206 does not. What other info can I get you to help me fix this in 9.2.1.X?
#5 Updated by aurf alien over 5 years ago
Thanks very much Doug, nice of you to let me know.
I've noticed that Solarflare released a new driver as of March 13 of this year.
So I've compiled it against the latest FreeBSD 9.2 and it does work as individually configured ports. LCAP still causes a panic however.
But in FreeNAS 220.127.116.11 is causes a panic even when trying to use the card as separately configured ports.
Is there any way some one would compile it against 18.104.22.168 or 22.214.171.124 and send the sfxge.ko and accompanying sfxge.ko.symbols files? I'd be very appreciative to say the least.
I assume that its not possible to use whats been compiled under the latest FreeBSD 9.2?
#6 Updated by aurf alien over 5 years ago
Andrew Rybchenko from the firstname.lastname@example.org list has a patch that fixes this issue as he was able to repeat it. He will push it out to subversion after discussing it with Solarflare.
Once its pushed to subversion, how quickly can it be integrated into FreeNAS?
And is it possible for me to apply this patch on my systems w/o having to wait?
#7 Updated by Josh Paetzel over 5 years ago
- Status changed from Unscreened to Screened
We'll get it in the next release. You won't be able to patch your system, however I'll get you a kernel you can swap in as soon as it's available so you have a fix now, then can pick up the mainline change with the next release.