[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7a8e220d77d7e30a0cfaf984404ef2f57eaa785f.camel@sipsolutions.net>
Date: Tue, 11 Jun 2024 16:50:48 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Fabio Estevam <festevam@...il.com>
Cc: miriam.rachel.korenblit@...el.com, kvalo@...nel.org, Jakub Kicinski
<kuba@...nel.org>, linux-wireless <linux-wireless@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: iwlwifi: Regression after migrating to 6.6.32
On Tue, 2024-06-11 at 11:32 -0300, Fabio Estevam wrote:
> Hi Johannes,
>
> I forgot to mention, but the Wifi device I am using is:
>
> Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
>
> On Tue, Jun 11, 2024 at 10:54 AM Johannes Berg
> <johannes@...solutions.net> wrote:
>
> > > [ 5.038174] rxb->offset is 0 trans_pcie->rx_buf_bytes is 4096
> >
> > so that looks pretty normal?
> >
> > Might be useful to see rx->page_dma too, supported_dma_mask should be
> > 4095 or 2047 depending on the device, but I'm not sure how you could end
> > up with a DMA mapping for a page that's not at least 11 bit aligned?
>
> Here it goes:
>
> [ 4.344218] rxb->offset is 0 trans_pcie->rx_buf_bytes is 4096
> rxb->page_dma is 4215433216 trans_pcie->supported_dma_mask is 4095
> I don't know what a typical rxb->page_dma should be.
>
It should be an address (so that's fine), but I don't see how it ends up
not being page-aligned if we request to map a page and 4096 bytes??
Is that platform "weird" with strange page size, or something?
johannes
Powered by blists - more mailing lists