From owner-freebsd-net@FreeBSD.ORG Thu Jul 9 03:47:09 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 390DA10656C2 for ; Thu, 9 Jul 2009 03:47:09 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.216.172]) by mx1.freebsd.org (Postfix) with ESMTP id F3F978FC0A for ; Thu, 9 Jul 2009 03:47:08 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by mail-px0-f172.google.com with SMTP id 2so1496230pxi.3 for ; Wed, 08 Jul 2009 20:47:08 -0700 (PDT) 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:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:organization:x-operation-sytem; bh=aJ9jvt1pEK+0Z7EqIAfByQkkGRD1bwJARifdtMBIO7s=; b=rf4Sx4u+/suzrVT6ED89TzgWxX1NFuiIC60B+tYfX/aeiIetFHK8U7ZmdFE6YP+Pfl 6LBNt3frsQbI13MMtxKy6Pk6QulI2I5oWlHa6+pLxWqN627ZsUBHbXDU8OIrbn4Kw0a9 e0ph3v+hpIdpWWFqcntJDJAfif8GWAuwisufI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent:organization:x-operation-sytem; b=rEzudAiEVF4ueJrOLsI6cqxPfclBnfDOehHF+qhOs7fYqsyI0yFUPJqFyO3M+kojBH KNAjtz41zIT3/H/KmmJFd23lnqY6K9xwiDLNTN1++zZWopUx3NoPQbU3akaG7UBGA2Gn ySF1pNIyWa7hqGe1RfR+pFTolnkUwIyEcYtjA= Received: by 10.140.141.21 with SMTP id o21mr141837rvd.92.1247107016851; Wed, 08 Jul 2009 19:36:56 -0700 (PDT) Received: from weongyo ([114.111.62.249]) by mx.google.com with ESMTPS id c20sm3384365rvf.31.2009.07.08.19.36.54 (version=SSLv3 cipher=RC4-MD5); Wed, 08 Jul 2009 19:36:55 -0700 (PDT) Received: by weongyo (sSMTP sendmail emulation); Thu, 9 Jul 2009 11:36:51 +0900 From: Weongyo Jeong Date: Thu, 9 Jul 2009 11:36:51 +0900 To: Nikos Vassiliadis Message-ID: <20090709023651.GA1553@weongyo.cdnetworks.kr> Mail-Followup-To: Nikos Vassiliadis , freebsd-net@freebsd.org References: <4A43386D.80500@gmx.com> <20090625103420.GD31161@weongyo.cdnetworks.kr> <4A436A8A.1000405@gmx.com> <20090626041246.GE31161@weongyo.cdnetworks.kr> <4A461AF9.7040900@gmx.com> <20090629032520.GA1138@weongyo.cdnetworks.kr> <4A4880EF.5010206@gmx.com> <4A4E2873.3010501@gmx.com> <20090706043747.GD1138@weongyo.cdnetworks.kr> <4A531A94.40701@gmx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A531A94.40701@gmx.com> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: freebsd-net@freebsd.org Subject: Re: ndis and USB wirelless ethernet X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Weongyo Jeong List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jul 2009 03:47:09 -0000 On Tue, Jul 07, 2009 at 12:51:16PM +0300, Nikos Vassiliadis wrote: > Weongyo Jeong wrote: > >I'm happy to see your device is successfully associated with AP. > >However it seems it's a bad news that you sometimes meet crashes. Does > >a random crash mean a OS hang (e.g. could not type any keys) or no more > >work of network operations? > > It hangs, I cannot use the keyboard and I have to power-cycle it. > It can happen after some time downloading and uploading. It hangs > after 5 to 30 minutes of heavy traffic. By heavy traffic, I mean > the maximum I can get from this device, which is 50KBytes/sec. > > I am not sure what will happen if I let it idle for, let's say > one day, but I haven't had a single crash during times with > low activity, such as ssh traffic. > > >Frankly speaking, for both cases it looks I could not provide any > >solutions without backtraces unless I encountered same problems on my > >environment. It'd better if we can reproduce its problem easily. > > Unfortunately, I have no solid facts to show you. The only strange > thing I've seen and is consistent, is this: > > speed# vmstat -m | grep USBdev ; sleep 1 ; vmstat -m | grep USBdev ; > sleep 1 ; vmstat -m | grep USBdev > USBdev 53 4K - 267579 16,32,128,1024 > USBdev 53 4K - 267612 16,32,128,1024 > USBdev 53 4K - 267642 16,32,128,1024 > speed# > speed# vmstat -m | grep USBdev ; sleep 1 ; vmstat -m | grep USBdev ; > sleep 1 ; vmstat -m | grep USBdev > USBdev 53 4K - 268071 16,32,128,1024 > USBdev 53 4K - 268101 16,32,128,1024 > USBdev 53 4K - 268140 16,32,128,1024 > > And then with some traffic: > speed# ping -i 0.01 192.168.1.1 > /dev/null & > [1] 1777 > speed# vmstat -m | grep USBdev ; sleep 1 ; vmstat -m | grep USBdev ; > sleep 1 ; vmstat -m | grep USBdev > USBdev 53 4K - 270249 16,32,128,1024 > USBdev 58 4K - 271095 16,32,128,1024 > USBdev 56 4K - 272008 16,32,128,1024 > speed# vmstat -m | grep USBdev ; sleep 1 ; vmstat -m | grep USBdev ; > sleep 1 ; vmstat -m | grep USBdev > USBdev 54 4K - 279649 16,32,128,1024 > USBdev 57 4K - 280544 16,32,128,1024 > USBdev 54 4K - 281423 16,32,128,1024 > > I don't know how relevant is the above, but it seemed strange, > so I am posting it... It's a normal case that in implementation it allocates a memory buffer for transactions. So if it increases without any reduction it'd be a problem. regards, Weongyo Jeong