From: Michal Hocko <mhocko@kernel.org>
To: Johannes Berg <johannes.berg@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: many "changed bandwidth, new config is" messages in the log
Date: Thu, 24 Nov 2016 16:07:24 +0100 [thread overview]
Message-ID: <20161124150723.GA4776@dhcp22.suse.cz> (raw)
Hi,
I have only now managed to move to 4.9-rc5 (from 4.8) and started seeing
quite a lot of following messages
"
[ 346.612211] wlan0: AP c0:4a:00:f1:48:f2 changed bandwidth, new config is 2472 MHz, width 1 (2472/0 MHz)
[ 352.655929] wlan0: AP c0:4a:00:f1:48:f2 changed bandwidth, new config is 2472 MHz, width 2 (2462/0 MHz)
"
It always seems to be changing width from 1 -> 2 and back
$ dmesg | grep "changed bandwidth" | wc -l
42
in 13 minutes of uptime. I have noticed this came in via 30eb1dc2c430
("mac80211: properly track HT/VHT operation changes").
Is this something to be worried about?
--
Michal Hocko
SUSE Labs
next reply other threads:[~2016-11-24 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 15:07 Michal Hocko [this message]
2016-11-24 15:12 ` many "changed bandwidth, new config is" messages in the log Johannes Berg
2016-11-24 15:25 ` Michal Hocko
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=20161124150723.GA4776@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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