Hi, With this commit the kernel doesn't load the firmware and I lost my wifi device, But without this commit the firmware load fine without a kernel panic. kernel 6.0.15/6.1.3 brcmfmac 0000:02:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) kernel 6.0.17 brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4366/4 wl0: Nov 5 2018 03:19:56 version 10.28.2 (r769115) FWID 01-d2cbb8fd PCI info : 02:00.0 Network controller: Broadcom Inc. and subsidiaries Device 43c3 (rev 04) Subsystem: ASUSTeK Computer Inc. Device 86fb Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at f7000000 (64-bit, non-prefetchable) [size=32K] Memory at f6800000 (64-bit, non-prefetchable) [size=8M] Memory at f2400000 (64-bit, prefetchable) [size=4M] Capabilities: <access denied> Kernel driver in use: brcmfmac Kernel modules: brcmfmac Christian
kernel version should be 6.0.17/6.1.3 and 6.0.15 Christian
*** Bug 216893 has been marked as a duplicate of this bug. ***
Please CC (send your entire bug report): wright dot feng AT cypress dot com He's not on this bugzilla.
CC sent to Wright Feng
This address return bounces. Sent with two different address email.
The regression was introduced by following commit: https://lore.kernel.org/all/20220929031001.9962-3-ian.lin@infineon.com/ This has also been reported on the linux-wireless list. Regards, Arend
Created attachment 303558 [details] increase invalid max flowring limit Attached possible patch for the reported issue. Please provide feedback.
Of course this patch solve this issue.
Would be nice to know why the patch proposed in this bug isn't applied to 6.1.7 Christian
(In reply to Christian Marillat from comment #9) > Would be nice to know why the patch proposed in this bug isn't applied to > 6.1.7 It would be nice if you pay attention. It has been applied earlier this week on the wireless repo. It has to go to networking repo and then land in Linus' tree before it will be taken by the stable maintainers. So it will take a week or two. Please be patient. Regards, Arend