From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Zaki <zaki.bm@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: Crash when loading module
Date: Wed, 28 Aug 2013 08:40:59 +0300 [thread overview]
Message-ID: <87fvtujrtg.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CABQkniCRG=UhP2TtKRxC5tquoCoMfuVsuGPPz=zGVKzUcakGxw@mail.gmail.com> (Zaki's message of "Fri, 16 Aug 2013 17:46:31 +0800")
Zaki <zaki.bm@gmail.com> writes:
> Hi,
>
> I am new to ath10k. Used to have ath9k-based module last time. I am
> using Freescale MPC8315ERDB board to host the QCA988X_2_0_DEVICE_ID
> device.
Are you sure it's QCA9880 v2? For some reason v1 has same PCI id as v2.
> I am forcing the module to use legacy interrupt handler because my BSP
> doesn't support MSI or MSI-X just yet.
How did you force the legacy interrupt handler?
What version of ath10k are you using? Are you using ath.git master
branch or something else?
> During the module loading, the system crash. Looks like it failed at
> some reset device or reset target function, but i am not too sure
> which one causing it. Below are the logs i collected. I would
> apopreciate any help. Thanks a lot in advance.
>
> # modprobe ath10k_pci.ko
> [ 42.465296] cfg80211: Calling CRDA to update world regulatory domain
> [ 42.744607] ath10k_pci 0001:02:00.0: BAR 0: assigned [mem 0xa0000000-0xa01ff]
> [ 42.752698] ath10k_pci 0001:02:00.0: enabling device (0000 -> 0002)
> [ 42.759300] ath10k: MSI-X didn't succeed (1), trying MSI
> [ 42.785492] ath10k: legacy interrupt handling
> [ 42.850072] Oops: Machine check, sig: 7 [#1]
> [ 42.854333] DEBUG_PAGEALLOC MPC831x RDB
According to the link below this error might indicate that the PCI
device is not responding. I wonder if you are using v1 board?
https://lkml.org/lkml/2007/8/23/41
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2013-08-28 5:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 9:46 Crash when loading module Zaki
2013-08-28 5:40 ` Kalle Valo [this message]
[not found] ` <CABQkniBk-BUJW5Prjzw4J7jh=km15AZkNim523QZ+eU72=oJeQ@mail.gmail.com>
2013-08-28 6:32 ` Kalle Valo
2013-08-28 6:40 ` Zaki
2013-08-28 6:58 ` Bartosz Markowski
2013-08-28 7:13 ` Zaki
2013-08-28 7:46 ` Zaki
2013-08-28 7:59 ` Kalle Valo
2013-08-30 7:29 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2013-08-31 15:31 Christian Lamparter
2013-09-01 6:15 ` 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=87fvtujrtg.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=zaki.bm@gmail.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 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.