From owner-freebsd-stable@FreeBSD.ORG Fri Feb 27 03:56:00 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B2221065670; Fri, 27 Feb 2009 03:56:00 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id F1E898FC0A; Fri, 27 Feb 2009 03:55:59 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by rv-out-0506.google.com with SMTP id f6so869757rvb.43 for ; Thu, 26 Feb 2009 19:55:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent:organization :x-operation-sytem; bh=nLfCEgXpH65KTILS67Dx1sKhLWebB+oCwm7zGZpMges=; b=lADQBV2tao+T4pA0pJLaASafji/tsXe/iK4jQyL4XrwwQDCiowWNlC7SaPpiwh3rTd jLxG9DanfBkQb5bXAeKxicPUMDTaorJQhy9mV6Y0ZiogBFDo4zefIuRy+GrMPdXq3/kj skCCvBOIcceU8rT2FDS2FY/1sVpROps0xqpKo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent :organization:x-operation-sytem; b=o/8guoxP756Xzz5QzENaLZ3keCon7A+nZtszpHZE6Mw9/m+6sYtHXaaiPK0OXGiGvA OVpHiSiqb2fPNaEcKO7zmehUAd4HgT7UgrLFRaXLCQP+WfZX1I7vPNLbSuOVDuGIO3+3 aALB/ZQW/2k+ZBzYN23IrgUW7j8x3Krn8Bn28= Received: by 10.140.132.4 with SMTP id f4mr969179rvd.211.1235706959706; Thu, 26 Feb 2009 19:55:59 -0800 (PST) Received: from weongyo ([114.111.62.249]) by mx.google.com with ESMTPS id c20sm1689141rvf.1.2009.02.26.19.55.57 (version=SSLv3 cipher=RC4-MD5); Thu, 26 Feb 2009 19:55:59 -0800 (PST) Received: by weongyo (sSMTP sendmail emulation); Fri, 27 Feb 2009 12:55:32 +0900 From: Weongyo Jeong Date: Fri, 27 Feb 2009 12:55:32 +0900 To: Bengt Ahlgren Message-ID: <20090227035532.GC72273@weongyo.cdnetworks.kr> References: <49A61894.5040804@fusiongol.com> <20090226045340.GC70144@weongyo.cdnetworks.kr> <49A74A21.1050109@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49A74A21.1050109@freebsd.org> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: Nathan Butcher , Sam Leffler , freebsd-stable@freebsd.org Subject: Re: ural driver stalls under FreeBSD7.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Weongyo Jeong List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2009 03:56:00 -0000 On Thu, Feb 26, 2009 at 06:04:17PM -0800, Sam Leffler wrote: > Bengt Ahlgren wrote: > >Weongyo Jeong writes: > > > >>On Thu, Feb 26, 2009 at 01:20:36PM +0900, Nathan Butcher wrote: > >> > >>>I have a Buffalo WLI-U2-KG54-AI wireless USB adaptor. > >>>It has been malfunctioning for quite a while under FreeBSD7.0 and 7.1 > >>> > >>>Typically, It works for a while until eventually it stalls data > >>>transfers completely. It always seems to do this after an unspecified > >>>amount of time. > >>> > >>>I know the hardware isn't at fault because the device works fine under > >>>Linux. > >>> > >>Could you please check that `ifconfig -bgscan' disabling the > >>background scan helps your symptom? > > > >The above sounds like the same problem as this: > > > >http://lists.freebsd.org/pipermail/freebsd-mobile/2009-February/011376.html > >http://lists.freebsd.org/pipermail/freebsd-mobile/2009-February/011343.html > > > >The problem is in the background scanning logic in sys/net80211. > > I don't see how you come to this conclusion. ural is a totally > different driver than ath and so far as I can recall you never found the > cause for your problem w/ ath. Most of the usb wireless drivers do a > haphazard job of synchronizing async tasks like bg scan with the > foreground tx/rx processing. This can lead to firmware and/or usb > issues. ath does not have these issues but I am aware of at least one > problem w/ bg scanning in ath under RELENG_7 (that is not present in HEAD). I agree with sam because I saw some cases like stalls during background scanning that most of them I think it's caused by H/W miss-operation or miss-configuration by mistakes of driver. regards, Weongyo Jeong