From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian.chadd@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: BAR error, failed to get chip id.
Date: Wed, 22 Jan 2014 16:37:04 -0800 [thread overview]
Message-ID: <52E06430.5060408@candelatech.com> (raw)
In-Reply-To: <CAJ-VmokveU-WxqboRhdagLwp2E2o-Bic7Pd4LvHaj7TX+rBnYA@mail.gmail.com>
On 01/22/2014 04:10 PM, Adrian Chadd wrote:
> Tgis is rev 2.0 right? I recall reset bugs in 1.0 that had the pcie bits not setup right by the firmware after a cold reset.
I'm using a rev 2 development NIC (CUS223, I think..haven't cracked the
machine open in a while).
I usually get about 1-3 module reloads before the system either totally
freezes or prints out the info below (and fails to load the driver),
requiring reboot of the system.
I have been working on other features and bugs and have been ignoring
these lockups, but now I'm a bit more interested in trying to resolve
them...
Thanks,
Ben
>
> Adrian
>
> On Jan 22, 2014 3:34 PM, "Ben Greear" <greearb@candelatech.com <mailto:greearb@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.
>
>
> 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@candelatech.com <mailto:greearb@candelatech.com>>
> Candela Technologies Inc http://www.candelatech.com
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org <mailto:ath10k@lists.infradead.org>
> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-01-23 0:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 20:33 BAR error, failed to get chip id Ben Greear
2014-01-22 21:49 ` Dave Taht
2014-01-22 21:54 ` Ben Greear
[not found] ` <CAJ-VmokveU-WxqboRhdagLwp2E2o-Bic7Pd4LvHaj7TX+rBnYA@mail.gmail.com>
2014-01-23 0:37 ` Ben Greear [this message]
[not found] ` <CAJ-VmomSpAyESOnBdUHUf__=HC1wp-=otH9-v2PNJbmzLQ6mxg@mail.gmail.com>
2014-01-23 0:49 ` Ben Greear
2014-01-23 6:05 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52E06430.5060408@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian.chadd@gmail.com \
--cc=ath10k@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox