[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

2017-02-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340

Rick Macklem  changed:

   What|Removed |Added

 Status|Closed  |In Progress
 Resolution|FIXED   |---

--- Comment #24 from Rick Macklem  ---
Please test the patch I just attached. (4th one) I think it might make the
code less fragile to nfsd threads being signalled. I have not been able
to create a crash with the patch during limited testing.

Since avg@'s crash occurred with the other patches, I have reopened the
PR.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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"

[Bug 204340] [panic] nfsd, em, msix, fatal trap 9

2017-02-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340

--- Comment #23 from Rick Macklem  ---
Created attachment 179512
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179512=edit
add svcpool_close so that svcpool_destroy doesn't get called when nfsd threads
are killed

This patch adds a new function to the server krpc called svcpool_close().
It is similar to svcpool_destroy(), but does not free the data structures,
so that the pool can be used again.

This function is then used instead of svcpool_destroy(), svcpool_create()
when the nfsd threads are killed.

These crashes are caused because the data structures were free'd by
svcpool_destroy() when the nfsd threads were killed off (or signalled somehow).
By avoiding the svcpool_destroy() call, the crashes should be avoided.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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"

Re: Disappointing packets-per-second performance results on a Dell, PE R530

2017-02-01 Thread Olivier Cochard-Labbé 
​​
​​
On Wed, Feb 1, 2017 at 1:00 AM, Jordan Caraballo <
jordancaraball...@gmail.com> wrote:

> Hi Oliver, my bad, I missed that one. Here is the info:
>
> * Switch with 48x 10G ports and 12x 40G ports was used
> * (48) 10G connected nodes were used.
> * (24) nodes on each side of the firewall
> * Packet per second (PPS) tests were run using 'iperf'
> * Bandwidth tests were run using 'nuttcp'
> * Parallelization was handled by using pdsh
> * Each of the 24 sending nodes ran either:
>   iperf3 -c "" -u -A 5 -l 512 -b 0 -t "" -J
>   nuttcp -fparse -l 128k -w1m -T "" ""
>
>
​Your current performance (1.5Mpps) seems to indicate that only one,
perhaps 2 cores maximum are used.

Can you confirm that during your iperf bench there are 24 distinct flows
simultaneously (different source/destination IP) ?
source-IP-1 -> target-IP-1
source-IP-2 -> target-IP-2
... until source-IP-24 -> target-IP-24

On your dual CPU with 18 cores, chelsio drivers should create per each port:
- 8 RX queues (rxq NIC)
- 16 TX queues (txq NIC)

Can you check on /var/run/dmesg.boot that you've got something like this:

t5nex0:  mem 0xfb78-0xfb7f,0xfa
00-0xfaff,0xf9ff-0xf9ff1fff irq 40 at device 0.4 numa-domain 0 on
pci7
cxl0:  numa-domain 0 on t5nex0
cxl0: Ethernet address: 00:07:43:2e:e4:70
cxl0: 16 txq, 8 rxq (NIC); 8 txq, 2 rxq (TOE)

=> Notice the 16 txq, 8 rxq (NIC) lines

Now, like Slawa says, we should see the 8 IRQ assigned to these 8 rxq and
equally used.
After your bench, output of a "vmstat -ia | grep t5nex0:0a" should display
a minimum of 8 lines with equally distributed number like this example:

[root@hp]~# vmstat -ia | grep t5nex0:0a
irq292: t5nex0:0a037  0
irq293: t5nex0:0a1288498629
irq294: t5nex0:0a2225410492
irq295: t5nex0:0a3306227668
irq296: t5nex0:0a4282679617
irq297: t5nex0:0a5313143683
irq298: t5nex0:0a6318727695
irq299: t5nex0:0a7308669673

(my example seems not perfect because queue0 seems under-utilized, but
you've got the idea)
___
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"

[Bug 216681] IPsec traceroute6 -I does not work

2017-02-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216681

Mark Linimon  changed:

   What|Removed |Added

   Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
   Keywords||patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
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"

[Bug 202680] Silent data corruption on em(4) interfaces

2017-02-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680

--- Comment #28 from Dmitry Afanasiev  ---
Bug still exists on stable/10 r309900 - 3 times got ssh disconnections, and got
2 errors for dumb TCP data transfer per ~3Tb of transmitted data.

To check on current I should switch some services from this server and should
have a time to run tests. But I will try to test in this month.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
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"

[Bug 216304] Adding xn0 to bridge0 causes kernel panic

2017-02-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216304

Kristof Provost  changed:

   What|Removed |Added

   Assignee|freebsd-net@FreeBSD.org |k...@freebsd.org
  Flags||mfc-stable10+,
   ||mfc-stable11+
 Resolution|--- |FIXED
 Status|New |Closed

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
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"

[Bug 216304] Adding xn0 to bridge0 causes kernel panic

2017-02-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216304

--- Comment #9 from commit-h...@freebsd.org ---
A commit references this bug:

Author: kp
Date: Wed Feb  1 21:44:50 UTC 2017
New revision: 313066
URL: https://svnweb.freebsd.org/changeset/base/313066

Log:
  MFC 312782

  bridge: Release the bridge lock when calling bridge_set_ifcap()

  This calls ioctl() handlers for the different interfaces in the bridge.
  These handlers expect to get called in an ioctl context where it's safe
  for them to sleep. We may not sleep with the bridge lock held.

  However, we still need to protect the interface list, to ensure it
  doesn't get changed while we iterate over it.
  Use BRIDGE_XLOCK(), which prevents bridge members from being removed.
  Adding bridge members is safe, because it uses LIST_INSERT_HEAD().

  This caused panics when adding xen interfaces to a bridge.

  PR:   216304
  Reviewed by:  ae
  Sponsored by: RootBSD
  Differential Revision:https://reviews.freebsd.org/D9290

Changes:
_U  stable/10/
  stable/10/sys/net/if_bridge.c
  stable/10/sys/net/if_bridgevar.h

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
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"

[Bug 216304] Adding xn0 to bridge0 causes kernel panic

2017-02-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216304

--- Comment #8 from commit-h...@freebsd.org ---
A commit references this bug:

Author: kp
Date: Wed Feb  1 20:27:38 UTC 2017
New revision: 313050
URL: https://svnweb.freebsd.org/changeset/base/313050

Log:
  MFC 312782

  bridge: Release the bridge lock when calling bridge_set_ifcap()

  This calls ioctl() handlers for the different interfaces in the bridge.
  These handlers expect to get called in an ioctl context where it's safe
  for them to sleep. We may not sleep with the bridge lock held.

  However, we still need to protect the interface list, to ensure it
  doesn't get changed while we iterate over it.
  Use BRIDGE_XLOCK(), which prevents bridge members from being removed.
  Adding bridge members is safe, because it uses LIST_INSERT_HEAD().

  This caused panics when adding xen interfaces to a bridge.

  PR:   216304
  Reviewed by:  ae
  Sponsored by: RootBSD
  Differential Revision:https://reviews.freebsd.org/D9290

Changes:
_U  stable/11/
  stable/11/sys/net/if_bridge.c
  stable/11/sys/net/if_bridgevar.h

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
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"

RE: Infor Partner Info

2017-02-01 Thread Paul Christopher 
Hi,

 

I was researching your company website and I understand that your company is
a "Infor Partner" and I figured it'd be worth leaving a note, We maintain
about 25 Million+ B2B contacts from various industries. We are specialized
in working with companies whose target market is Infor Users. By helping
them acquire relevant Marketing Lists. Just wanted to check if you would be
interested in reaching out to Infor users and similar service provider and
users with contact information for your Lead Generation, Email campaign,
Tele marketing and other marketing initiatives?

 

We have Infor Products Users like:

 

2DDesignAutomation, 3DDesignAutomation, ACmanagerCRM, Adage,
AdvancedPlanning, AdvancedScheduling, AnaelFMS, AnaelHCM, Approva, Baan5.x,
BaanIV, Infor BI, BIApplicationStudio, BIDashboards, BIDeltaMiner,
BIImportMaster, BIOfficePlus, BPCS, CAS, CloudSuite, Infor COM, Infor CORS,
CPM, Infor CRM, Infor DemandPlanning, Infor DistributionFACTS, Infor
DistributionSX.e, ESeriesFMS, ESeriesHCM, Infor EAM, Infor e-Commerce,
Elevon, EnRoute, EPAK, Epiphany, EzLite, EzPLUS, EzRMS, F9, FourthShift,
GlobalHR, GrowthPower, Infor HMS, InfiniumFMS, InfiniumHCM, InfiniumMM/PR,
Infopoint, Inforce, Infor ION, Infor KBM, Landmark, Lawson, Leanware, Infor
LN, Infor LoadPlanning, Infor LX, MSeriesFMS, MSeriesHCM, Infor M3, M3EAM,
MAC-PACXE, MANMAN, MasterpieceFMS, MasterpieceHCM, MAX+TM, MAXCIM,
MaxRecall, MediSuite, Ming.le, Infor MK, Mongoose, Infor MP2, NetworkDesign,
Optiva, Pathway, PLMDiscrete, PLMFashion, Point.Man, PRISM,  InforPRMS,
Protean, PublicSector, Infor RFID, RoutePlanning, SalesPortal,
SmartStreameXFM, SmartStreamFMS, SmartStreamHCM, StarlightPMS, System21,
TRANS4M, Workspace, Infor XA, Infor XBRL, Infor Xpert and many more Users
across the globe.

 

All contacts come with the following information: LinkedIn Profile, Company
Name, Contact name, Title, Address, Phone, Fax, City, State, Zip codes,
Country, Industry, Employee size, Revenue size, Sic Code, Website and
verified email address.

 

Unlike any other vendors out there, our lists are dual verified (Email &
Call). We only provide you opt in contacts (permission based).

 

Note: If this is not relevant to you please reply back with your Target
Market, we have all types of target market available.

 

If it sounds good for you, Please let me know your Exact:

 

Target Industry/Technology User: _ (Any Industry)

Target Geography :( worldwide)

Target Job Title :__( Any Job Title)

 

So, that I can get back to you with more information like counts, cost and
as well as free sample file for your review.

 

Waiting for your Swift Response

 

Regards,

Paul Christopher

Marketing Manager

Cordell Data Marketing Inc.

984 Rowley Drive 
San Jose 95132
United States

 

To opt out please response Remove in subject line.

___
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"

Re: ipv6 setup.

2017-02-01 Thread Herbert J. Skuhra 
Hei,

Ørjan Tønder skrev:
> 
> I am trying too get ipv6 up and running but i cant get outside.
> -- /etc/rc.conf
> ipv6_default_interface="re0"
> #ifconfig_re0_ipv6="inet6 accept_rtadv"
> ifconfig_re0_ipv6="inet6 2a01:4f8:131:50a1::2/64"
> ipv6_defaultrouter="inet6 fe80::1%re0"
  
Remove the inet6 keyword in the last line and try again!

--
Herbert
___
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"

Re: 11-stable mountd listens on port 993

2017-02-01 Thread Eric van Gyzen 

On 02/01/2017 06:28, Peter Blok wrote:

I just updated to 11-stable@313042 and when I rebootted my system dovecot
didn’t want to start because port 993 was already in use.

Checked with lsof and it was mountd that was listening on this port. When I
stopped mountd and started dovecot everything was fine. When I started mountd
after this it worked ok.

Next reboot everything was fine.

Anybody know why mountd could have been listening to port 993?


Since mountd uses bindresvport_sa(3), the kernel chooses a port in the "low" 
range, configured via sysctl:


net.inet.ip.portrange.lowlast: 600
net.inet.ip.portrange.lowfirst: 1023

There is some randomness in the algorithm, so there is roughly a 1/424 chance of 
conflict.  You might use the -p flag to mountd or reduce lowfirst below 993.


Cheers,

Eric
___
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"

11-stable mountd listens on port 993

2017-02-01 Thread Peter Blok 
I just updated to 11-stable@313042 and when I rebootted my system dovecot 
didn’t want to start because port 993 was already in use.

Checked with lsof and it was mountd that was listening on this port. When I 
stopped mountd and started dovecot everything was fine. When I started mountd 
after this it worked ok.

Next reboot everything was fine.

Anybody know why mountd could have been listening to port 993?

Peter


___
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"

Re: Disappointing packets-per-second performance results on a Dell, PE R530

2017-02-01 Thread Slawa Olhovchenkov 
On Tue, Jan 31, 2017 at 08:00:03PM -0400, Jordan Caraballo wrote:

> Hi Oliver, my bad, I missed that one. Here is the info:
> 
> * Switch with 48x 10G ports and 12x 40G ports was used
> * (48) 10G connected nodes were used.
> * (24) nodes on each side of the firewall
> * Packet per second (PPS) tests were run using 'iperf'
> * Bandwidth tests were run using 'nuttcp'
> * Parallelization was handled by using pdsh
> * Each of the 24 sending nodes ran either:
>iperf3 -c "" -u -A 5 -l 512 -b 0 -t "" -J
>nuttcp -fparse -l 128k -w1m -T "" ""

Very strange result.
I am don't see in you output any chelsio irq, like this:

irq289: t5nex0:evt 2  0
irq300: t5nex0:1a0  204093767467  48085
irq301: t5nex0:1a1  204536605147  48189
irq302: t5nex0:1a2  204677310714  48222
irq303: t5nex0:1a3  204727624595  48234
irq304: t5nex0:1a4  204345362150  48144
irq305: t5nex0:1a5  203085398725  47847
irq306: t5nex0:1a6  204014240537  48066
irq307: t5nex0:1a7  204216351652  48114
irq308: t5nex0:1A0 132806676 31
irq309: t5nex0:1A1 133275327 31

Do you using polling?

> On 31/01/17 16:45, Olivier Cochard-Labbé wrote:
> > On Tue, Jan 31, 2017 at 6:53 PM, Jordan Caraballo 
> > > wrote:
> >
> > This are the most recent stats. No advances so far. The system has
> > -Current right now.
> >
> > Any help or feedback would be appreciated.
> >
> >
> > ​I've tried: But you didn't answer my previous question.
> >
> > How do you generate your IP traffic ?
> > What tool are you using​ and can you provide the exact command line used ?
> 
> ___
> 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"
___
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"

ipv6 setup.

2017-02-01 Thread Ørjan Tønder 
I am trying too get ipv6 up and running but i cant get outside.

-- /etc/rc.conf
ipv6_default_interface="re0"
#ifconfig_re0_ipv6="inet6 accept_rtadv"
ifconfig_re0_ipv6="inet6 2a01:4f8:131:50a1::2/64"
ipv6_defaultrouter="inet6 fe80::1%re0"


-- Routing tables

Internet6:
Destination   Gateway   Flags
 Netif Expire
::/96 ::1   UGRS
 lo0
default   fe80::1%re0   UGS
re0
::1   link#2UH
 lo0
:::0.0.0.0/96 ::1   UGRS
 lo0
2a01:4f8:131:50a1::/64link#1U
re0
2a01:4f8:131:50a1::2  link#1UHS
lo0
fe80::/10 ::1   UGRS
 lo0
fe80::%re0/64 link#1U
re0
fe80::6e62:6dff:fe7c:2c98%re0 link#1UHS
lo0
fe80::%lo0/64 link#2U
lo0
fe80::1%lo0   link#2UHS
lo0
fe80::%tun0/64link#8U
 tun0
fe80::6e62:6dff:fe7c:2c98%tun0link#8UHS
lo0
ff01::%re0/32 2a01:4f8:131:50a1::2  U
re0
ff01::%lo0/32 ::1   U
lo0
ff01::%tun0/32fe80::6e62:6dff:fe7c:2c98%tun0 U
 tun0
ff02::/16 ::1   UGRS
 lo0
ff02::%re0/32 2a01:4f8:131:50a1::2  U
re0
ff02::%lo0/32 ::1   U
lo0
ff02::%tun0/32fe80::6e62:6dff:fe7c:2c98%tun0 U
 tun0

ping6 ::1
PING6(56=40+8+8 bytes) ::1 --> ::1
16 bytes from ::1, icmp_seq=0 hlim=64 time=0.050 ms

ping6 2a01:4f8:131:50a1::2
PING6(56=40+8+8 bytes) 2a01:4f8:131:50a1::2 --> 2a01:4f8:131:50a1::2
16 bytes from 2a01:4f8:131:50a1::2, icmp_seq=0 hlim=64 time=0.055 ms


ping6 2001:4860:4860::
PING6(56=40+8+8 bytes) 2a01:4f8:131:50a1::2 --> 2001:4860:4860::
ping6: sendmsg: Operation not permitted
ping6: wrote 2001:4860:4860:: 16 chars, ret=-1

traceroute6 2001:4860:4860::
traceroute6 to 2001:4860:4860:: (2001:4860:4860::) from
2a01:4f8:131:50a1::2, 64 hops max, 12 byte packets
sendto: Operation not permitted
 1 traceroute6: wrote 2001:4860:4860:: 12 chars, ret=-1
 2a01:4f8:131:50a1::2  0.065 mssendto: Operation not permitted

I have in pf.conf
pass quick on $ext_if proto ipv6

I cant understand what i am missing, still learning the ropes of ipv6.

could anyone help me getting this up and running?
___
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"