All of
 help / color / mirror / Atom feed
From: chainofflowers <>
Subject: Re: [PATCH 2/3] brcmfmac: return error when getting invalid max_flowrings from dongle
Date: Sun, 08 Jan 2023 20:53:20 +0000	[thread overview]
Message-ID: <4781984.GXAFRqVoOG@luna> (raw)
In-Reply-To: <>

Hi! This patch:

causes my Asus PCE-AC88 (1043:86fb) to stop working, because when modprobe 
loads brcmfmac it throws this error:
[ 2740.647600] brcmfmac 0000:0d:00.0: brcmf_pcie_init_ringbuffers: invalid 

This is also being reported on reddit:

(also, see

I think that the check on value > 256 is used as a kind of red herring to 
indirectly spot an inconsistent properties report from the PCI bus (?) about 
the network card.
Before that patch, the driver was correctly working for me and I could not 
observe any kernel panic. Maybe, at least in my case, the wrong value was 
still reported but could be safely ignored, as at a later point in time, when 
the card is initialised, everything worked fine.

I am now stuck at kernel 6.1.1, if I upgrade I cannot use the card.
Is there anything I can do to circumvent this issue? May I help somehow with 
debugging & testing? Please let me know...



  parent reply	other threads:[~2023-01-08 20:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29  3:09 [PATCH 0/3] brcmfmac: PCIE debug mechanism series Ian Lin
2022-09-29  3:09 ` [PATCH 1/3] brcmfmac: add a timer to read console periodically in PCIE bus Ian Lin
2022-10-04  7:07   ` Kalle Valo
2022-10-04  8:28   ` Kalle Valo
2022-10-10  9:53   ` Arend Van Spriel
2022-09-29  3:10 ` [PATCH 2/3] brcmfmac: return error when getting invalid max_flowrings from dongle Ian Lin
2022-10-10  9:58   ` Arend Van Spriel
2023-01-08 20:53   ` chainofflowers [this message]
2023-01-09  8:52     ` Arend van Spriel
2023-01-09 17:23       ` chainofflowers
2022-09-29  3:10 ` [PATCH 3/3] brcmfmac: dump dongle memory when attaching failed Ian Lin

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:

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

  git send-email \
    --in-reply-to=4781984.GXAFRqVoOG@luna \ \ \ \ \ \ \ \ \ \

* 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.