ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Emanuel Taube <emanuel.taube@gmail.com>
Cc: Sven Schnelle <svens@stackframe.org>,
	Michal Kazior <michal.kazior@tieto.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Firmware crash
Date: Thu, 26 Jun 2014 10:32:19 -0700	[thread overview]
Message-ID: <53AC5923.6080209@candelatech.com> (raw)
In-Reply-To: <CAANdOW5bHeVqwqLVW7Ngr81mNJ6sa0tf3ojNDDFFzssrZTGvfw@mail.gmail.com>

On 06/26/2014 10:12 AM, Emanuel Taube wrote:
> Hi Ben,
> 
> your latest firmware fixes the crashes I was able to reproduce before.

Excellent, thanks for confirming.  Looks like it was simple null-pointer
deref.  I'll roll this into my firmware, so next 'official' release will
have the fix as well.

I'll send QCA a note off-list on what fixes it in case they want to
put the fix upstream some day.

Thanks,
Ben

> 
> Thanks and regards,
> Emanuel
> 
> 
> 2014-06-26 17:44 GMT+02:00 Ben Greear <greearb@candelatech.com <mailto:greearb@candelatech.com>>:
> 
>     On 06/26/2014 08:39 AM, Emanuel Taube wrote:
>     > Hi Ben,
>     >
>     > here is the dmesg output with your new community firmware:
> 
>     Looks like null-dereference (or possibly some other bad memory dereference),
>     not actually an assert (at least in my code).
> 
>     Can you re-download the firmware (same location) and see if that fixes the problem?
> 
>     Thanks,
>     Ben
> 
>     --
>     Ben Greear <greearb@candelatech.com <mailto:greearb@candelatech.com>>
>     Candela Technologies Inc  http://www.candelatech.com
> 
> 


-- 
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

      parent reply	other threads:[~2014-06-26 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 11:10 Firmware crash Sven Schnelle
2014-06-26 11:47 ` Michal Kazior
2014-06-26 13:06   ` Ben Greear
     [not found]     ` <CAANdOW6yrv-Z_+bXw_z3zrmz=Q4N=r0xh9YitwwCoUAQchChLg@mail.gmail.com>
2014-06-26 14:37       ` Ben Greear
2014-06-26 15:23       ` Ben Greear
     [not found]         ` <CAANdOW7QyeNxJcG+kbXiUQZOXkF0ofZFh_RLbD6U1MjTyED+1Q@mail.gmail.com>
2014-06-26 15:44           ` Ben Greear
     [not found]             ` <CAANdOW5bHeVqwqLVW7Ngr81mNJ6sa0tf3ojNDDFFzssrZTGvfw@mail.gmail.com>
2014-06-26 17:32               ` Ben Greear [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=53AC5923.6080209@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=emanuel.taube@gmail.com \
    --cc=michal.kazior@tieto.com \
    --cc=svens@stackframe.org \
    /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