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 07:37:51 -0700 [thread overview]
Message-ID: <53AC303F.2040606@candelatech.com> (raw)
In-Reply-To: <CAANdOW6yrv-Z_+bXw_z3zrmz=Q4N=r0xh9YitwwCoUAQchChLg@mail.gmail.com>
On 06/26/2014 07:33 AM, Emanuel Taube wrote:
> Hi Ben,
>
> I am able to reproduce it with your firmware-2-ct-no-commercial-7.bin
> here is the crash dump:
Thanks. I am going to have to update my decode program to parse
this...it doesn't look like 'normal' dmesg output on my systems.
Should have it done shortly...
Ben
>
> assertion failed? pc=0x9a1a49, line=0, dump area=0x401930
> Target ID: 0x4100016c (1090519404)
> Debug Info:
> 0x4100016c 0x00000000 0x009a1a49 0x00000000
> 0x00000000 0x00060324 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x009b58cb 0x0094085d 0x00000000 0x009a1a49
> 0x809430b8 0x00401a40 0x00000001 0x00000002
> 0x80940975 0x00401a60 0x0000001f 0x00403bec
> 0x409406b9 0x00401a80 0x0000001f 0x00419154
> 0x00000000 0x00401aa0 0x00050024 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
>
> to reproduce it I run 2 ath10k APs, one with the
> WIPHY_FLAG_IBSS_RSN enabled and one without.
> Whichever AP starts first keeps running while the other one
> crashes when trying to start hostapd.
>
> Thanks,
> Emanuel
>
>
> 2014-06-26 15:06 GMT+02:00 Ben Greear <greearb@candelatech.com <mailto:greearb@candelatech.com>>:
>
>
>
> On 06/26/2014 04:47 AM, Michal Kazior wrote:
>
> TSF id: 1, free_tsf_id_map: 1
> assertion failed? pc=0x9a0e15, line=0, dump area=0x401930
> Target ID: 0x4100016c (1090519404)
> Debug Info:
> 0x4100016c 0x00000000 0x009a0e15 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x009a0e15
> 0x00000000 0x00401930 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
> 0x00000000 0x00000000 0x00000000 0x00000000
>
>
> Apparently firmware crashes while processing a beacon frame with a
> NULL dereference.
>
>
> I fixed some issues in this area in my CT firmware, so you could
> try it if you want. If you can crash my firmware, please
> send me the similar crash dump and I can probably fix it.
>
> Note this is not official QCA firmware, so any problems specific to
> this firmware should be directed at me, and not QCA, and when reporting
> general bugs (say, with driver), if you are using CT firmware be sure to
> note that.
>
> http://www.candelatech.com/__ath10k.php <http://www.candelatech.com/ath10k.php>
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb@candelatech.com <mailto:greearb@candelatech.com>>
> Candela Technologies Inc http://www.candelatech.com
>
>
> _________________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org <mailto:ath10k@lists.infradead.org>
> http://lists.infradead.org/__mailman/listinfo/ath10k <http://lists.infradead.org/mailman/listinfo/ath10k>
>
>
--
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:[~2014-06-26 14:38 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 [this message]
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
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=53AC303F.2040606@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 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.