Return-path: Received: from bu3sch.de ([62.75.166.246]:44523 "EHLO vs166246.vserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754349AbZCSS2T (ORCPT ); Thu, 19 Mar 2009 14:28:19 -0400 From: Michael Buesch To: John W Linville Subject: [PATCH] b43: Mask PHY TX error interrupt, if not debugging Date: Thu, 19 Mar 2009 19:27:21 +0100 Cc: bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org MIME-Version: 1.0 Message-Id: <200903191927.21868.mb@bu3sch.de> (sfid-20090319_192822_001589_3A0606B8) Content-Type: text/plain; charset="us-ascii" Sender: linux-wireless-owner@vger.kernel.org List-ID: This masks the PHY TX error interrupt, if debugging is disabled. Currently we have a bug somewhere which triggers this interrupt once in a while. (Depends on the network noise/quality). While this is nonfatal, it scares the hell out of users and we frequently receive bugreports that incorrectly identify this error message as the reason. There's another problem with this. The PHY TX error interrupt is protected with a watchdog that will restart the device if it keeps triggering very often. This is used to fix interrupt storms from completely broken devices. However, this watchdog might trigger in completely normal operation. If the TX capacity of the card is saturated, the likeliness of the watchdog triggering increases, as more TX errors occur. The current threshold for the watchdog is 1000 errors in 15 seconds. This patch adds a workaround for the issue by just enabling the interrupt if debugging is disabled (by Kconfig or by modparam). This has the downside that real fatal PHY TX errors are not caught anymore. But this is nonfatal due to the following reasons: * If the card is not able to transmit anymore, MLME will notice anyway. * I did _never_ see a real fatal PHY TX error in a mainline b43 driver. * It does _not_ result in interrupt storms or something like that. It will simply result in a stalled card. It can be debugged by enabling the debugging module parameter. Signed-off-by: Michael Buesch --- I wonder how much placebo "PHY TX error was fixed and my card performs great again" we will get. :D !!! DISTRIBUTIONS !!! Disable CONFIG_B43_DEBUG! There is absolutely _no_ reason to enable it on a release kernel. There were valid reasons in the past, but there are none left anymore. So please _disable_ this option now, if you didn't do this already, because with CONFIG_B43_DEBUG enabled the PHY TX errors will still show. John, please merge this for the next feature release. Index: wireless-testing/drivers/net/wireless/b43/main.c =================================================================== --- wireless-testing.orig/drivers/net/wireless/b43/main.c 2009-03-19 17:27:39.000000000 +0100 +++ wireless-testing/drivers/net/wireless/b43/main.c 2009-03-19 18:53:16.000000000 +0100 @@ -3990,12 +3990,14 @@ static void setup_struct_wldev_for_init( setup_struct_phy_for_init(dev, &dev->phy); /* IRQ related flags */ dev->irq_reason = 0; memset(dev->dma_reason, 0, sizeof(dev->dma_reason)); dev->irq_savedstate = B43_IRQ_MASKTEMPLATE; + if (b43_modparam_verbose < B43_VERBOSITY_DEBUG) + dev->irq_savedstate &= ~B43_IRQ_PHY_TXERR; dev->mac_suspended = 1; /* Noise calculation context */ memset(&dev->noisecalc, 0, sizeof(dev->noisecalc)); } -- Greetings, Michael.