All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Hsu <ryanhsu@qca.qualcomm.com>
To: "Guilherme Íscaro" <cabelitostos@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Reporting a bug for QCA6174 802.11ac
Date: Thu, 23 Mar 2017 22:46:03 +0000	[thread overview]
Message-ID: <1490309165963.76201@qca.qualcomm.com> (raw)
In-Reply-To: <CAAf+CsD0bvwaB2pLLActv9XCimdNaWAjoS2ZU4WN1d-kt3rSDA@mail.gmail.com>

Let's start from the basic, could you provide the ftrace logs and also the AP model you're using? try without security or different phy mode to see if it would behave differently?

The last thing is, your previous logs only stuffed with the register access failure logs, can you share a full dmesg logs as well?

Ryan
________________________________________
From: Guilherme Íscaro <cabelitostos@gmail.com>
Sent: Wednesday, March 22, 2017 3:17 PM
To: Ryan Hsu
Cc: ath10k@lists.infradead.org
Subject: Re: Reporting a bug for QCA6174 802.11ac

Hi, unfortunately the problem happened with the new drivers and firmware. :[
I really don't know what to do anymore.....

thanks.

2017-03-22 10:56 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
> I've installed the new firmware/driver. I'll send a new email in some
> days to tell you guys if the new driver/firmware resolved the problem.
>
> Thanks for the help.
>
> 2017-03-21 15:58 GMT-03:00 Guilherme Íscaro <cabelitostos@gmail.com>:
>> Hello Ryan, Thanks for your response.
>>
>> My AP is in the same room that I use my notebook, it's right in front
>> of me. There's no specific scenario for this failure to happen.
>> Sometimes it does not happens for days, but sometimes it happens 3/4
>> times in the same day.
>> It looks like that there is not specific scenario, sometimes it
>> happens while I'm using firefox, sometimes it happens when my laptop
>> is "doing nothing". (Was it helpful?)
>>
>> I'm using WiFi 802.11n, 2.4ghz with AES.
>>
>> I'll try this new firmware/driver.
>>
>> Thanks.
>>
>>
>>
>> 2017-03-21 15:35 GMT-03:00 Ryan Hsu <ryanhsu@qca.qualcomm.com>:
>>> Iscaro,
>>>
>>> Not sure how exactly the issue and scenario of your usage.
>>>
>>> e.g how far the AP from you and is there any specific scenario you're seeing the failure open?
>>>
>>> Also would you mind try to pick up the latest firmware to see if that help?
>>> https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4
>>>
>>> With the latest firmware, you might also need to get the latest driver backport package.
>>> http://buildbot.w1.fi/backports-wireless-testing/
>>>
>>> Ryan
>>>
>>>> -----Original Message-----
>>>> From: ath10k [mailto:ath10k-bounces@lists.infradead.org] On Behalf Of
>>>> Guilherme Íscaro
>>>> Sent: Monday, March 20, 2017 08:32 AM
>>>> To: ath10k@lists.infradead.org
>>>> Subject: Reporting a bug for QCA6174 802.11ac
>>>>
>>>> Hello everyone, I would like to report a bug for QCA6174.
>>>>
>>>> I use WiFi everyday, but from time to time I lose my connection. This might be
>>>> related to a firmware problem, because after I lose my connection the firmware
>>>> keeps flooding dmesg about problems.
>>>>
>>>> I have this problem since I  bought my laptop (which was last year) and I do
>>>> regular updates in my system.
>>>>
>>>> P.S: dmest output attached.
>>>>
>>>> My system:
>>>>
>>>> Dist: Arch Linux.
>>>> Kernel: 4.10.3-1
>>>> Linux-firmware version: 20170309.695f2d6-1 (commit 695f2d6d82173f4e...
>>>> from linux-firmware)
>>>> Board: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac
>>>> Wireless Network Adapter (rev 32)
>>>>
>>>>
>>>> Please, let me know if I should provide more info.
>>>>
>>>> Thanks.

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

  reply	other threads:[~2017-03-23 22:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 15:31 Reporting a bug for QCA6174 802.11ac Guilherme Íscaro
2017-03-21 18:35 ` Ryan Hsu
2017-03-21 18:58   ` Guilherme Íscaro
2017-03-22 13:56     ` Guilherme Íscaro
2017-03-22 22:17       ` Guilherme Íscaro
2017-03-23 22:46         ` Ryan Hsu [this message]
2017-03-23 23:11           ` Guilherme Íscaro
2017-03-28 17:45             ` Guilherme Íscaro
2017-03-31 11:12               ` Kalle Valo
2017-03-31 15:11                 ` Adrian Chadd
2017-04-05 19:48                   ` Guilherme Íscaro
2017-04-06  3:52                     ` Kalle Valo

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=1490309165963.76201@qca.qualcomm.com \
    --to=ryanhsu@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=cabelitostos@gmail.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.