From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: ath10k crash on startup, related to ath10k_ce_completed_recv_next?
Date: Thu, 13 Feb 2014 17:39:53 +0200 [thread overview]
Message-ID: <878utf81iu.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <52FCE5AD.3080606@candelatech.com> (Ben Greear's message of "Thu, 13 Feb 2014 07:33:01 -0800")
Ben Greear <greearb@candelatech.com> writes:
> On 02/13/2014 02:09 AM, Kalle Valo wrote:
>> Ben Greear <greearb@candelatech.com> writes:
>>
>>> I saw the crash below on startup. My firmware is put back together
>>> again and mostly working, so not sure it is related to overly
>>> broken firmware.
>>>
>>> I have a few patches to ath10k, but mostly debugging code
>>> that should not affect the logic below.
>>
>> When you have your own changes it pretty difficult to start debugging
>> crashes like this, as your private changes can break something. Can you
>> see these crashes with the upstream version?
>
> I am unlikely to test with pure upstream code anytime soon..I need the
> features I added to take advantage of my customized CT firmware, and I need my
> firmware in order to run any of my more interesting test cases.
>
> If the problem is not obvious, then please just consider my crash reports
> as FYI and I'll work on them when I have time.
Ok, I'll do that. Please do keep sending these reports, they are
useful even if I can't analyse them right away.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-02-13 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 2:15 ath10k crash on startup, related to ath10k_ce_completed_recv_next? Ben Greear
2014-02-13 10:09 ` Kalle Valo
2014-02-13 15:33 ` Ben Greear
2014-02-13 15:39 ` Kalle Valo [this message]
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=878utf81iu.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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