aboutsummaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorRobert Stonehouse <rstonehouse@solarflare.com>2013-10-07 13:44:17 -0400
committerBen Hutchings <bhutchings@solarflare.com>2013-12-06 17:29:19 -0500
commit2d9955bedb18a403bde1290607d5c02cd86ae5fe (patch)
tree98cf6102b6d955eeb83b10c0efb4af209f40475b /drivers
parent2dd6426597eb642197a0bdb13d096acb1164b958 (diff)
sfc: Demote "MC Scheduler error" messages
The MC firmware is cooperatively multitasking and its scheduler will send an event when a task yields after running for more than the expected maximum time. This can be useful for firmware development but does not usually indicate a serious error and does not help to detect a lockup (there is a hardware watchdog that does that). Change the message and reduce log level accordingly. Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/net/ethernet/sfc/mcdi.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/net/ethernet/sfc/mcdi.c b/drivers/net/ethernet/sfc/mcdi.c
index 4b0bd8a1514d..25f91c0ca6a6 100644
--- a/drivers/net/ethernet/sfc/mcdi.c
+++ b/drivers/net/ethernet/sfc/mcdi.c
@@ -867,8 +867,8 @@ void efx_mcdi_process_event(struct efx_channel *channel,
867 efx_mcdi_sensor_event(efx, event); 867 efx_mcdi_sensor_event(efx, event);
868 break; 868 break;
869 case MCDI_EVENT_CODE_SCHEDERR: 869 case MCDI_EVENT_CODE_SCHEDERR:
870 netif_info(efx, hw, efx->net_dev, 870 netif_dbg(efx, hw, efx->net_dev,
871 "MC Scheduler error address=0x%x\n", data); 871 "MC Scheduler alert (0x%x)\n", data);
872 break; 872 break;
873 case MCDI_EVENT_CODE_REBOOT: 873 case MCDI_EVENT_CODE_REBOOT:
874 case MCDI_EVENT_CODE_MC_REBOOT: 874 case MCDI_EVENT_CODE_MC_REBOOT: