Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Mar 2017 18:29:28 +0100
From:      Vincenzo Maffione <v.maffione@gmail.com>
To:        Harry Schmalzbauer <freebsd@omnilan.de>
Cc:        freebsd-net <freebsd-net@freebsd.org>
Subject:   Re: [panic] netmap(4) and if_lagg(4)
Message-ID:  <CA%2B_eA9iCT7evWUcZMA_ViKfrZnSHp3OpBTS5c4iJ9=ZjO-Pfgw@mail.gmail.com>
In-Reply-To: <58CBCD7A.8060301@omnilan.de>
References:  <58CBCD7A.8060301@omnilan.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
  This is supposed to work because of the emulated netmap adapter.
By means of that, Netmap works on tap(4) interfaces if_bridge interfaces,
epairs, etc. Have you tried those to see if that works?
Maybe here the problem is that if_lagg is a "metadriver", which interacts
in a bad way with the emulated adapter, which needs to intercept all the
packets received from the driver.

Cheers,
  Vincenzo

2017-03-17 12:50 GMT+01:00 Harry Schmalzbauer <freebsd@omnilan.de>:

>  Unforutantely I can't use if_lagg(4) as physical vale interface:
>
> lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
> 9000
> options=6403b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,
> VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
>         ether 96:07:e9:78:c6:ac
>         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>         media: Ethernet autoselect
>         status: active
>         groups: lagg
>         laggproto lacp lagghash l2,l3,l4
>         laggport: igb0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
>         laggport: igb1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
>
> 'vale-ctl -h vale0:lagg0'
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 2; apic id = 02
> fault virtual address   = 0xc
> fault code              = supervisor read data, page not present
> instruction pointer     = 0x20:0xffffffff80422b54
> stack pointer           = 0x28:0xfffffe0444720740
> frame pointer           = 0x28:0xfffffe0444720760
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 12 (irq268: igb0:que 2)
> trap number             = 12
> panic: page fault
> cpuid = 2
> KDB: stack backtrace:
> #0 0xffffffff805ccbc7 at kdb_backtrace+0x67
> #1 0xffffffff8058aa26 at vpanic+0x186
> #2 0xffffffff8058a893 at panic+0x43
> #3 0xffffffff808762b2 at trap_fatal+0x322
> #4 0xffffffff8087647c at trap_pfault+0x1bc
> #5 0xffffffff80875b30 at trap+0x280
> #6 0xffffffff8085c6f1 at calltrap+0x8
> #7 0xffffffff8068d254 at vlan_input+0x1a4
> #8 0xffffffff80680188 at ether_demux+0x98
> #9 0xffffffff80680eaf at ether_nh_input+0x30f
> #10 0xffffffff8069a725 at netisr_dispatch_src+0xa5
> #11 0xffffffff806804a6 at ether_input+0x26
> #12 0xffffffff8039a84d at igb_rxeof+0x6fd
> #13 0xffffffff80399c54 at igb_msix_que+0x114
> #14 0xffffffff805528de at intr_event_execute_handlers+0xde
> #15 0xffffffff80552bb6 at ithread_loop+0xc6
> #16 0xffffffff8054ffc5 at fork_exit+0x85
> #17 0xffffffff8085cc2e at fork_trampoline+0xe
>
> Is vale supposed to work with artificial interfaces like if_lagg?
> Is it worth filing a bug report or won't it ever be possible?
>
> Thanks,
>
> -harry
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
>



-- 
Vincenzo Maffione



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B_eA9iCT7evWUcZMA_ViKfrZnSHp3OpBTS5c4iJ9=ZjO-Pfgw>