From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 3 00:54:33 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 37AD4371; Wed, 3 Apr 2013 00:54:33 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) by mx1.freebsd.org (Postfix) with ESMTP id D55C481A; Wed, 3 Apr 2013 00:54:32 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id v28so463448qcm.10 for ; Tue, 02 Apr 2013 17:54:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JSwGRKhAQpbQPDCf1qhsvYNImcVmA7wBCwKQO6/oLCE=; b=OGv/Iv1E2fQYzHuD0v5CdWuidEGpAdZvOcArXluvAT8RlRCacUmLphmO93NrWIteiv WgbogAQ7qlowub5R6TP87AtFFm/23LCnWxLx4gNiUvh+G8nXFc01OZ3ucLTPEXflHOsJ T0QIkuIsoy7FUdDCzt+W/2Jy36QZAcnZ7794+2KERwxnLAu9KMgZXMkTKNaRsAbJGeWd cOe0Gi96l3mxeE61alHBkWZ1/jhUGZZS5pd/Wfv8Hc9UqmOwY7I67Qp+fpKD7EDW1Tt5 GE+UTEJvU/v2Bq+6rntQMTjUOR8b4qKLvGLTmmvTOgd8hSe2BHG7XmNiWbWydWvpC8oQ FUFg== X-Received: by 10.229.69.76 with SMTP id y12mr6930458qci.123.1364950471700; Tue, 02 Apr 2013 17:54:31 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id k8sm4622782qej.2.2013.04.02.17.54.30 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 17:54:31 -0700 (PDT) Message-ID: <515B7DBF.8070100@gmail.com> Date: Tue, 02 Apr 2013 19:54:23 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B7907.80705@gmail.com> <515B7B5F.8080400@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Apr 2013 00:54:33 -0000 Right now I'm at 62 bpages bounced, with it running in a loop every second listing hw.busdma. Right now it's half an hour of uptime, and when I did 4500 pings, I lost one packet. Quickly's relative. I mainly use ssh to access my FreeBSD machine, I don't recall the last time I ran X, which kind of pissed me off that I had to buy a video card for a console when the monitor's always off. Twelve gigs lost pretty fast, I'll try 9 to see if 8's a magic number. On 4/2/2013 7:46 PM, Adrian Chadd wrote: > On 2 April 2013 17:44, Joshua Isom wrote: >> I did get a couple bounced after pinging for a while via ssh, but only one >> ping packet dropped, so it should be good for anything tcp. > > So what, 8GB almost-but-not-quite worked? > > How much RAM do I need to ensure that things will break quickly? :) > > > > Adrian >