* BAR error, failed to get chip id.
@ 2014-01-22 20:33 Ben Greear
2014-01-22 21:49 ` Dave Taht
[not found] ` <CAJ-VmokveU-WxqboRhdagLwp2E2o-Bic7Pd4LvHaj7TX+rBnYA@mail.gmail.com>
0 siblings, 2 replies; 6+ messages in thread
From: Ben Greear @ 2014-01-22 20:33 UTC (permalink / raw)
To: ath10k
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>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BAR error, failed to get chip id.
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>
1 sibling, 1 reply; 6+ messages in thread
From: Dave Taht @ 2014-01-22 21:49 UTC (permalink / raw)
To: Ben Greear; +Cc: ath10k
On Wed, Jan 22, 2014 at 3:33 PM, Ben Greear <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.
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@candelatech.com>
> Candela Technologies Inc http://www.candelatech.com
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BAR error, failed to get chip id.
2014-01-22 21:49 ` Dave Taht
@ 2014-01-22 21:54 ` Ben Greear
0 siblings, 0 replies; 6+ messages in thread
From: Ben Greear @ 2014-01-22 21:54 UTC (permalink / raw)
To: Dave Taht; +Cc: ath10k
On 01/22/2014 01:49 PM, Dave Taht wrote:
> On Wed, Jan 22, 2014 at 3:33 PM, Ben Greear <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.
>
> 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 <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BAR error, failed to get chip id.
[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 6:05 ` Kalle Valo
0 siblings, 2 replies; 6+ messages in thread
From: Ben Greear @ 2014-01-23 0:37 UTC (permalink / raw)
To: Adrian Chadd; +Cc: ath10k
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BAR error, failed to get chip id.
[not found] ` <CAJ-VmomSpAyESOnBdUHUf__=HC1wp-=otH9-v2PNJbmzLQ6mxg@mail.gmail.com>
@ 2014-01-23 0:49 ` Ben Greear
0 siblings, 0 replies; 6+ messages in thread
From: Ben Greear @ 2014-01-23 0:49 UTC (permalink / raw)
To: Adrian Chadd; +Cc: ath10k
On 01/22/2014 04:41 PM, Adrian Chadd wrote:
> We need a pcie analyzer. Can you query its port to see what errors have shown up? Maybe we can toss some delay calls in the driver path when its detaching and
> attaching..
Do you have any suggestions for a pcie analyzer? I'd certainly consider
buying one...and maybe sending it to someone who could actually use it :)
Next time I see the BAR thing I'll see if I can find any info about
PCIe errors.
Thanks,
Ben
>
> Adrian
>
> On Jan 22, 2014 7:37 PM, "Ben Greear" <greearb@candelatech.com <mailto:greearb@candelatech.com>> wrote:
>
> 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> <mailto: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> <mailto: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> <mailto:ath10k@lists.infradead.org <mailto:ath10k@lists.infradead.org>>
> > http://lists.infradead.org/mailman/listinfo/ath10k
> >
>
>
> --
> Ben Greear <greearb@candelatech.com <mailto:greearb@candelatech.com>>
> Candela Technologies Inc http://www.candelatech.com
>
--
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BAR error, failed to get chip id.
2014-01-23 0:37 ` Ben Greear
[not found] ` <CAJ-VmomSpAyESOnBdUHUf__=HC1wp-=otH9-v2PNJbmzLQ6mxg@mail.gmail.com>
@ 2014-01-23 6:05 ` Kalle Valo
1 sibling, 0 replies; 6+ messages in thread
From: Kalle Valo @ 2014-01-23 6:05 UTC (permalink / raw)
To: Ben Greear; +Cc: Adrian Chadd, ath10k
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-01-23 6:06 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.