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 <free...@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 _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
