brcmfmac: don't net_ratelimit() CONSOLE messages on firmware crash

Firmware crash is a pretty rare event and can't happen too frequently as
it has to be followed by a hardware reinitialization and config reload.
It should be safe to don't use net_ratelimit() when it happens.

For reporting & debugging purposes it's important to provide a complete
log as the last lines are actually the most important. This change
modifies brcmfmac to print all messages in an unlimited way in that
specific case. With this change there should be finally a backtrace of
firmware finally visible after a crash.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
index 4ea5401c4d6b68417ec8bec5c34d22f0a4cf6c02..8d0e744166433bae92fb993217e91768525d0575 100644 (file)
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
@@ -794,7 +794,8 @@ static void brcmf_pcie_bus_console_read(struct brcmf_pciedev_info *devinfo,
                if (ch == '\n') {
                        console->log_str[console->log_idx] = 0;
                        if (error)
-                               brcmf_err(bus, "CONSOLE: %s", console->log_str);
+                               __brcmf_err(bus, __func__, "CONSOLE: %s",
+                                           console->log_str);
                        else
                                pr_debug("CONSOLE: %s", console->log_str);
                        console->log_idx = 0;