From nobody@FreeBSD.org  Tue Apr 15 00:31:42 2008
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 070AD106564A
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 15 Apr 2008 00:31:42 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id EA8C88FC12
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 15 Apr 2008 00:31:41 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m3F0VZNE082581
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 15 Apr 2008 00:31:35 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.2/8.14.1/Submit) id m3F0VZ0G082580;
	Tue, 15 Apr 2008 00:31:35 GMT
	(envelope-from nobody)
Message-Id: <200804150031.m3F0VZ0G082580@www.freebsd.org>
Date: Tue, 15 Apr 2008 00:31:35 GMT
From: Paul <paul@gtcomm.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: tcpdump on lagg interface during high pps wedges netcode
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         122780
>Category:       kern
>Synopsis:       [lagg] tcpdump on lagg interface during high pps wedges netcode
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-net
>State:          feedback
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Apr 15 00:40:01 UTC 2008
>Closed-Date:    
>Last-Modified:  Mon Jan 18 20:55:20 UTC 2010
>Originator:     Paul
>Release:        7.0 Release
>Organization:
GTCOMM
>Environment:
FreeBSD x 7.0-RELEASE FreeBSD 7.0-RELEASE #2: Fri Apr  4 13:11:07 EDT 2008     root@x:/usr/obj/usr/src/sys/ROUTER  amd64

>Description:
Sending a rate of 200kpps through or to lagg interface and then using
the tcpdump command causes the entire network stack to have issues on
all interfaces including ones that use other drivers eventually causing
machine to be unaccessable on the network.  (ex.  tcpdump -n -i lagg0 )

Lagg interface is on EM driver using two EM ports, example:
ifconfig lagg0 laggproto lacp laggport em4 laggport em5  

Port on the other end is either Cisco switch or another FREEBSD machine
with lagg interface.  Both have same problems.

kern.hz=4000
kern.polling.enable=1
kern.polling.reg_frac=400
kern.polling.user_frac=20
kern.polling.idle_poll=1
kern.polling.each_burst=1000
kern.polling.burst_max=8000

EM is PCI-E 4x 4 port  Intel Server card, copper ports

I would be happy to provide any more information.  dmesg reports nothing
when it happens and I did not get a chance to do much more debugging on
the issue.

I do have a second issue with this setup which may or may not be related.
With polling enabled, the machine panics on a spin lock when rebooting,
during the shutdown process.  


>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-amd64->freebsd-net 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Tue Apr 15 02:47:08 UTC 2008 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=122780 

From: Paul <paul@gtcomm.net>
To: bug-followup@FreeBSD.org, paul@gtcomm.net
Cc:  
Subject: Re: amd64/122780: [lagg] tcpdump on lagg interface during high pps
 wedges netcode
Date: Wed, 16 Apr 2008 18:40:53 -0400

 It seems to happen while attaching the BPF to the interface.  I ran a 
 tcpdump first, and then started the traffic and I saw the traffic in 
 tcpdump, but after traffic is going and then issuing tcpdump command, 
 instantly locks.
 
 I also just had a lockup with adding and removing ospf networks in 
 quagga ospfd where the entire machine froze when I removed a network 
 (from a lagg interface) , I could not repeat this problem. :/
 
 

From: Ed Maste <emaste@freebsd.org>
To: bug-followup@FreeBSD.org, paul@gtcomm.net
Cc:  
Subject: Re: kern/122780: [lagg] tcpdump on lagg interface during high pps wedges netcode
Date: Mon, 17 Aug 2009 16:14:13 -0400

 Can you retest on recent 7.x or HEAD?  I think there have been BPF changes
 to address this issue.
 
 -Ed

From: Paul <paul@gtcomm.net>
To: Ed Maste <emaste@freebsd.org>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/122780: [lagg] tcpdump on lagg interface during high pps
 wedges netcode
Date: Sun, 30 Aug 2009 23:33:59 -0400

 Yes next time I reboot one of the routers I can test it.  Have you guys 
 made any progress on SMP routing yet?
 
 
 Ed Maste wrote:
 > Can you retest on recent 7.x or HEAD?  I think there have been BPF changes
 > to address this issue.
 >
 > -Ed
 >
 >   
 
 -- 
 GloboTech Communications
 Phone: 1-514-907-0050 x 215
 Toll Free: 1-(888)-GTCOMM1
 Fax: 1-(514)-907-0750
 paul@gtcomm.net
 http://www.gtcomm.net 
 
State-Changed-From-To: open->feedback 
State-Changed-By: emaste 
State-Changed-When: Mon Jan 18 20:54:42 UTC 2010 
State-Changed-Why:  
Results of testing on more recent 7.x (or newer branch) requested 

http://www.freebsd.org/cgi/query-pr.cgi?pr=122780 
>Unformatted:
