From owner-freebsd-current@FreeBSD.ORG Sun Apr 26 22:07:39 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B0091065672 for ; Sun, 26 Apr 2009 22:07:39 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 3FC588FC19 for ; Sun, 26 Apr 2009 22:07:39 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 4B0BF73098; Sun, 26 Apr 2009 23:57:40 +0200 (CEST) Date: Sun, 26 Apr 2009 23:57:40 +0200 From: Luigi Rizzo To: Maxim Ignatenko Message-ID: <20090426215740.GA33188@onelab2.iet.unipi.it> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: [dummynet] Several queues connected to one pipe: "dummynet: OUCH! pipe should have been idle!" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Apr 2009 22:07:39 -0000 On Sun, Apr 26, 2009 at 05:32:45PM +0300, Maxim Ignatenko wrote: > Hi, > > I have next dummynet configuration: > > ipfw pipe 3 bw 3Mbit/s > ipfw queue 10 config pipe 3 weight 10 mask src-ip 0xffffffff > ipfw queue 11 config pipe 3 weight 10 mask dst-ip 0xffffffff > > Two queues for different traffic directions connected to one pipe. > After update to r191410 my /var/log/messages filled with: > Apr 24 16:33:31 imax kernel: dummynet: OUCH! pipe should have been idle! > Apr 24 16:33:59 imax last message repeated 8 times > Apr 24 16:35:53 imax last message repeated 519 times > Apr 24 16:38:55 imax last message repeated 50 times could you give us a few more details on the branch you are using (HEAD or RELENG_7 ?) and what svn revision did you use before the update (which did not show the error) ? thanks luigi