On 09/14/2017 05:11 PM, Adrian Chadd wrote:
On 14 September 2017 at 17:08, Ben Greear <[email protected]
<mailto:[email protected]>> wrote:
This is with our hacked 4.9 kernel, hacked firmware, and hacked driver (yah
me!).
Sometimes on reboots, in at least some systems, the device is not woken up
correctly,
and of course it never recovers.
Any idea if there is some way to retry this a few times to see if the device
can be recovered?
There were always weird cold reset races that necessitated a PCI bus reset of
the device. :( can you even see the device? do any of the registers work?
Can the cold reset be done on generic x86-64 hardware?
And, it shows up enough that the system probes it, at least. I guess no
infrastructure to speak of set up for this thing, so not sure how to
probe any registers.
Thanks,
Ben
-adrian
1177 Sep 14 17:00:09 ct524 kernel: ath10k driver, optimized for CT
firmware, probing pci device: 0x46.
1178 Sep 14 17:00:09 ct524 systemd[1]: Reached target Swap.
1179 Sep 14 17:00:09 ct524 kernel: ath10k_pci 0000:04:00.0: failed to wake
up device : -110
1180 Sep 14 17:00:09 ct524 kernel: ath10k_pci: probe of 0000:04:00.0 failed
with error -110
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
<http://lists.infradead.org/mailman/listinfo/ath10k>
--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
