Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Feb 2009 14:33:17 +0900
From:      Nathan Butcher <n-butcher@fusiongol.com>
To:        Weongyo Jeong <weongyo@freebsd.org>
Cc:        Sam Leffler <sam@freebsd.org>, freebsd-stable@freebsd.org
Subject:   Re: ural driver stalls under FreeBSD7.1
Message-ID:  <49A77B1D.70801@fusiongol.com>
In-Reply-To: <20090227035532.GC72273@weongyo.cdnetworks.kr>
References:  <49A61894.5040804@fusiongol.com> <20090226045340.GC70144@weongyo.cdnetworks.kr> <uh7hc2h13a7.fsf@P142.sics.se> <49A74A21.1050109@freebsd.org> <20090227035532.GC72273@weongyo.cdnetworks.kr>

next in thread | previous in thread | raw e-mail | index | archive | help
Weongyo Jeong wrote:
> On Thu, Feb 26, 2009 at 06:04:17PM -0800, Sam Leffler wrote:
>> Bengt Ahlgren wrote:
>>> Weongyo Jeong <weongyo.jeong@gmail.com> 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 <ifname> -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.

I'll do some testing without the bgscan and report back.
(haven't had time recently)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49A77B1D.70801>