From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Adrian Chadd <adrian.chadd@gmail.com>, ath10k@lists.infradead.org
Subject: Re: BAR error, failed to get chip id.
Date: Thu, 23 Jan 2014 08:05:22 +0200 [thread overview]
Message-ID: <87iotb9qsd.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <52E06430.5060408@candelatech.com> (Ben Greear's message of "Wed, 22 Jan 2014 16:37:04 -0800")
Ben Greear <greearb@candelatech.com> writes:
> 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...
I was told that CUS223 has a problem with cold resets. Whenever the host
issues a cold reset occasionally voltage in one of the board component's
goes too down and causes PCI errors. I think that's what you are seeing.
The workaround is to use warm resets, but we are still having some
problems with that after firmware crashes. Hopefully we can send patches
next week.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-01-23 6:06 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
[not found] ` <CAJ-VmomSpAyESOnBdUHUf__=HC1wp-=otH9-v2PNJbmzLQ6mxg@mail.gmail.com>
2014-01-23 0:49 ` Ben Greear
2014-01-23 6:05 ` Kalle Valo [this message]
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=87iotb9qsd.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=adrian.chadd@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.