BAR error, failed to get chip id.
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
Signature · 8 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 5 lines · Ben Greear
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.
Quoted 25 lines
Kernel 3.13.0-rc8-wl-ath+ on an
x86_64(ttyS0)ct523-9292 login:
ath10k_pci0000:05:00.0: BAR 0: error updating (0xf4400004!=0xffffffff)ath10k_pci0000:05:00.0: BAR 0: error updating (high0x000000!=0xffffffff)
ath10k: Failed to get chip id: -110After this, it takes a power cycle to get the system working again.
Anyone seen similar?
Thanks,
Ben--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
Signature · 8 lines
Dave Täht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 10 lines · Dave Taht
Quoted 5 lines · Ben Greear
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
Signature · 8 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 1 line · Adrian Chadd
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
Quoted 36 lines
Adrian
On Jan 22, 2014 3:34 PM, "Ben Greear" <[email protected] <mailto:[email protected]>> 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_pci0000:05:00.0: BAR 0: error updating (0xf4400004!=0xffffffff)ath10k_pci0000:05:00.0: BAR 0: error updating (high0x000000!=0xffffffff)
ath10k: Failed to get chip id: -110After this, it takes a power cycle to get the system working again.
Anyone seen similar?
Thanks,
Ben--
Ben Greear <[email protected] <mailto:[email protected]>> Candela Technologies Inc http://www.candelatech.com_______________________________________________
ath10k mailing list
[email protected] <mailto:[email protected]>
http://lists.infradead.org/mailman/listinfo/ath10k
Signature · 8 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 2 lines · Adrian Chadd
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
Quoted 66 lines
Adrian
On Jan 22, 2014 7:37 PM, "Ben Greear" <[email protected] <mailto:[email protected]>> 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" <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> 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 <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> > Candela Technologies Inc http://www.candelatech.com > > > _______________________________________________ > ath10k mailing list > [email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> > http://lists.infradead.org/mailman/listinfo/ath10k > -- Ben Greear <[email protected] <mailto:[email protected]>> Candela Technologies Inc http://www.candelatech.com
Signature · 8 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 6 lines · Ben Greear
Quoted 1 line · Adrian Chadd
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).
Quoted 7 lines
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.
Signature · 6 lines
Kalle Valo _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k