From owner-freebsd-mobile@FreeBSD.ORG Sat Jul 29 19:03:24 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04ADF16A55E for ; Sat, 29 Jul 2006 19:03:24 +0000 (UTC) (envelope-from rsf@ns.live555.com) Received: from ns.live555.com (ns.live555.com [66.80.62.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B1D343EC8 for ; Sat, 29 Jul 2006 19:02:56 +0000 (GMT) (envelope-from rsf@ns.live555.com) Received: from ns.live555.com (localhost.live555.com [127.0.0.1]) by ns.live555.com (8.13.6/8.13.6) with ESMTP id k6TJ2t7s019791 for ; Sat, 29 Jul 2006 12:02:55 -0700 (PDT) (envelope-from rsf@ns.live555.com) Received: (from rsf@localhost) by ns.live555.com (8.13.6/8.13.6/Submit) id k6TJ2tGU019782; Sat, 29 Jul 2006 12:02:55 -0700 (PDT) (envelope-from rsf) Mime-Version: 1.0 Message-Id: In-Reply-To: <44CB8896.30904@errno.com> References: <44CB8179.5050503@errno.com> <44CB8896.30904@errno.com> Date: Sat, 29 Jul 2006 12:02:43 -0700 To: freebsd-mobile@freebsd.org From: Ross Finlayson Content-Type: text/plain; charset="us-ascii" ; format="flowed" Subject: Re: Ongoing problems with the "ath" interface - is any relief in sight?? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2006 19:03:24 -0000 >BTW, the fact the subsequent reset failed with error 3 (HAL_EIO in ah.h) >indicates you've got something more going on. But since you didn't >provide any details on what you're doing it's hard to say if you've got >a hardware problem. Presumably you've done basic things like swap out >parts and/or try to reproduce the problem in a controlled environment. Yes, I have seen these errors occur on two separate systems, with two different types of WiFi network hardware (but both using Atheros chips): kernel: ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) kernel: ath0: mem 0xe1020000-0xe102ffff irq 10 at device 18.0 on pci0 kernel: ath0: Ethernet address: 00:80:48:3c:6c:00 kernel: ath0: mac 10.5 phy 6.1 radio 6.3 kernel: ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) kernel: ath0: mem 0x41400000-0x4140ffff irq 5 at device 9.0 on pci0 kernel: ath0: Ethernet address: 00:13:46:98:3b:13 kernel: ath0: mac 7.9 phy 4.5 radio 5.6 > > "stuck beacon" means the tx dma of the beacon frame failed to complete >> in a full beacon interval. Diagnosing such a problem requires >> understanding why dma failed to complete. This usually involves >> checking the dma descriptor for clues and/or looking at other >> h/w-related state. If you have a "memory smash" then you will see it in >> the descriptor contents--but I doubt it. In my experience this problem >> is usually caused by feeding bogus data to the dma engine that causes it >> to lockup but the problem in general is very complicated and not > > something I can diagnose remotely. Is there any patch that I could make to the code that could provide (for you) more informative error output when these errors occur? Ross.