From owner-freebsd-current@FreeBSD.ORG Wed Sep 30 06:08:37 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 5DD10106566B; Wed, 30 Sep 2009 06:08:37 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id 8B86E8FC0C; Wed, 30 Sep 2009 06:08:36 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=EONtiXv_LWnWky7dZu0A:9 a=Vi2w8v1TNhgi9gMX4SiAiswxyNIA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1321992139; Wed, 30 Sep 2009 08:08:34 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Wed, 30 Sep 2009 08:09:18 +0200 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <86051.1254232666@critter.freebsd.dk> <4AC26052.7010303@freebsd.org> In-Reply-To: <4AC26052.7010303@freebsd.org> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909300809.19538.hselasky@c2i.net> Cc: Lawrence Stewart , Poul-Henning Kamp Subject: Re: if_rum dies on transmit... 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, 30 Sep 2009 06:08:37 -0000 On Tuesday 29 September 2009 21:30:26 Lawrence Stewart wrote: > Poul-Henning Kamp wrote: > > Has anybody else seen if_rum die when you try to transmit a file over > > a TCP connection ? > > > > If I try to print across the network, upload a file with ftp or anything > > else of that general tenor, if_rum seems to hang the output queue and > > stops transmitting packets. > > Yes I see the same thing with my D-LINK DWA-110 USB stick which shows up > as a rum device. According to Sam who had a quick look at the issue for > me when I first noticed it, the rum driver is in pretty bad shape and > should be expected to be flaky. > > I don't think the issue is specific to TCP connections though. I think > it's related to timing of inbound/outbound packets. I would frequently > trigger it when fetch ran as part of a port update, but it happened at > other seemingly random times as well. I suspect that TCP incoming data > and the outgoing ACKs might tickle the (locking? state machine?) bug > more effectively than other traffic mixes. > > > Restarting wpa_supplicant mostly resolves the issue, but it does not > > on its own discover the problem. > > > > According to tcpdump(8), packets are still received. > > > > Any ideas ? > > I've never done any driver work so I have no idea how to resolve the > issue, and just live with it randomly crapping out on me. I found > restarting wpa_supplicant to be a hit and miss way to fix it. The > easiest way to avoid panics or re occurrences was to pull the dongle, > wait 5 secs, reinsert and then recreate the wlan dev and start > wpa_supplicant. During testing I've seen similar issues. The rum hardware is not always reliable, but the kernel shouldn't panic ... --HPS