linux-kernel - Re: Fwd: After kernel 6.3.7 or 6.3.8 b43 driver fails

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 24 Jun 2023 23:41:11 -0500
From:   Larry Finger <Larry.Finger@...inger.net>
To:     Bagas Sanjaya <bagasdotme@...il.com>,
        "Sardonimous ." <sardonimous@...mail.com>,
        Arnd Bergmann <arnd@...db.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Linux Wireless <linux-wireless@...r.kernel.org>,
        Netdev <netdev@...r.kernel.org>
Cc:     Michael Büsch <m@...s.ch>,
        kernel test robot <lkp@...el.com>,
        Simon Horman <simon.horman@...igine.com>,
        Kalle Valo <kvalo@...nel.org>
Subject: Re: Fwd: After kernel 6.3.7 or 6.3.8 b43 driver fails

On 6/24/23 19:50, Bagas Sanjaya wrote:
> On 6/25/23 04:47, Sardonimous . wrote:
>> A newer report with the missing top lines:
>>
> 
> tl;dr:
> 
>> A: http://en.wikipedia.org/wiki/Top_post
>> Q: Were do I find info about this thing called top-posting?
>> A: Because it messes up the order in which people normally read text.
>> Q: Why is top-posting such a bad thing?
>> A: Top-posting.
>> Q: What is the most annoying thing in e-mail?
>>
>> A: No.
>> Q: Should I include quotations after my reply?
>>
>> http://daringfireball.net/2007/07/on_top
> 
> Also, please send plain-text email: I don't see your dmesg on
> lore.kernel.org archive because you send HTML email instead.
> 
> But anyway, I'm pasting yours from Bugzilla thread instead
> (as Arnd requested):
> 
> ```
> Jun 20 18:20:11 askasleikir kernel: ------------[ cut here ]------------
> Jun 20 18:20:11 askasleikir kernel: WARNING: CPU: 1 PID: 33 at net/mac80211/util.c:514 __ieee80211_stop_queue+0xcc/0xe0 [mac80211]
> Jun 20 18:20:11 askasleikir kernel: Modules linked in: ccm tun qrtr rpcrdma rdma_cm iw_cm ib_cm ib_core nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver fscache net>
> Jun 20 18:20:11 askasleikir kernel:  lockd grace crypto_user sunrpc fuse dm_mod loop bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 sr_mod>
> Jun 20 18:20:11 askasleikir kernel: CPU: 1 PID: 33 Comm: kworker/u4:2 Tainted: G        W          6.3.6-arch1-1 #1 a07497485287c74e7a472f42ded4b2ddcf7a6fd7
> Jun 20 18:20:11 askasleikir kernel: Hardware name: Apple Inc. MacBookPro7,1/Mac-F222BEC8, BIOS    MBP71.88Z.0039.B15.1702241313 02/24/17
> Jun 20 18:20:11 askasleikir kernel: Workqueue: phy0 b43_tx_work [b43]
> Jun 20 18:20:11 askasleikir kernel: RIP: 0010:__ieee80211_stop_queue+0xcc/0xe0 [mac80211]
> Jun 20 18:20:11 askasleikir kernel: Code: 74 11 48 8b 78 08 0f b7 d6 89 e9 4c 89 e6 e8 fb ea 00 00 65 ff 0d 2c 2d ac 3e 0f 85 55 ff ff ff e8 d9 44 69 c3 e9 4b ff>
> Jun 20 18:20:11 askasleikir kernel: RSP: 0018:ffffb3538013bdb8 EFLAGS: 00010097
> Jun 20 18:20:11 askasleikir kernel: RAX: 0000000000000001 RBX: 0000000000000002 RCX: 0000000000000000
> Jun 20 18:20:11 askasleikir kernel: RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff9e55cfa248e0
> Jun 20 18:20:11 askasleikir kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 000000008010000f
> Jun 20 18:20:11 askasleikir kernel: R10: 0000000000000005 R11: 0000000000000181 R12: ffff9e55cfa248e0
> Jun 20 18:20:11 askasleikir kernel: R13: 0000000000000000 R14: ffff9e55cfa26238 R15: ffff9e55cfa26090
> Jun 20 18:20:11 askasleikir kernel: FS:  0000000000000000(0000) GS:ffff9e55fbf00000(0000) knlGS:0000000000000000
> Jun 20 18:20:11 askasleikir kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> Jun 20 18:20:11 askasleikir kernel: CR2: 00007f37cce5d180 CR3: 0000000057620000 CR4: 00000000000406e0
> Jun 20 18:20:11 askasleikir kernel: Call Trace:
> Jun 20 18:20:11 askasleikir kernel:  <TASK>
> Jun 20 18:20:11 askasleikir kernel:  ? __ieee80211_stop_queue+0xcc/0xe0 [mac80211 01be121fb223b347160617528f5dda900e828bc2]
> Jun 20 18:20:11 askasleikir kernel:  ? __warn+0x81/0x130
> Jun 20 18:20:11 askasleikir kernel:  ? __ieee80211_stop_queue+0xcc/0xe0 [mac80211 01be121fb223b347160617528f5dda900e828bc2]
> Jun 20 18:20:11 askasleikir kernel:  ? report_bug+0x171/0x1a0
> Jun 20 18:20:11 askasleikir kernel:  ? handle_bug+0x3c/0x80
> Jun 20 18:20:11 askasleikir kernel:  ? exc_invalid_op+0x17/0x70
> Jun 20 18:20:11 askasleikir kernel:  ? asm_exc_invalid_op+0x1a/0x20
> Jun 20 18:20:11 askasleikir kernel:  ? __ieee80211_stop_queue+0xcc/0xe0 [mac80211 01be121fb223b347160617528f5dda900e828bc2]
> Jun 20 18:20:11 askasleikir kernel:  ? __slab_free+0xe0/0x310
> Jun 20 18:20:11 askasleikir kernel:  ieee80211_stop_queue+0x36/0x50 [mac80211 01be121fb223b347160617528f5dda900e828bc2]
> Jun 20 18:20:11 askasleikir kernel:  b43_pio_tx+0x373/0x390 [b43 3dc9b3f0fd98e2a659c64e057bd3b22d977e5228]
> Jun 20 18:20:11 askasleikir kernel:  b43_tx_work+0x57/0x130 [b43 3dc9b3f0fd98e2a659c64e057bd3b22d977e5228]
> Jun 20 18:20:11 askasleikir kernel:  process_one_work+0x1c7/0x3d0
> Jun 20 18:20:11 askasleikir kernel:  worker_thread+0x51/0x390
> Jun 20 18:20:11 askasleikir kernel:  ? __pfx_worker_thread+0x10/0x10
> Jun 20 18:20:11 askasleikir kernel:  kthread+0xde/0x110
> Jun 20 18:20:11 askasleikir kernel:  ? __pfx_kthread+0x10/0x10
> Jun 20 18:20:11 askasleikir kernel:  ret_from_fork+0x2c/0x50
> Jun 20 18:20:11 askasleikir kernel:  </TASK>
> Jun 20 18:20:11 askasleikir kernel: ---[ end trace 0000000000000000 ]---
> Jun 20 18:20:11 askasleikir kernel: ------------[ cut here ]------------

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.

Does dmesg offer any clues as to what is happening?

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.



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