Re: [jci...@ulb.ac.be: Listen queue overflow: 8 already in queue awaiting acceptance]

2014-10-03 Thread Julien Cigar
On Thu, Oct 02, 2014 at 04:36:49PM -0700, hiren panchasara wrote: > On Thu, Oct 2, 2014 at 11:19 AM, Julien Cigar wrote: > > On Thu, Oct 02, 2014 at 10:24:13AM -0700, hiren panchasara wrote: > >> On Thu, Oct 2, 2014 at 9:42 AM, Julien Cigar wrote: > >> > sorry for cross-posting, I'm forwarding th

Re: Detaching the slave from the lagg interface which has vlan on top of it, hits an panic

2014-10-03 Thread Gleb Smirnoff
On Fri, Oct 03, 2014 at 12:40:30AM +, Hariprasad S wrote: H> HI, H> H> Detaching the slave from the lagg interface which has vlan on top of it, hits an panic. H> Kernel used: FreeBSD HEAD r272051 H> H> Is anyone aware of this issue? Yes, melifaro@ demonstrated it recently. No fix available

Re: Detaching the slave from the lagg interface which has vlan on top of it, hits an panic

2014-10-03 Thread Alexander V. Chernikov
On 03.10.2014 04:40, Hariprasad S wrote: HI, Detaching the slave from the lagg interface which has vlan on top of it, hits an panic. Kernel used: FreeBSD HEAD r272051 Is anyone aware of this issue? Yes. What is happening here: We acquire lagg WLOCK to set new link layer address (due to "mast

Re: Detaching the slave from the lagg interface which has vlan on top of it, hits an panic

2014-10-03 Thread Gleb Smirnoff
On Fri, Oct 03, 2014 at 01:52:19PM +0400, Alexander V. Chernikov wrote: A> On 03.10.2014 04:40, Hariprasad S wrote: A> > HI, A> > A> > Detaching the slave from the lagg interface which has vlan on top of it, hits an panic. A> > Kernel used: FreeBSD HEAD r272051 A> > A> > Is anyone aware of this i

Re: TCP stack lock contention with short-lived connections

2014-10-03 Thread Julien Charbon
Hi, On 23/05/14 14:06, Julien Charbon wrote: > On 27/02/14 11:32, Julien Charbon wrote: >> On 07/11/13 14:55, Julien Charbon wrote: >>> On Mon, 04 Nov 2013 22:21:04 +0100, Julien Charbon >>> wrote: I have put technical and how-to-repeat details in below PR: kern/183659: TCP stack

Re: ixgbe(4) spin lock held too long

2014-10-03 Thread John Baldwin
On Thursday, October 02, 2014 06:40:21 PM Jason Wolfe wrote: > On Wed, Sep 10, 2014 at 8:24 AM, John Baldwin wrote: > > On Monday, September 08, 2014 03:34:02 PM Eric van Gyzen wrote: > > > On 09/08/2014 15:19, Sean Bruno wrote: > > > > On Mon, 2014-09-08 at 12:09 -0700, Sean Bruno wrote: > > > >>

Re: Addressing refcount issues in ip6_setdstifaddr and ip6_getdstifaddr routines.

2014-10-03 Thread Vedant Mathur
Andrey, Not a bad option. I saw you deleted the ip6_findaux routine which is used in route6_input. You have a ifdef around it. Whats that for? -Vedant On Wed, Oct 1, 2014 at 12:05 AM, Andrey V. Elsukov wrote: > On 30.09.2014 19:24, Vedant Mathur wrote: > > *Solution 2:* > > > > In ip6_setdsti

Re: Addressing refcount issues in ip6_setdstifaddr and ip6_getdstifaddr routines.

2014-10-03 Thread Andrey V. Elsukov
On 03.10.2014 18:03, Vedant Mathur wrote: > Andrey, > > Not a bad option. I saw you deleted the ip6_findaux routine which is > used in route6_input. You have a ifdef around it. Whats that for? Hi, It isn't my ifdef, it was here and never has been used in FreeBSD. Probably similar functional wil

Re: [jci...@ulb.ac.be: Listen queue overflow: 8 already in queue awaiting acceptance]

2014-10-03 Thread hiren panchasara
On Fri, Oct 3, 2014 at 1:01 AM, Julien Cigar wrote: > On Thu, Oct 02, 2014 at 04:36:49PM -0700, hiren panchasara wrote: >> On Thu, Oct 2, 2014 at 11:19 AM, Julien Cigar wrote: >> > On Thu, Oct 02, 2014 at 10:24:13AM -0700, hiren panchasara wrote: >> >> On Thu, Oct 2, 2014 at 9:42 AM, Julien Cigar

[Bug 193053] ixgbe(4) IXGBE_LEGACY_TX + ALTQ path broken

2014-10-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193053 Dan changed: What|Removed |Added CC||dan_...@yahoo.com --- Comment #10 from Dan

[Bug 193053] ixgbe(4) IXGBE_LEGACY_TX + ALTQ path broken

2014-10-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193053 --- Comment #11 from ncrog...@gmail.com --- (In reply to Dan from comment #10) > On 10.1-RC1, with the change below, I still get the dreaded "pfctl: igb1: > driver does not support altq". If ixgbe is targeted for 10.1-RELEASE, can > igb be

[Bug 193053] ixgbe(4) IXGBE_LEGACY_TX + ALTQ path broken

2014-10-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193053 --- Comment #12 from Dan --- (In reply to ncrogers from comment #11) > (In reply to Dan from comment #10) > > On 10.1-RC1, with the change below, I still get the dreaded "pfctl: igb1: > > driver does not support altq". If ixgbe is targeted

[Bug 193053] ixgbe(4) IXGBE_LEGACY_TX + ALTQ path broken

2014-10-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193053 --- Comment #13 from Dan --- Thanks, btw. That worked. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.or