From: Luciano Coelho <luciano.coelho@intel.com>
To: "Yan, Zheng" <zyan@redhat.com>
Cc: stable@vger.kernel.org, linuxwifi@intel.com
Subject: Re: 4.17.2 -> 4.17.3 iwlwifi regression
Date: Thu, 05 Jul 2018 08:44:32 +0300 [thread overview]
Message-ID: <e2d1ccc68d2c8e6d29aa755faaa6c9560fb0c8de.camel@intel.com> (raw)
In-Reply-To: <5586D97E-2C46-401D-836D-081086E178F9@redhat.com>
On Thu, 2018-07-05 at 08:49 +0800, Yan, Zheng wrote:
> I started to get following warning and unstable connection after
> upgrading kernel to 4.17.3 (from 4.17.2).
>
>
> iwlwifi 0000:04:00.0: loaded firmware version 38.c0e03d94.0 op_mode iwlmvm
> iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 9260, REV=0x324
> audit: type=1130 audit(1529640588.009:69): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> iwlwifi 0000:04:00.0: base HW address: 74:e5:f9:a6:bb:52
> …
>
>
> WARNING: CPU: 1 PID: 0 at drivers/net/wireless/intel/iwlwifi/mvm/tx.c:710 iwl_mvm_tx_tso_segment+0x28a/0x2a0 [iwlmvm]
Strange, I don't see anything that could directly cause this issue:
luca@redipa:~/public/linux$ git log v4.17.2..v4.17.3 --oneline -- net/ drivers/net/wireless/intel/iwlwifi/
1d79bd39cd5b iwlwifi: fw: harden page loading code
aba9ac38845c net: in virtio_net_hdr only add VLAN_HLEN to csum_start if payload holds vlan
e8b9a16954b5 udp: fix rx queue len reported by diag and proc interface
be3bb23cc0e4 socket: close race condition between sock_close() and sockfs_setattr()
6196f30e84ca tls: fix waitall behavior in tls_sw_recvmsg
7fd98de479ea tls: fix use-after-free in tls_push_record
1caf7914a7a5 tcp: verify the checksum of the first data segment in a new connection
a316034b203f net/sched: act_simple: fix parsing of TCA_DEF_DATA
36ee02c5ff46 net: dsa: add error handling for pskb_trim_rcsum
b788fc5f6977 ipv6: allow PMTU exceptions to local routes
Did you happen to upgrade the firmware at the same time? How often does
it happen? Can you try to bisect?
--
Cheers,
Luca.
next prev parent reply other threads:[~2018-07-05 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 0:49 4.17.2 -> 4.17.3 iwlwifi regression Yan, Zheng
2018-07-05 5:44 ` Luciano Coelho [this message]
2018-07-05 8:50 ` Yan, Zheng
2018-07-05 15:08 ` Greg KH
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=e2d1ccc68d2c8e6d29aa755faaa6c9560fb0c8de.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=linuxwifi@intel.com \
--cc=stable@vger.kernel.org \
--cc=zyan@redhat.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).