From: Kalle Valo <kvalo@codeaurora.org>
To: linux-wireless@vger.kernel.org
Cc: linuxwifi@intel.com
Subject: Re: [regression] iwlwifi: crash in iwl_parse_tlv_firmware()
Date: Sun, 29 Jan 2017 16:04:43 +0200 [thread overview]
Message-ID: <87efzmt11g.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87inoyt1ff.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Sun, 29 Jan 2017 15:56:20 +0200")
Kalle Valo <kvalo@codeaurora.org> writes:
> updated the kernel on my test laptop and noticed that now iwlwifi
> crashes every time during boot. This is with tag ath-201701271935
> ath.git master branch, which essentially is wt-2017-01-27 from
> wireless-testing plus latest ath patches.
>
> I tried v4.10-rc5 and iwlwifi didn't crash so my guess is that this is a
> regression in the latest iwlwifi pull. Below is the crash log and the
> location in source. This is all I got via netconsole.
Forgot to include info about the device (from a working kernel):
[ 17.911087] iwlwifi 0000:44:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 17.931205] iwlwifi 0000:44:00.0: loaded firmware version 39.31.5.1 build 35138 op_mode iwldvm
[ 18.073590] iwlwifi 0000:44:00.0: CONFIG_IWLWIFI_DEBUG enabled
[ 18.073679] iwlwifi 0000:44:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
[ 18.073757] iwlwifi 0000:44:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[ 18.073837] iwlwifi 0000:44:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C
[ 18.078383] iwlwifi 0000:44:00.0: L1 Enabled - LTR Disabled
[ 19.359378] iwlwifi 0000:44:00.0 wlan1: renamed from wlan0
--
Kalle Valo
next prev parent reply other threads:[~2017-01-29 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 13:56 [regression] iwlwifi: crash in iwl_parse_tlv_firmware() Kalle Valo
2017-01-29 14:04 ` Kalle Valo [this message]
2017-01-30 10:34 ` [PATCH] iwlwifi: alloc memory dynamically also for DVM Luca Coelho
2017-01-30 11:40 ` Kalle Valo
2017-01-30 11:42 ` Luca Coelho
2017-01-31 7:11 ` 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=87efzmt11g.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.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;
as well as URLs for NNTP newsgroup(s).