From: Larry Finger Date: Wed, 9 Dec 2009 19:25:56 +0000 (-0600) Subject: b43: Remove reset after fatal DMA error X-Git-Tag: firefly_0821_release~10186^2~1769 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=a56d040407bfbb67c0c3c15994768ed389d2b93f;p=firefly-linux-kernel-4.4.55.git b43: Remove reset after fatal DMA error commit 214ac9a4ead6cb254451c09d9c8234a76693feb1 upstream. As shown in Kernel Bugzilla #14761, doing a controller restart after a fatal DMA error does not accomplish anything other than consume the CPU on an affected system. Accordingly, substitute a meaningful message for the restart. Signed-off-by: Larry Finger Signed-off-by: John W. Linville Cc: maximilian attems Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/net/wireless/b43/main.c b/drivers/net/wireless/b43/main.c index a8a00d28a1a8..1642c9c9a348 100644 --- a/drivers/net/wireless/b43/main.c +++ b/drivers/net/wireless/b43/main.c @@ -1788,7 +1788,10 @@ static void b43_do_interrupt_thread(struct b43_wldev *dev) dma_reason[0], dma_reason[1], dma_reason[2], dma_reason[3], dma_reason[4], dma_reason[5]); - b43_controller_restart(dev, "DMA error"); + b43err(dev->wl, "This device does not support DMA " + "on your system. Please use PIO instead.\n"); + b43err(dev->wl, "CONFIG_B43_FORCE_PIO must be set in " + "your kernel configuration.\n"); return; } if (merged_dma_reason & B43_DMAIRQ_NONFATALMASK) {