Re: panic after LOR, 2nd netmap_mem2.c, 1st vm_fault.c

Bezüglich Harry Schmalzbauer's Nachricht vom 07.06.2017 16:20 (localtime): > lock order reversal: (sleepable after non-sleepable) > 1st 0xf8007519a960 vm object (vm object) @ > /usr/local/share/deploy-tools/RELENG_11/src/sys/vm/vm_fault.c:572 > 2nd 0xf8003299b000 (d)->nm_mtx

Re: ovs-netmap forgotten?

You can play with NIC interrupt coalescing settings to keep them under control (I don't know how in FreeBSD, but in Linux you would do that with e.g. "ethtool -C rx-usecs 100"). As written in the last line of netmap(4), you must disable all the offloadings when playing with netmap physical ports.

Re: panic after LOR, 2nd netmap_mem2.c, 1st vm_fault.c

Hi, I see this happening all the time, it's a locking problem. It does not cause a panic, usually. Can you please open an issue on the github tracker ( https://github.com/luigirizzo/netmap)? Thanks, Vincenzo 2017-06-07 18:28 GMT+02:00 Harry Schmalzbauer : > Bezüglich

Re: Anybody using SO_BINTIME with IPv6?

sobo...@sippysoft.com said: > SO_BINTIME was ENOTSUPP with IPv6 from the day one. Thanks. Is that a literal ENOTSUPP? Should I get an error from setsockopt? Or is that just shorthand for never-got-implemented? Do you want a bug report? If nothing else, the man page should be updated. Just

chelsio T-580_CR DPDK link down

Hi guys, I am currently trying to implement DPDK in a Dell PE R530 equipped with a Chelsio T-580-CR port in an 8x slot. So far, links to ports do not want to come up. Below are the commands of my exact approach. ### Installed dpdk from /usr/ports/net/dpdk in a

panic after LOR, 2nd netmap_mem2.c, 1st vm_fault.c

lock order reversal: (sleepable after non-sleepable) 1st 0xf8007519a960 vm object (vm object) @ /usr/local/share/deploy-tools/RELENG_11/src/sys/vm/vm_fault.c:572 2nd 0xf8003299b000 (d)->nm_mtx ((d)->nm_mtx) @ /usr/local/share/deploy-tools/RELENG_11/src/sys/dev/netmap/netmap_mem2.c:577