ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: theros@openmailbox.org
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k@lists.infradead.org
Subject: Re: QCA6174 seemingly randomly fails to wake
Date: Sun, 10 Jan 2016 00:26:49 +0100	[thread overview]
Message-ID: <1b49b497f4f2551430f7594521c9d9b0@openmailbox.org> (raw)
In-Reply-To: <CA+BoTQkmR95XqsKsjeDOR1b_+0srg8ydFgutfUG+M6C27XwrMw@mail.gmail.com>

Sorry about the late response, I was without my laptop due to an 
unrelated problem.

The patch seems to have fixed the issue - it didn't occur again after 
applying it. I did however use driver backports and applied the patch to 
those myself, as opposed to compiling the entire kernel from the 
repository you provided.

On 2015-11-04 08:30, Michal Kazior wrote:
> On 4 November 2015 at 01:00,  <theros@openmailbox.org> wrote:
>> Hello,
>> 
>> I am having issues with the ath10k driver and the Qualcomm Atheros 
>> QCA6174
>> network adapter. Seemingly randomly, the wireless connection on my 
>> laptop
>> stops working. dmesg outputs a long series of:
>> 
>> [11061.645929] ath10k_pci 0000:07:00.0: failed to wake target for 
>> write32 of
>> 0x0000025c at 0x0003543c: -110
> 
> This looks very similar to how QCA99X0 failed when PCI PS was enabled
> for the card:
> 
>   
> http://lists.infradead.org/pipermail/ath10k/2015-September/005939.html
> 
> As far as I know the reason of failure is not really understood and it
> simply was disabled to fix reliability.
> 
> It seems that QCA6174 suffers from this as well - at least on your
> platform. This is rather sad as we'll probably need to disable it by
> default for QCA6174 now as well which will increase power consumption
> a little bit.
> 
> 
>> Rarely a reboot fixes this and I can use the network adapter again, 
>> but more
>> often than not, after a reboot, there is no output related to ath10k 
>> in
>> dmesg and the laptop is behaving as if the network adapter is not 
>> present.
>> The adapter eventually starts working again - I have not noticed a 
>> specific
>> pattern, sometimes it is after a few hours, sometimes I couldn't get 
>> it
>> working for days.
>> 
>> I have tried thoroughly searching online but was unable to find 
>> anything
>> that would be of help. I do admit I am a little out of my depth here, 
>> but I
>> will happily provide any further information necessary in order to 
>> diagnose
>> and fix this.
>> 
>> I am on Xubuntu 15.10, kernel 4.2.0-16-generic.
> 
> Can you perhaps try compiling the kernel from:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git
> 
> with the following diff applied:
> 
> diff --git a/drivers/net/wireless/ath/ath10k/pci.c
> b/drivers/net/wireless/ath/ath10k/pci.c
> index 3fca200b986c..edf7a7637d88 100644
> --- a/drivers/net/wireless/ath/ath10k/pci.c
> +++ b/drivers/net/wireless/ath/ath10k/pci.c
> @@ -2968,7 +2968,7 @@ static int ath10k_pci_probe(struct pci_dev *pdev,
>         case QCA6164_2_1_DEVICE_ID:
>         case QCA6174_2_1_DEVICE_ID:
>                 hw_rev = ATH10K_HW_QCA6174;
> -               pci_ps = true;
> +               pci_ps = false;
>                 break;
>         case QCA99X0_2_0_DEVICE_ID:
>                 hw_rev = ATH10K_HW_QCA99X0;
> 
> and report back if this fixes the problem for you, please?
> 
> 
> Michał
> 
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2016-01-09 23:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04  0:00 QCA6174 seemingly randomly fails to wake theros
2015-11-04  7:30 ` Michal Kazior
2016-01-09 23:26   ` theros [this message]
2016-01-11 12:48     ` Michal Kazior
2016-01-11 16:21       ` Adrian Chadd

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=1b49b497f4f2551430f7594521c9d9b0@openmailbox.org \
    --to=theros@openmailbox.org \
    --cc=ath10k@lists.infradead.org \
    --cc=michal.kazior@tieto.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox