BAR error, failed to get chip id.

[Dave Taht]

On Wed, Jan 22, 2014 at 3:33 PM, Ben Greear <greearb at candelatech.com> 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.

>
>
> Kernel 3.13.0-rc8-wl-ath+ on an x86_64 (ttyS0)
>
> ct523-9292 login: ath10k_pci 0000:05:00.0: BAR 0: error updating (0xf4400004 != 0xffffffff)
> ath10k_pci 0000:05:00.0: BAR 0: error updating (high 0x000000 != 0xffffffff)
> ath10k: Failed to get chip id: -110
>
>
> After this, it takes a power cycle to get the system working again.
>
> Anyone seen similar?
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>
>
> _______________________________________________
> ath10k mailing list
> ath10k at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html