All of lore.kernel.org
 help / color / mirror / Atom feed
From: mindfsck <mindfsck@gmail.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Rate marked as a VHT rate but data is invalid: MCS: 10, NSS: 2
Date: Wed, 06 May 2015 20:42:30 +0200	[thread overview]
Message-ID: <554A6096.1090501@gmail.com> (raw)
In-Reply-To: <554A5CAF.7040105@gmail.com>

BTW - after my last mail, I left the laptop as is and talked 10min with 
my wife.
Suddenly my right pocket trouser got hot.
There is a Moto G mobile inside unhappily connecting to my AP and 
disconnecting again all the time to no end :-)
I never saw this behavior before, it happens only when running this 
ath10k master kernel ;-)

mindfsck

On 06.05.2015 20:25, mindfsck wrote:
>
> Hi Michal,
>
> On 05.05.2015 07:05, Michal Kazior wrote:
>>> Here is the kernel log:
>>> -- 
>>> [    5.319175] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 
>>> irq_mode
>>> 0 reset_mode 0
>>> [    5.505523] ath10k_pci 0000:03:00.0: Direct firmware load for
>>> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
>>> [    5.505773] ath10k_pci 0000:03:00.0: Direct firmware load for
>>> ath10k/QCA6174/hw2.1/board-pci-168c:003e:11ad:0804.bin failed with 
>>> error -2
>>> [    5.505775] ath10k_pci 0000:03:00.0: failed to load spec board file,
>>> falling back to generic: -2
>>> [    5.505946] ath10k_pci 0000:03:00.0: Direct firmware load for
>>> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
>>> [    5.505948] ath10k_pci 0000:03:00.0: could not fetch firmware file
>>> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
>>>
>>> ...
>>>
>>> [   10.315505] ahci 0000:00:1f.2: port does not support device sleep
>>> [   14.314165] wlan1: authenticate with 00:1b:2f:61:b5:e8
>>> [   14.391351] wlan1: send auth to 00:1b:2f:61:b5:e8 (try 1/3)
>>> [   14.393075] wlan1: authenticated
>>> [   14.393232] ath10k_pci 0000:03:00.0 wlan1: disabling HT as 
>>> WMM/QoS is not
>>> supported by the AP
>>> [   14.393235] ath10k_pci 0000:03:00.0 wlan1: disabling VHT as 
>>> WMM/QoS is
>>> not supported by the AP
>>> [   14.394803] wlan1: associate with 00:1b:2f:61:b5:e8 (try 1/3)
>>> [   14.397284] wlan1: RX AssocResp from 00:1b:2f:61:b5:e8 (capab=0x431
>>> status=0 aid=3)
>>> [   14.420679] wlan1: associated
>>> [   14.420709] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
>>> [   14.552494] ------------[ cut here ]------------
>>> [   14.552520] WARNING: CPU: 2 PID: 0 at net/mac80211/rx.c:3578
>>> ieee80211_rx+0x26c/0x940 [mac80211]()
>>> [   14.552522] Rate marked as a VHT rate but data is invalid: MCS: 
>>> 10, NSS:
>>> 2
>> Either ath10k doesn't parse VHT-SIG properly or firmware reports
>> invalid VHT-SIG field. Can't say much without debug logs.
>>
>>
>> [...]
>>> [  210.696624] ath10k_pci 0000:03:00.0: firmware crashed! (uuid
>>> 14ca9744-7171-4365-9612-3f5ede30cbec)
>>> [  210.696635] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
>>> 0x003405ff, 168c:003e:11ad:0804 fallback) fw killer-n1525-fw api 4 
>>> htt 3.0
>>> wmi 4 cal otp max_sta 32
>>> [  210.696637] ath10k_pci 0000:03:00.0: debug 0 debugfs 1 tracing 1 
>>> dfs 0
>>> testmode 0
>>> [  210.698647] ath10k_pci 0000:03:00.0: firmware register dump:
>>> [  210.698648] ath10k_pci 0000:03:00.0: [00]: 0x05010000 0x00000000
>>> 0x0099BFAA 0x00000000
>>> [  210.698650] ath10k_pci 0000:03:00.0: [04]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.698651] ath10k_pci 0000:03:00.0: [08]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.698652] ath10k_pci 0000:03:00.0: [12]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.698653] ath10k_pci 0000:03:00.0: [16]: 0x00000000 0x00000000
>>> 0x00000000 0x0099BFAA
>>> [  210.698655] ath10k_pci 0000:03:00.0: [20]: 0x00000000 0x004018F0
>>> 0x00000000 0x00000000
>>> [  210.698656] ath10k_pci 0000:03:00.0: [24]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.698657] ath10k_pci 0000:03:00.0: [28]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.698658] ath10k_pci 0000:03:00.0: [32]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.698659] ath10k_pci 0000:03:00.0: [36]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.698660] ath10k_pci 0000:03:00.0: [40]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.698661] ath10k_pci 0000:03:00.0: [44]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.698663] ath10k_pci 0000:03:00.0: [48]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.698664] ath10k_pci 0000:03:00.0: [52]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.698665] ath10k_pci 0000:03:00.0: [56]: 0x00000000 0x00000000
>>> 0x00000000 0x00000000
>>> [  210.742185] ath10k_pci 0000:03:00.0: device has crashed during init
>>> [  210.766216] ath10k_pci 0000:03:00.0: device has crashed during init
>>> [  210.766218] ath10k_pci 0000:03:00.0: failed to wait for target 
>>> init: -70
>>> [  210.766650] ieee80211 phy0: Hardware restart was requested
>>> [  210.766663] ath10k_pci 0000:03:00.0: failed to synchronize 
>>> monitor vdev 1
>>> stop: -108
>>> [  210.766664] ath10k_pci 0000:03:00.0: failed to stop monitor vdev: 
>>> -108
>>> [  210.806322] ath10k_pci 0000:03:00.0: device has crashed during init
>>> [  210.830324] ath10k_pci 0000:03:00.0: device has crashed during init
>>> [  210.830327] ath10k_pci 0000:03:00.0: failed to wait for target 
>>> init: -70
>>> [  212.227905] ath10k_pci 0000:03:00.0: device successfully recovered
>>> [  216.232179] ath10k_pci 0000:03:00.0: firmware crashed! (uuid
>>> 9c23d4de-4420-4632-8665-62e3a7076276)
>>> [  216.232190] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
>>> 0x003405ff, 168c:003e:11ad:0804 fallback) fw killer-n1525-fw api 4 
>>> htt 3.0
>>> wmi 4 cal otp max_sta 32
>>> [  216.232192] ath10k_pci 0000:03:00.0: debug 0 debugfs 1 tracing 1 
>>> dfs 0
>>> testmode 0
>>> [  216.234197] ath10k_pci 0000:03:00.0: firmware register dump:
>> Either device reset didn't reset it entirely or there's a recurring
>> condition in driver which leads to the crash. Without debug logs I
>> can't help much. You'll need to compile ath10k with debug enabled and
>> gather traces with `trace-cmd` [1].
>>
>>
>> [1]: 
>> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug#tracing
>>
>>
>> Michał
> Already using your master kernel which had debug&trace enabled.
> I attached the trace.dat.
>
> Thanks,
>  mindfsck


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

  parent reply	other threads:[~2015-05-06 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 18:26 Rate marked as a VHT rate but data is invalid: MCS: 10, NSS: 2 mindfsck
2015-05-05  5:05 ` Michal Kazior
     [not found]   ` <554A5CAF.7040105@gmail.com>
2015-05-06 18:42     ` mindfsck [this message]
2015-05-07  6:38       ` Michal Kazior
2015-05-07  6:33     ` Michal Kazior

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=554A6096.1090501@gmail.com \
    --to=mindfsck@gmail.com \
    --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 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.