From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: ath10k@lists.infradead.org
Subject: Re: Fwd: ath10k related kernel crash in wireless-testing (3.12.0-rc3-wl+)
Date: Mon, 21 Oct 2013 08:59:58 -0700 [thread overview]
Message-ID: <52654F7E.3080606@candelatech.com> (raw)
In-Reply-To: <87fvruu3jz.fsf@kamboji.qca.qualcomm.com>
On 10/21/2013 07:00 AM, Kalle Valo wrote:
> Kalle Valo <kvalo@qca.qualcomm.com> writes:
>
>> Ben Greear <greearb@candelatech.com> writes:
>>
>>> I sent this to the wrong list the first time.
>>>
>>> Do you know if this is already addressed? If not, I'll see if I can
>>> find a fix.
>>
>> [...]
>>
>>> ath10k: MSI-X interrupt handling (8 intrs)
>>> ath10k: Unable to wakeup target
>>> ath10k: target took longer 5000 us to wake up (awake count 1)
>>> ath10k: Failed to get pcie state addr: -16
>>> ath10k: early firmware event indicated
>>> BUG: unable to handle kernel NULL pointer dereference at 0000000000000004
>>> IP: [<ffffffffa06ae46c>] ath10k_ce_completed_send_next+0x47/0x122
>>> [ath10k_pci]
>>
>> I think there are two bugs here:
>>
>> 1) Cold reset doesn't always work, Michal has a patch for that. That's
>> why the wakeup fails:
>>
>> http://lists.infradead.org/pipermail/ath10k/2013-October/000638.html
>>
>> 2) We enable interrupts too early and if wakeup fails and we get a
>> spurious interrupt ath10k crashes. We don't have a fix for this yet.
>
> I was able to reproduce your crash and it seems that my patch "ath10k:
> add error handling to ath10k_pci_wait()" fixes the crash. But it's not
> an ultimate solution, it's just bandaid for the issue:
>
> [ 3200.447601] ath10k: MSI-X didn't succeed (1), trying MSI
> [ 3200.447898] ath10k_pci 0000:02:00.0: irq 49 for MSI/MSI-X
> [ 3200.449101] ath10k: MSI interrupt handling
> [ 3201.620679] ath10k: Unable to wakeup target
> [ 3201.620754] ath10k: Failed to reset target, target did not wake up: -110
> [ 3201.621111] ath10k: early firmware event indicated
> [ 3201.621624] ath10k: could not start pci hif (-110)
> [ 3201.621691] ath10k: could not probe fw (-110)
> [ 3201.621750] ath10k: could not register driver core (-110)
>
> We are working on fixing the wakeup issue, doing just warm reset helps
> but there are other problems with that. Need to investigate more.
>
> And we need to fix the interrupt race properly at some point, I added a
> todo entry for this:
>
> http://wireless.kernel.org/en/users/Drivers/ath10k/todo
Thanks. Is this the proper repository to develop/test against?
git://github.com/kvalo/ath.git
('master' branch)?
Thanks,
Ben
--
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
next prev parent reply other threads:[~2013-10-21 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52588F0C.3000009@candelatech.com>
2013-10-16 16:00 ` Fwd: ath10k related kernel crash in wireless-testing (3.12.0-rc3-wl+) Ben Greear
2013-10-16 16:23 ` Kalle Valo
2013-10-17 8:43 ` Kalle Valo
2013-10-17 22:58 ` Michal Kazior
2013-10-18 6:29 ` Kalle Valo
2013-10-18 15:41 ` Michal Kazior
2013-10-21 14:00 ` Kalle Valo
2013-10-21 15:59 ` Ben Greear [this message]
2013-10-21 16:46 ` 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=52654F7E.3080606@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.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