On Sun, Sep 04, 2011 at 10:28:35AM +0200, Paul Bolle wrote:

On Tue, 2011-06-07 at 16:54 +0200, Stanislaw Gruszka wrote:

quoted

That could be useful hint, we do not scan chan by chan, but we
have thing called "plcp check health", which "restart radio"
by requesting one channel scan. So perhaps disabling that could
help.

[...]

diff --git a/drivers/net/wireless/iwlegacy/iwl-rx.c b/drivers/net/wireless/iwlegacy/iwl-rx.c
index 654cf23..6062da0 100644
--- a/drivers/net/wireless/iwlegacy/iwl-rx.c
+++ b/drivers/net/wireless/iwlegacy/iwl-rx.c

@@ -230,6 +230,8 @@ EXPORT_SYMBOL(iwl_legacy_rx_spectrum_measure_notif);
 void iwl_legacy_recover_from_statistics(struct iwl_priv *priv,
 				struct iwl_rx_packet *pkt)
 {
+	return;
+
 	if (test_bit(STATUS_EXIT_PENDING, &priv->status))
 		return;
 	if (iwl_legacy_is_any_associated(priv)) {

0) I finally got around to applying this patch (to v3.0.4).

1) After a few days of normal usage (with quite a bit of suspend and
resume cycles) this error was again triggered. So avoiding
check_plcp_health() doesn't seem to help.

2) I never send you the debug output (ie, output after doing "modprobe
iwl4965 debug=0x47ffffff"), did I?

No, but if error show up after few days, gathering and analyzing few
days of debug logs in impractical. Does wifi stop working after an
error, or there is some other negative impact? Or only that messages
are printed and driver recover itself?

Stanislaw