All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: prabhu <d.praabhu@gmail.com>, Taketo Kabe <kabe@sra-tohoku.co.jp>
Cc: kvalo@codeaurora.org, m@bues.ch, linux-wireless@vger.kernel.org,
	b43-dev@lists.infradead.org
Subject: Re: [Regression]BCM4312 is broken in kernel 4.18[Root cause found]
Date: Sun, 26 Aug 2018 11:14:38 -0500	[thread overview]
Message-ID: <25814b23-dcc9-3a20-7276-40818bbba6cb@lwfinger.net> (raw)
In-Reply-To: <CAHnrWRp2n7W_Xb5kjT1ykcC0gL3ONc+dmqePAbKEEBHLd1euFA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 533 bytes --]

On 08/26/2018 02:23 AM, prabhu wrote:
> Larry,
> 
> Upgrading the firmware didn't fix the issue.
> 
> The patch fixes it. My system has been running without any issues
> since yesterday.

I did not think the new firmware would help, but it had to be tried. Thanks for 
the testing.

@Pradhu & @Taketo: Attached is a new (improved?) patch for you to try. You need 
to start from an unmodified 4.18 source. This patch should allow both of your 
systems to work and avoid needing to revert Taketo's fix for his setup.

Thanks,

Larry



[-- Attachment #2: 0001-b43-Fix-regression-in-kernel-4.18.patch --]
[-- Type: text/x-patch, Size: 2123 bytes --]

>From 4805a08715de42d49587975979425031307218b6 Mon Sep 17 00:00:00 2001
From: Larry Finger <Larry.Finger@lwfinger.net>
Date: Sun, 26 Aug 2018 10:47:52 -0500
Subject: [PATCH] b43: Fix regression in kernel 4.18
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org

In commit 66cffd6daab7 ("b43: fix transmit failure when VT is switched"),
a condition is noted where the network controller needs to be reset. Note
that this situation happens when running the open-source firmware
(http://netweb.ing.unibs.it/~openfwwf/), plus a number of other special
conditions.

for a different card model, it is reported that this change breaks
operation running the proprietary firmware
(https://marc.info/?l=linux-wireless&m=153504546924558&w=2). Rather
than reverting the previous patch, the code is tweaked to avoid the
reset unless the open-source firmware is being used.

Fixes: 66cffd6daab7 ("b43: fix transmit failure when VT is switched")
Cc: Stable <stable@vger.kernel.org> # 4.18+
Cc: Taketo Kabe <kabe@sra-tohoku.co.jp>
Cc: D. Prabhu <d.praabhu@gmail.com>
Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
---
 drivers/net/wireless/broadcom/b43/dma.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/net/wireless/broadcom/b43/dma.c b/drivers/net/wireless/broadcom/b43/dma.c
index 6b0e1ec346cb..d46d57b989ae 100644
--- a/drivers/net/wireless/broadcom/b43/dma.c
+++ b/drivers/net/wireless/broadcom/b43/dma.c
@@ -1518,13 +1518,15 @@ void b43_dma_handle_txstatus(struct b43_wldev *dev,
 			}
 		} else {
 			/* More than a single header/data pair were missed.
-			 * Report this error, and reset the controller to
+			 * Report this error. If running with open-source
+			 * firmware, then reset the controller to
 			 * revive operation.
 			 */
 			b43dbg(dev->wl,
 			       "Out of order TX status report on DMA ring %d. Expected %d, but got %d\n",
 			       ring->index, firstused, slot);
-			b43_controller_restart(dev, "Out of order TX");
+			if (dev->fw.opensource)
+				b43_controller_restart(dev, "Out of order TX");
 			return;
 		}
 	}
-- 
2.18.0


  reply	other threads:[~2018-08-26 19:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 17:30 [Regression]BCM4312 is broken in kernel 4.18[Root cause found] prabhu
2018-08-23 18:11 ` Michael Büsch
2018-08-24  8:23   ` Kalle Valo
2018-08-24 16:15     ` Larry Finger
2018-08-26  7:23       ` prabhu
2018-08-26 16:14         ` Larry Finger [this message]
2018-08-27 11:30           ` prabhu
2018-08-27 15:28             ` Larry Finger
     [not found]               ` <CAHnrWRpPzV5BK3BoMrQ1vH=nxu70dVONLdhCnHh0SpBEa2v5LQ@mail.gmail.com>
2018-09-04 15:15                 ` Larry Finger
2018-08-28 12:41           ` Taketo Kabe
2018-08-23 19:20 ` Larry Finger
2018-08-24  7:54   ` prabhu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25814b23-dcc9-3a20-7276-40818bbba6cb@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=d.praabhu@gmail.com \
    --cc=kabe@sra-tohoku.co.jp \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=m@bues.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.