[panic] netmap(4) and if_lagg(4)

Harry Schmalzbauer freebsd at omnilan.de
Fri May 26 07:12:37 UTC 2017


Bezüglich Vincenzo Maffione's Nachricht vom 25.05.2017 22:57 (localtime):
> No, the thing is that I misinterpreted your stack trace. The patch is ok
> for a different bug. It seems that the problem are vlans more than lagg.
> Which interface did you put in netmap mode, em or em.345?

Good morning,

it was if_lagg itself, no vlan clone.
The latter is a completely different problem, and contrary to the
initial panic report, vlan clones don't lead to panics anymore.


-harry


More information about the freebsd-net mailing list