From: Eric Biggers <ebiggers3@gmail.com>
To: "Dreyfuss, Haim" <haim.dreyfuss@intel.com>
Cc: linuxwifi <linuxwifi@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Coelho, Luciano" <luciano.coelho@intel.com>,
Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [4.17 iwlwifi regression] NULL pointer dereference in reg_query_regdb_wmm()
Date: Mon, 21 May 2018 21:59:06 -0700 [thread overview]
Message-ID: <20180522045906.GB987@sol.localdomain> (raw)
In-Reply-To: <20180522044712.GA987@sol.localdomain>
On Mon, May 21, 2018 at 09:47:12PM -0700, Eric Biggers wrote:
> Hi Haim,
>
> On Mon, May 21, 2018 at 10:10:09AM +0000, Dreyfuss, Haim wrote:
> > Hello,
> >
> > Can you provide the following information?
> > 1. The *boot* you mentioned is from clean shutdown or from Sx state?
> > 2. Do you know which MCC the driver is trying to update?
> > I will appreciate if you could reproduce it with trace-cmd (recording at least iwlwifi , iwlwifi_msg -and iwlwifi_ucode)
> > Or if you can't, just send dmesg but make sure to set iwlwifi.debug in the kernel parameters to 0x4000
> >
>
> It's a clean boot, from powered off.
>
> I built an v4.17-rc6 kernel with CONFIG_IWLWIFI_DEBUG=y and booted with
> iwlwifi.debug=0x4000. I've attached the dmesg output and kernel config.
>
> The crash happens right away, so there's no time to easily run trace-cmd.
> But if the other stuff still isn't enough, I can try booting with the
> NetworkManager service disabled, then enabling it at runtime.
>
> - Eric
The crash goes away if I replace iwlwifi-7265D-27.ucode in CONFIG_EXTRA_FIRMWARE
with iwlwifi-7265D-29.ucode. I don't know how well supported using old iwlwifi
firmware versions is supposed to be, but it shouldn't crash the kernel.
- Eric
next prev parent reply other threads:[~2018-05-22 4:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 18:33 [4.17 iwlwifi regression] NULL pointer dereference in reg_query_regdb_wmm() Eric Biggers
2018-05-21 7:42 ` Luca Coelho
2018-05-21 16:25 ` Kalle Valo
2018-05-21 16:30 ` Luca Coelho
2018-05-21 17:57 ` Kalle Valo
2018-05-21 10:10 ` Dreyfuss, Haim
2018-05-21 16:28 ` Kalle Valo
2018-05-21 16:56 ` Dreyfuss, Haim
2018-05-22 14:06 ` Kalle Valo
2018-05-22 4:47 ` Eric Biggers
2018-05-22 4:59 ` Eric Biggers [this message]
2018-05-22 7:58 ` Dreyfuss, Haim
2018-05-21 10:11 ` Dreyfuss, Haim
2018-05-21 20:34 ` [PATCH] cfg80211: fix NULL pointer derference when querying regdb Luca Coelho
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=20180522045906.GB987@sol.localdomain \
--to=ebiggers3@gmail.com \
--cc=haim.dreyfuss@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@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 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.