ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: More than one ath10k NIC will not load (bisected)
Date: Fri, 23 Jan 2015 07:54:27 -0800	[thread overview]
Message-ID: <54C26EB3.7050805@candelatech.com> (raw)
In-Reply-To: <CA+BoTQmF+z5+HW+=xis7LPSmq6sSxn2ZuiJHGM83dAAftkN_sA@mail.gmail.com>



On 01/22/2015 10:43 PM, Michal Kazior wrote:
> On 22 January 2015 at 22:08, Ben Greear <greearb@candelatech.com> wrote:
>>
>> On 01/21/2015 11:47 AM, Ben Greear wrote:
>>> On 01/21/2015 11:01 AM, Ben Greear wrote:
>>>> On 01/20/2015 06:49 PM, Ben Greear wrote:
>>>>> On 01/20/2015 06:13 PM, Sebastian Gottschall wrote:
>>>>>> Am 20.01.2015 um 22:53 schrieb Ben Greear:
>>>>>>> I tried running a patched version of 3.19.0-rc5 kernel, and it seems to work
>>>>>>> fine when there is one ath10k NIC in the system, but when there is two it
>>>>>>> doesn't try to load the firmware.
>>
>> Ok, this bisects to this commit.  First (or sometimes second) NIC will load,
>> but the other one will not load firmware.  No obvious errors in dmesg.
>
> So I'm confused. If it doesn't load firmware then there has to be some
> error in dmesg. If there are no errors then how come you know it
> doesn't load firmware? Is it being probed at all?
>
>
>> Platform is x86-64, Fedora 20.  NICS:
>>
>> 03:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless Network Adapter
>> 04:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless Network Adapter
>>
>>
>> 7c0f0e3c9797e5a08d15da68812f24eadaf9e82b is the first bad commit
>> commit 7c0f0e3c9797e5a08d15da68812f24eadaf9e82b
>> Author: Michal Kazior <michal.kazior@tieto.com>
>> Date:   Mon Oct 20 14:14:38 2014 +0200
>>
>>      ath10k: mask/unmask msi fw irq
>>
>>      This was the final missing bit to making sure the
>>      device doesn't assert interrupts to host.
>>
>>      This should fix possible race when target crashes
>>      during driver teardown.
>>
>>      This also removes an early warm reset workaround
>>      during pci probing.
>>
>>      Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
>>      Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
>>
>> :040000 040000 f7ab5ff9f7e3713118dab6f23d02f11003de6fef fa5cb5ee76bdee2c654fcb8e6b8b1283c225bcc2 M      drivers
>
> Hmm.. This removes warm_reset in probe function but I fail to see how
> this could end up not loading one of the NIC *silently*?
>
> Anyway there's a pending patch which adds the reset back:
> https://github.com/kvalo/ath/commit/bdcd6f4e4ac5d2d2a56da4813f56655e6db0ee45
> . You might want to try it and see if it helps.

Reverting the patch made it work again for me.

I don't understand that code well, but perhaps you are disabling
a shared interrupt that silently stops the second NIC from
being able to do it's thing?

Do you have a PC with 2 NICs in it that you could try yourself?

I can grab you the logs of a failure to boot later today.

Thanks,
Ben

>
>
> Michał
>

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

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

  reply	other threads:[~2015-01-23 15:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 21:53 More than one ath10k NIC in 3.19.0-rc5? Ben Greear
2015-01-21  2:13 ` Sebastian Gottschall
2015-01-21  2:49   ` Ben Greear
2015-01-21 19:01     ` Ben Greear
2015-01-21 19:47       ` Ben Greear
2015-01-22 21:08         ` More than one ath10k NIC will not load (bisected) Ben Greear
2015-01-23  6:43           ` Michal Kazior
2015-01-23 15:54             ` Ben Greear [this message]
2015-01-24 18:53               ` Janusz Dziedzic
2015-02-05 20:50                 ` AW: " Conrad Kostecki
2015-02-04  9:07               ` Kalle Valo
2015-02-04  9:35                 ` Michal Kazior
2015-02-04 12:02                   ` Kalle Valo
2015-02-04 15:23                   ` Ben Greear
2015-02-05  6:02                     ` Michal Kazior
2015-02-05  6:41                       ` Ben Greear

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=54C26EB3.7050805@candelatech.com \
    --to=greearb@candelatech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox