On Fri, 2012-06-22 at 19:58 +0200, Bjørn Mork wrote:
> Hello,
>
> I just started receiving these mysterious error messages on each
> transmitted packet:
>
>
> Jun 22 19:48:21 nemi kernel: [255522.415447] iwlwifi 0000:03:00.0: GF was set with SGI:SISO
> Jun 22 19:48:21 nemi kernel: [255522.445200] iwlwifi 0000:03:00.0: GF was set with SGI:SISO
> Jun 22 19:48:21 nemi kernel: [255522.448130] iwlwifi 0000:03:00.0: GF was set with SGI:SISO
> Jun 22 19:48:21 nemi kernel: [255522.454865] iwlwifi 0000:03:00.0: GF was set with SGI:SISO
> Jun 22 19:48:21 nemi kernel: [255522.474708] iwlwifi 0000:03:00.0: GF was set with SGI:SISO
> Jun 22 19:48:21 nemi kernel: [255522.486878] iwlwifi 0000:03:00.0: GF was set with SGI:SISO
>
> which seems to originate from this code in
> drivers/net/wireless/iwlwifi/dvm/rs.c :
>
> if (use_green) {
> rate_n_flags |= RATE_MCS_GF_MSK;
> if (is_siso(tbl->lq_type) && tbl->is_SGI) {
> rate_n_flags &= ~RATE_MCS_SGI_MSK;
> IWL_ERR(priv, "GF was set with SGI:SISO\n");
> }
> }
>
>
>
> But I do fail to see what I as an user is expected to do about this...
>
> Could the message be improved with some end user guidance? And it
> should obviously be rate-limited.
There's nothing you can do about it, I'll just downgrade it -- see patch
below, also for an explanation.
> This is the first time I notice this issue, so I don't think it's very
> reproducible.
Too bad, I would've been interested in a command trace when this
happens, but it would have to be a fairly long-running trace before the
error message happens.
Were you in some special place when this happened? It has to be an 11n
AP that is greenfield capable, with no 11a/b/g stations connected to it.
Maybe some 11g client disconnected from the AP and then the messages
started showing up?
johannes
[PATCH] iwlwifi: turn down "GF was set with SGI:SISO" message
Single-stream SGI is incompatible with greenfield,
802.11-12 says:
NOTE—Short GI is not used in HT-greenfield format
with one spatial stream, in which case the HT-SIG
is immediately followed by data. It is very
difficult to parse the HT-SIG in time to demodulate
these data with the correct GI length if the GI
length is not known in advance.
The error indicates that somehow the RS algorithm
tried to select 1x1 with SGI while the station is
in greenfield mode, which shouldn't happen, but
there's no need to flood the log with the message
either.
Signed-off-by: Johannes Berg <johannes.berg@xxxxxxxxx>
---
drivers/net/wireless/iwlwifi/dvm/rs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/iwlwifi/dvm/rs.c b/drivers/net/wireless/iwlwifi/dvm/rs.c
index 6fddd27..39d26f2 100644
--- a/drivers/net/wireless/iwlwifi/dvm/rs.c
+++ b/drivers/net/wireless/iwlwifi/dvm/rs.c
@@ -598,7 +598,8 @@ static u32 rate_n_flags_from_tbl(struct iwl_priv *priv,
rate_n_flags |= RATE_MCS_GF_MSK;
if (is_siso(tbl->lq_type) && tbl->is_SGI) {
rate_n_flags &= ~RATE_MCS_SGI_MSK;
- IWL_ERR(priv, "GF was set with SGI:SISO\n");
+ IWL_DEBUG_RATE(priv,
+ "GF was set with SGI:SISO\n");
}
}
}
--
1.7.10
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
