From: Johannes Berg <johannes@sipsolutions.net>
To: Fabio Estevam <festevam@gmail.com>,
miriam.rachel.korenblit@intel.com, kvalo@kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: iwlwifi: Regression after migrating to 6.6.32
Date: Tue, 11 Jun 2024 14:52:56 +0200 [thread overview]
Message-ID: <3fbb5317d9ff33ef1b60ca8297537335ce86a79d.camel@sipsolutions.net> (raw)
In-Reply-To: <CAOMZO5A7+nxACoBPY0k8cOpVQByZtEV_N1489MK5wETHF_RXWA@mail.gmail.com>
On Tue, 2024-06-11 at 08:46 -0300, Fabio Estevam wrote:
>
> [ 6.995391] ------------[ cut here ]------------
> [ 7.373564] WARNING: CPU: 3 PID: 136 at
> /drivers/net/wireless/intel/iwlwifi/pcie/rx.c:269
> iwl_pcie_rxmq_restock+0x158/0x178 [iwlwifi]
>
This warning happens if DMA mapping/allocation returns a page that's not
page-aligned??
rxb->page_dma =
dma_map_page(trans->dev, page, rxb->offset,
trans_pcie->rx_buf_bytes,
DMA_FROM_DEVICE);
(or similar places), where rxb->offset will always be 0 unless
rx_buf_bytes is set to 2048, but that can only happen if the amsdu_size
module parameter is set to 4 (=2k) but that's not even supported any
more?
Maybe make this WARN_ONCE(...) with a string that has more info on the
addresses.
johannes
next prev parent reply other threads:[~2024-06-11 12:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 11:46 Fabio Estevam
2024-06-11 12:52 ` Johannes Berg [this message]
2024-06-11 13:43 ` Fabio Estevam
2024-06-11 13:54 ` Johannes Berg
2024-06-11 14:32 ` Fabio Estevam
2024-06-11 14:50 ` Johannes Berg
2024-06-11 14:59 ` Fabio Estevam
2024-06-12 19:10 ` Johannes Berg
2024-06-12 19:15 ` Fabio Estevam
2024-06-13 6:58 ` Johannes Berg
2024-06-13 7:10 ` Baochen Qiang
2024-06-13 7:40 ` Johannes Berg
2024-06-13 9:51 ` Baochen Qiang
2024-06-13 10:36 ` Johannes Berg
2024-06-13 20:15 ` Fabio Estevam
2024-06-17 12:08 ` Will Deacon
2024-06-17 14:08 ` Fabio Estevam
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=3fbb5317d9ff33ef1b60ca8297537335ce86a79d.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=festevam@gmail.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.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
all inboxes | Powered by JetHome®