Commit e3b1d879 authored by Rafał Miłecki's avatar Rafał Miłecki Committed by Kalle Valo

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: default avatarRafał Miłecki <rafal@milecki.pl>
Acked-by: default avatarArend van Spriel <arend.vanspriel@broadcom.com>
Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
parent 2ec4ad49
...@@ -794,7 +794,8 @@ static void brcmf_pcie_bus_console_read(struct brcmf_pciedev_info *devinfo, ...@@ -794,7 +794,8 @@ static void brcmf_pcie_bus_console_read(struct brcmf_pciedev_info *devinfo,
if (ch == '\n') { if (ch == '\n') {
console->log_str[console->log_idx] = 0; console->log_str[console->log_idx] = 0;
if (error) if (error)
brcmf_err(bus, "CONSOLE: %s", console->log_str); __brcmf_err(bus, __func__, "CONSOLE: %s",
console->log_str);
else else
pr_debug("CONSOLE: %s", console->log_str); pr_debug("CONSOLE: %s", console->log_str);
console->log_idx = 0; console->log_idx = 0;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment