From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.candelatech.com ([208.74.158.172] helo=ns3.lanforge.com) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1W65lG-0005x4-PM for ath10k@lists.infradead.org; Wed, 22 Jan 2014 21:55:03 +0000 Message-ID: <52E03E1F.8000102@candelatech.com> Date: Wed, 22 Jan 2014 13:54:39 -0800 From: Ben Greear MIME-Version: 1.0 Subject: Re: BAR error, failed to get chip id. References: <52E02B28.6020503@candelatech.com> In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Dave Taht Cc: ath10k@lists.infradead.org On 01/22/2014 01:49 PM, Dave Taht wrote: > On Wed, Jan 22, 2014 at 3:33 PM, Ben Greear wrote: >> >> I see this fairly often on module reload. Firmware is modified >> by me, based on 10.1.389, so if there are firmware fixes since then >> that address this problem I would not know of it. Kernel is ath-testing, >> with some local changes, but nothing pertaining to the pci code. > > I have had pci issues on an older atom box, not on a newer nuc. > > Can try that box again to see what happens. I'm using a core-i7 low-power system...has been rock solid for ath9k for a long time, for what that is worth. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k