From: Johannes Berg <johannes@sipsolutions.net>
To: "Toralf Förster" <toralf.foerster@gmx.de>,
linux-wireless <linux-wireless@vger.kernel.org>
Cc: Emmanuel Grumbach <egrumbach@gmail.com>
Subject: Re: warning at net/mac80211/driver-ops.h:647 ieee80211_sta_wmm_params
Date: Tue, 05 Jan 2016 17:05:50 +0100 [thread overview]
Message-ID: <1452009950.12357.46.camel@sipsolutions.net> (raw)
In-Reply-To: <567FCB67.1000101@gmx.de> (sfid-20151227_122919_319415_803E9245)
On Sun, 2015-12-27 at 12:28 +0100, Toralf Förster wrote:
> Yesterday I got this warning for the first time while using WLAN in a
> train, I'm unsure if this warning is worth to be reported or not :
Definitely worth it, thanks!
> Dec 26 20:26:48 t44 kernel: [45827.647635] cfg80211: (5490000 KHz -
> 5710000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
> Dec 26 20:26:48 t44 kernel: [45827.647637] cfg80211: (57000000 KHz
> - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
> Dec 26 20:26:48 t44 kernel: [45827.700734] ------------[ cut here ]
> ------------
> Dec 26 20:26:48 t44 kernel: [45827.700762] WARNING: CPU: 0 PID: 1498
> at net/mac80211/driver-ops.h:647 ieee80211_sta_wmm_params+0x3f7/0x410
> [mac80211]()
> Dec 26 20:26:48 t44 kernel: [45827.700764] wlp3s0: invalid
> CW_min/CW_max: 127/3
Ugly. I once met a guy who worked on the train AP network, should dig
up his contact info ...
In the meantime, we should catch this bug at a higher layer and do ...
something. But what exactly? Use default WMM parameters like we usually
do in cases like this?
johannes
prev parent reply other threads:[~2016-01-05 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 11:28 warning at net/mac80211/driver-ops.h:647 ieee80211_sta_wmm_params Toralf Förster
2015-12-27 21:39 ` Emmanuel Grumbach
2015-12-28 13:20 ` Toralf Förster
2016-01-05 16:05 ` Johannes Berg [this message]
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=1452009950.12357.46.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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.