Date: Sun, 28 May 2017 10:58:41 +0200 From: Harry Schmalzbauer <freebsd@omnilan.de> To: Vincenzo Maffione <v.maffione@gmail.com> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: [panic] netmap(4) and if_lagg(4) Message-ID: <592A9141.4040002@omnilan.de> In-Reply-To: <CA%2B_eA9h=UmC3RpXaMmzQ7oRQbn_4E4eYf5oEBhV7YJ2G_hYfsQ@mail.gmail.com> References: <58CBCD7A.8060301@omnilan.de> <58CFA394.8070901@omnilan.de> <CA%2B_eA9jf_VjcYUZynu5CXx-ps5z7PSxOky=QLpR-miqtxmMU5w@mail.gmail.com> <5926EE96.1010000@omnilan.de> <CA%2B_eA9gcMD1QyG35p5UY8kz6n1kF%2B56Arz3q1T8HVBfMv3XN0w@mail.gmail.com> <5926F9F9.4040706@omnilan.de> <CA%2B_eA9hripEStmfJhj_Q93OF5jFf2nfQXeuA2DnuSjBmJi6j4g@mail.gmail.com> <592701D6.7030301@omnilan.de> <592742A8.4010207@omnilan.de> <CA%2B_eA9jg-xXJpeyQkcFzA%2B-y=qbwROww2FRWzCN=dkmfkaQivQ@mail.gmail.com> <5927D560.10003@omnilan.de> <CA%2B_eA9jhDZ-Cnj8zyAcp=1dw=Q%2BZm2m%2BBkxK11x6Y%2BHLhX%2BrUg@mail.gmail.com> <5927D77A.60502@omnilan.de> <CA%2B_eA9j%2BN5-2om2DETe0K1sAUPqDgwuNuNbF2F9St6C-YCKWQg@mail.gmail.com> <5927E974.6060706@omnilan.de> <CA%2B_eA9gpKd1k2VJnzi=bE2Oy7LLUD=pxRCt9yS0nACB3YAX2Sw@mail.gmail.com> <5927EF05.9040208@omnilan.de> <CA%2B_eA9gbPRYhVAftRTsNXVmzW23tkSOMXVbP4tU48hK--Zw%2BUg@mail.gmail.com> <59281DF8.20402@omnilan.de> <CA%2B_eA9h=UmC3RpXaMmzQ7oRQbn_4E4eYf5oEBhV7YJ2G_hYfsQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bezüglich Vincenzo Maffione's Nachricht vom 28.05.2017 09:46 (localtime): >> >> I also recomplied vale-ctl, but I get the following error when trying to >> add em0 (lagg-unrelated): >> 389.083433 [ 835] netmap_obj_malloc netmap_ring request size >> 65792 too large >> 389.091593 [1693] netmap_mem2_rings_create Cannot allocate RX_ring >> > > It means that you are giving too many slot to each RX ring, probably 4096. > Try to use less slots, or to increase the dev.netmap.ring_size sysctl > (default value is less than 65792). Hmm, then thn I guess a default like dev.netmap.priv_ring_size has changed, because my em txd/rxd were default 4096, for both, native stable/11-netmap and HEAD-netmap... Reducing r/txd to 1024 solved the problem (hw.em.rxd in loader.conf). >> >> Adding lagg still results in a panci, but with your latest >> "return()"-patch, it's different: >> >> 0xffffffff8042aefb is in freebsd_generic_rx_handler … >> >> > Yeah, the same bug jist slipped back. Discard the previous patch and > replace it with the attached one. Thanks a lot! This patch avoids the panic :-) But unfortunately kills lagg (existing sockets break, nothing more tested yet) 488.896454 [ 394] nm_os_generic_find_num_desc called, in tx 1024 rx 1024 488.903445 [ 402] nm_os_generic_find_num_queues called, in txq 0 rxq 0 488.910424 [1252] generic_netmap_attach Created generic NA 0xfffff80036b26400 (prev 0) 488.971772 [ 448] generic_netmap_register Generic adapter 0xfffff80036b26400 goes on 488.980127 [ 495] generic_netmap_register RX ring 0 of generic adapter 0xfffff80036b26400 goes on 488.989917 [ 495] generic_netmap_register RX ring 1 of generic adapter 0xfffff80036b26400 goes on 488.999720 [ 502] generic_netmap_register TX ring 0 of generic adapter 0xfffff80036b26400 goes on 489.009504 [ 502] generic_netmap_register TX ring 1 of generic adapter 0xfffff80036b26400 goes on 489.019802 [3055] netmap_transmit lagg0 drop mbuf requiring offloadings 490.579512 [3055] netmap_transmit lagg0 drop mbuf requiring offloadings 491.781780 [3055] netmap_transmit lagg0 drop mbuf requiring offloadings … Have a nice sunday, will try to find some time next week to do more investigation, must close for today, haven't even read the messages, just wanted to drop a note. thnaks, -harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?592A9141.4040002>