From: Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr>
To: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: Patrick CARNEIRO RODRIGUEZ <p.carneiro@actiasodielec.fr>
Subject: RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
Date: Wed, 16 Apr 2014 13:51:04 +0200 [thread overview]
Message-ID: <EE97821C81277E459BEA5C6384C6F241012F06CC483A@srvexch01.SODIELEC.local> (raw)
In-Reply-To: <87eh0yetyx.fsf@kamboji.qca.qualcomm.com>
Thank you for your response,
I didn't power down my cible to reboot, I just upload new program with new firmware and run it. The problem is when that error appear my console keep print it and I Have no longer access to my system, I can not type another command (dmesg) , then I have to reset my platform. I'll try to get the dmesg and sent you later.
My host platform is using processor Marvell Armada 370 and my module of wifi is Compex WLE900VX.
There's another problem: when I used the firmware version 999.999 some times when I ran my program and change the parameter of configuration, the firmware crash and I got a output dmesg which indicate a strange version of firmware (1.0.0.636 ???) :
ath10k: firmware crashed!
ath10k: hardware name qca988x hw2.0 version 0x4100016c
ath10k: firmware version: 1.0.0.636
ath10k: target register Dump Location: 0x00401930
ath10k: target Register Dump
ath10k: [00]: 0x4100016C 0x00000000 0x0098E3A9 0x00000000
ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x0098E3A9
ath10k: [20]: 0x00000000 0x00401930 0x00000000 0x00000000
ath10k: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [56]: 0x00000000 0x00000000 0x00000000 0x00000000
and then It reload the firmware 999.999. :
ath10k: firmware 999.999.0.636 booted
You can see the output of my dmesg
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
________________________________________
De : Kalle Valo [kvalo@qca.qualcomm.com]
Date d'envoi : mardi 15 avril 2014 13:02
À : Vu Hai NGUYEN
Cc : ath10k@lists.infradead.org; Patrick CARNEIRO RODRIGUEZ
Objet : Re: Report Firmware firmware-2.bin_10.1.467.2-1 Error
Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> writes:
> When I load the firmware-2.bin_10.1.467.2-1 I got this error when I
> put my device in mode ACCESS POINT: "PCI express error: irq - 228, Pex
> number: 0, Interrupt Cause Register value: 10" But if I use the
> version 999.999.0.x. I don't have this error.
I wonder if this has something to do with cold reset causing PCI bus
errors? But we need more information to say more. Can you send the full
dmesg output (from the beginning of kernel boot) along with detailed
descriptions of your host platform and what kind qca98xx board you have.
Even better is if you can also send a debug log output using debug mask
value 0x432. More info:
http://wireless.kernel.org/en/users/Drivers/ath10k/debug#Useful_debug_masks
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-04-16 11:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 4:14 Crash during driver startup Ben Greear
2014-04-10 10:05 ` [PATCH] ath10k: double check bmi xfer pointers Michal Kazior
2014-04-10 10:05 ` Michal Kazior
2014-04-10 13:42 ` Ben Greear
2014-04-10 13:42 ` Ben Greear
2014-04-11 5:40 ` Kalle Valo
2014-04-11 5:40 ` Kalle Valo
2014-04-11 5:47 ` Michal Kazior
2014-04-11 5:47 ` Michal Kazior
2014-04-11 7:58 ` Michal Kazior
2014-04-11 7:58 ` Michal Kazior
2014-04-11 15:09 ` load module ath10k: ieee80211 phy0: Failed to initialize wep: -2 Vu Hai NGUYEN
2014-04-14 6:39 ` Michal Kazior
2014-04-14 8:10 ` Kalle Valo
2014-04-14 15:49 ` RE : " Vu Hai NGUYEN
2014-04-15 8:20 ` Report Firmware firmware-2.bin_10.1.467.2-1 Error Vu Hai NGUYEN
2014-04-15 11:02 ` Kalle Valo
2014-04-16 11:51 ` Vu Hai NGUYEN [this message]
2014-04-16 11:51 ` RE : " Vu Hai NGUYEN
2014-04-24 6:35 ` Kalle Valo
2014-04-24 9:03 ` RE : " Vu Hai NGUYEN
2014-04-24 9:41 ` Michal Kazior
2014-04-24 10:18 ` Yeoh Chun-Yeow
2014-04-30 12:39 ` RE : " Vu Hai NGUYEN
2014-05-07 7:36 ` ath10k does not support selection antenna yet? Vu Hai NGUYEN
2014-05-07 7:48 ` Michal Kazior
2014-05-07 8:16 ` Yeoh Chun-Yeow
2014-05-07 8:16 ` RE : " Vu Hai NGUYEN
2014-05-07 9:26 ` Janusz Dziedzic
2014-05-07 14:11 ` Ben Greear
2014-05-07 14:21 ` Adrian Chadd
2014-05-07 14:33 ` Ben Greear
2014-05-07 14:50 ` Adrian Chadd
2014-05-07 15:09 ` Ben Greear
2014-04-14 8:05 ` [PATCH] ath10k: double check bmi xfer pointers Kalle Valo
2014-04-14 8:05 ` 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=EE97821C81277E459BEA5C6384C6F241012F06CC483A@srvexch01.SODIELEC.local \
--to=vh.nguyen@actiasodielec.fr \
--cc=ath10k@lists.infradead.org \
--cc=p.carneiro@actiasodielec.fr \
/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.