[panic] netmap(4) and if_lagg(4)
Vincenzo Maffione
v.maffione at gmail.com
Fri May 26 07:14:38 UTC 2017
Hi,
Your stack trace report this:
#7 0xffffffff8069dc50 at vlan_input+0x1f0
which means VLANs are involved, in some way. Is that the correct trace?
Cheers,
VIncenzo
2017-05-26 9:12 GMT+02:00 Harry Schmalzbauer <freebsd at omnilan.de>:
> 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
>
--
Vincenzo Maffione
More information about the freebsd-net
mailing list