From owner-freebsd-current@FreeBSD.ORG Wed Apr 25 19:30:26 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3620B16A47D for ; Wed, 25 Apr 2007 19:30:26 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id E34C513C4C4 for ; Wed, 25 Apr 2007 19:30:25 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.65.120]) by phk.freebsd.dk (Postfix) with ESMTP id 4652717382; Wed, 25 Apr 2007 19:30:24 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.1/8.14.1) with ESMTP id l3PJUN48010664; Wed, 25 Apr 2007 19:30:24 GMT (envelope-from phk@critter.freebsd.dk) To: Max Laier From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 25 Apr 2007 21:24:38 +0200." <200704252124.45502.max@love2party.net> Date: Wed, 25 Apr 2007 19:30:23 +0000 Message-ID: <10663.1177529423@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: freebsd-current@freebsd.org Subject: Re: interface transmit-queue stalls 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: Wed, 25 Apr 2007 19:30:26 -0000 In message <200704252124.45502.max@love2party.net>, Max Laier writes: >On Wednesday 25 April 2007 20:43, Poul-Henning Kamp wrote: >> Am I the only one who sees transmit queue stalls in -current ? >> >> The interface, ath and tun so far, receive just fine, but transmits >> fail to even enter the queue. > >Do you get ENOBUFS for local sends? Are you sure it gets down to the=20 >interface queue (might stall in the socket layer already - does the=20 >forwarding path work?)? What's your net.isr.direct setting? All settings are default, no ALTQ and I don't have much debugging output, because I can't find a way to pull it out. ifconfig down/up seems to help. >Does an ifconfig down/up cycle help the situation? I don't see any=20 >commits in that area lately. Do you have ALTQ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.