From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 21 16:17: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]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5F076723; Sat, 21 Dec 2013 16:17:33 +0000 (UTC) Received: from mail-qe0-x22a.google.com (mail-qe0-x22a.google.com [IPv6:2607:f8b0:400d:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0D57F1FD4; Sat, 21 Dec 2013 16:17:32 +0000 (UTC) Received: by mail-qe0-f42.google.com with SMTP id b4so3679425qen.29 for ; Sat, 21 Dec 2013 08:17:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=03yaTT7S/VGO5jS1pt2CiSR2d/idLzjB1giORk/So04=; b=0H7aM+mIvnZ8vxkfdfl93lFMA1dxQgBy5bXh/aWsgp1w3iivVxjkBe57mWr6RBk092 1USYi1nFwzU9sTOiqOBdgBbULhuVjSu0G2o0v1LSy95+cpyOHiZcEwaeSz3vMRSew2vN cEejAJijib3hM2E44lT34e76js3t3DTLx/GLQTNVrQk+qmK9M6MD9p1McFTvk/w7u/v3 suCUz61P1fWmM4a5tRljMtKCUqSw3BUy4Jlne9NRZA4OokcYGuKgQ4/4cUDXktes7Jby S/2qKT/XpMAj+x43REhm0E2RqydWQ2K/Yg5TeOrZkCHWkMJfLVI3PcQC/STuPmAPkln5 Xccw== MIME-Version: 1.0 X-Received: by 10.229.122.195 with SMTP id m3mr25714276qcr.7.1387642652191; Sat, 21 Dec 2013 08:17:32 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Sat, 21 Dec 2013 08:17:32 -0800 (PST) In-Reply-To: <20131221023924.GK3148@glenbarber.us> References: <20131221023558.GJ3148@glenbarber.us> <20131221023924.GK3148@glenbarber.us> Date: Sat, 21 Dec 2013 08:17:32 -0800 X-Google-Sender-Auth: lg6H5DizGuBQattAGtsWU5S3sDE Message-ID: Subject: Re: "disappearing" ath(4) From: Adrian Chadd To: Glen Barber Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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: Sat, 21 Dec 2013 16:17:33 -0000 Hi so as I said to glen on IRC. The first possible issue here is that the NIC just disappears for some reason and all register reads are 0xffffffff. it's not that. The second possibility is that it's asleep - and no, NIC reads aren't showing 0xdeadc0de, 0xdeadbeef, etc. So no, it's not that. The fact that calibration fails like it does tends to indicate there's some kind of noise spur from somewhere that's pissing the NIC off. It's difficult to establish that without writing code to do capture/dump the raw ADC samples. He's also recently opened up his laptop and fiddled around. he's going off to do some more testing. -a On 20 December 2013 18:39, Glen Barber wrote: > On Fri, Dec 20, 2013 at 09:35:58PM -0500, Glen Barber wrote: >> Hi, >> >> Since last upgrade, it seems every few days (it seems roughly every >> 2 days), my ath(4) disappears, or more specifically, "falls off" enough >> to be unusable. >> > > Adrian pointed out that I forgot to include actually relevant > information. > > Machine runs .0-CURRENT r258761, the wireless card info from dmesg.boot > is: > > ath0: mem 0xde800000-0xde80ffff irq 17 at device 0.0 on > pci2 > ath0: [HT] enabling HT modes > ath0: [HT] 1 stream STBC receive enabled > ath0: [HT] 1 RX streams; 1 TX streams > ath0: AR9285 mac 192.2 RF5133 phy 14.0 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > Glen >