mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-06 10:57:46 +00:00
b43: Remove reset after fatal DMA error
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 <Larry.Finger@lwfinger.net> Cc: Stable <stable@vger.kernel.org> [2.6.32] Signed-off-by: John W. Linville <linville@tuxdriver.com>
This commit is contained in:
parent
49d7590ce4
commit
214ac9a4ea
1 changed files with 4 additions and 1 deletions
|
@ -1784,7 +1784,10 @@ static void b43_do_interrupt_thread(struct b43_wldev *dev)
|
||||||
dma_reason[0], dma_reason[1],
|
dma_reason[0], dma_reason[1],
|
||||||
dma_reason[2], dma_reason[3],
|
dma_reason[2], dma_reason[3],
|
||||||
dma_reason[4], dma_reason[5]);
|
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;
|
return;
|
||||||
}
|
}
|
||||||
if (merged_dma_reason & B43_DMAIRQ_NONFATALMASK) {
|
if (merged_dma_reason & B43_DMAIRQ_NONFATALMASK) {
|
||||||
|
|
Loading…
Reference in a new issue