linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sardonimous <sardonimous@hotmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Wireless <linux-wireless@vger.kernel.org>,
	Netdev <netdev@vger.kernel.org>
Cc: "Michael Büsch" <m@bues.ch>, "kernel test robot" <lkp@intel.com>,
	"Simon Horman" <simon.horman@corigine.com>,
	"Kalle Valo" <kvalo@kernel.org>
Subject: Re: Fwd: After kernel 6.3.7 or 6.3.8 b43 driver fails
Date: Sun, 25 Jun 2023 11:58:00 -0500	[thread overview]
Message-ID: <RO2P215MB193879B2D99DD0BAF59EFA92A721A@RO2P215MB1938.LAMP215.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <69b98eb4-2c4e-fe75-90b4-4b08505a595a@lwfinger.net>

Hello Larry,

On 6/24/23 23:41, Larry Finger wrote:
>
> Sardonimous,
>
> The critical line is:
>> Jun 20 18:20:11 askasleikir kernel: b43_pio_tx+0x373/0x390
>
> I certainly have not used PIO for a long time. I expect that your 
> MacBook Pro should do DMA on the b43. Apple makes wierd hardware, but 
> not likely that wierd.

I have been unable to get DMA to work in the past.  So I have been 
configuring it with PIO=1 (/etc/modprobe,d/b43.conf):

     options b43 pio=1 qos=0

>
> Does dmesg offer any clues as to what is happening?
>
If I try with, say:

     options b43 pio=0 qos=0 verbose=3

Then

     rmmod b43
     rmmod ssb
     modprobe b43

I see the following:

     insmod /lib/modules/6.1.12-arch1-1/kernel/drivers/ssb/ssb.ko.zst
     insmod 
/lib/modules/6.1.12-arch1-1/kernel/drivers/net/wireless/broadcom/b43/b43.ko.zst 
pio=0 qos=0 verbose=3

...

[Jun25 11:51] ssb: Found chip with id 0x4322, rev 0x01 and package 0x0A
[  +0.096950] b43-pci-bridge 0000:02:00.0: Sonics Silicon Backplane 
found on PCI device 0000:02:00.0
[  +0.411653] b43-phy1: Broadcom 4322 WLAN found (core revision 16)
[  +0.038206] b43-phy1: Found PHY: Analog 8, Type 4 (N), Revision 4
[  +0.000032] b43-phy1: Found Radio: Manuf 0x17F, ID 0x2056, Revision 3, 
Version 0
[  +0.015660] Broadcom 43xx driver loaded [ Features: PNLS ]
[  +0.520933] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[  +0.726559] b43-phy1: Loading firmware version 784.2 (2012-08-15 21:35:19)
[  +0.276596] b43-phy1 debug: Chip initialized
[  +0.000562] b43-phy1 debug: 64-bit DMA initialized
[  +0.000013] b43-phy1 debug: QoS disabled
[  +0.023145] b43-phy1 debug: Wireless interface started
[  +0.056159] b43-phy1 debug: Adding Interface type 2
[  +0.086691] b43-phy1 debug: Removing Interface type 2
[  +0.000105] b43-phy1 debug: Wireless interface stopped
[  +0.099849] b43-phy1 ERROR: DMA RX reset timed out
[  +0.065067] b43 ssb0:0: Timeout waiting for bitmask 01800000 on 
register 0F90 to clear
[  +0.204905] b43-phy1: Loading firmware version 784.2 (2012-08-15 21:35:19)
[  +0.296681] b43-phy1 debug: Chip initialized
[  +0.000555] b43-phy1 debug: 64-bit DMA initialized
[  +0.000010] b43-phy1 debug: QoS disabled
[  +0.027099] b43-phy1 debug: Wireless interface started
[  +0.062503] b43-phy1 debug: Adding Interface type 2

The wlan0 device never seems to work, no IP address is obtained, etc.

> If there is nothing shown in the log, you definitely need to do a 
> proper bisection from the mainline git tree to isolate the change that 
> led to this failure.

Still working on initial kernel build.

> ADDED WITH EDIT: I looked at the code and b43 will not be built for 
> any hardware without DMA, thus it appears that adding "b43.pio=1" is 
> the only way to get PIO mode. Please check the output of dmesg for PIO 
> messages.
>
> Larry

Thanks & regards,

Sardonimous


  reply	other threads:[~2023-06-25 16:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24  1:44 Fwd: After kernel 6.3.7 or 6.3.8 b43 driver fails Bagas Sanjaya
2023-06-24  8:50 ` Michael Büsch
2023-06-24  9:29   ` Arnd Bergmann
2023-06-24 14:00     ` Linux regression tracking (Thorsten Leemhuis)
2023-06-24 16:22       ` Larry Finger
2023-06-24 21:32 ` Fwd: " Arnd Bergmann
     [not found]   ` <RO2P215MB193850DDADD38492BEC8CC2FA720A@RO2P215MB1938.LAMP215.PROD.OUTLOOK.COM>
2023-06-25  0:50     ` Bagas Sanjaya
2023-06-25  2:09       ` Larry Finger
2023-06-25  4:41       ` Larry Finger
2023-06-25 16:58         ` Sardonimous [this message]
2023-06-25 18:12           ` Arnd Bergmann
2023-06-25 18:17             ` Larry Finger
2023-06-25 21:11               ` Sardonimous
2023-06-25 23:05                 ` Larry Finger
2023-06-26 12:44                   ` Sardonimous
2023-06-26 15:21                     ` Larry Finger
2023-06-26 21:33                       ` Sardonimous
2023-06-27  0:31                         ` Larry Finger
2023-07-03 17:35                         ` Larry Finger
2023-07-03 20:13                           ` Sardonimous
2023-07-04  8:30                             ` Linux regression tracking #update (Thorsten Leemhuis)

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=RO2P215MB193879B2D99DD0BAF59EFA92A721A@RO2P215MB1938.LAMP215.PROD.OUTLOOK.COM \
    --to=sardonimous@hotmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=arnd@arndb.de \
    --cc=bagasdotme@gmail.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=m@bues.ch \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=simon.horman@corigine.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).