kernel panic when lagg is used (#323) [patch]

[doktornotor]

Can someone kindly apply this patch from HEAD?

https://bugs.freebsd.org/bugzilla/show_ ... ?id=211689
https://svnweb.freebsd.org/base?view=re ... ion=312979

The bug is pretty annoying, makes lagg completely unusable.

[zoon01]

those patches are already included in latest 11.1 series as those are in source code freebsd 11.1 release

[doktornotor]

Been testing for a while with 11.1.0.4.4899, looks like it finally works...

[igr4free]

Been testing for a while with 11.1.0.4.4899, looks like it finally works...

It’s necessary to make a fresh install? Wirh upgrade, i hace the same problem

[doktornotor]

I cannot imagine what would get solved with a fresh install, it's a kernel problem.

[lux]

i never had a single glitch with my lagg on both machines in my sig... both have intel LAN Cards installed

@ doktornotor

wich LAN Cards do you use?

[doktornotor]

The Microserver Gen8 has bge (Broadcom). Using igb Intel did not help at all. It's not a NIC driver bug, it's if_lagg.c problem. (Or, better said, multiple of them.)

[xbb]

I had problems with lagg too, which I "solved" by disabling zeroconf. Almost everytime I restarted a service (or saved configuration in the webui), my nas rebooted.

[igr4free]

I had problems with lagg too, which I "solved" by disabling zeroconf. Almost everytime I restarted a service (or saved configuration in the webui), my nas rebooted.

but zeroconf it's necessary enabled if you are using timemachine backup's (it's my case), thnks for your reply!

[lindsay]

The Microserver Gen8 has bge (Broadcom). Using igb Intel did not help at all. It's not a NIC driver bug, it's if_lagg.c problem. (Or, better said, multiple of them.)

Have 4 intel nic`s in LACP and have no problem. So it then can`t be a nic driver problem anf eighter a lagg problem;)

[lux]

...I had problems with lagg too, which I "solved" by disabling zeroconf...

i never used zeroconf, so it's disabled on all my Machines...

[doktornotor]

The Microserver Gen8 has bge (Broadcom). Using igb Intel did not help at all. It's not a NIC driver bug, it's if_lagg.c problem. (Or, better said, multiple of them.)

Have 4 intel nic`s in LACP and have no problem. So it then can`t be a nic driver problem anf eighter a lagg problem;)

The problem is that - depending on what service you reconfigure - the thing makes a giant kaboom on (re)configuring the lladdr (the MAC address) of the LAGG interface. This happens a whole lot more "reliably" when using dual stack/IPv6.

There are more fixes for this applied in current pfSense, however the Texan guy no longer makes the FreeBSD kernel patches available, despite their "open-source" touting in about every piece of their marketing material. So... what's been upstreamed has been upstreamed, as for the rest - SOL at the moment.