linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)"  <regressions@leemhuis.info>
To: Ryder Lee <ryder.lee@mediatek.com>,
	Lorenzo Bianconi <lorenzo@kernel.org>,
	Felix Fietkau <nbd@nbd.name>
Cc: Petr Tesarik <petr.tesarik.ext@huawei.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: [regression] Bug 217310 - mt7921e swiotlb buffer is full
Date: Wed, 12 Apr 2023 12:34:00 +0200	[thread overview]
Message-ID: <c63dab2b-906d-5383-39f9-b02e7d7d2659@leemhuis.info> (raw)

Hi, Thorsten here, the Linux kernel's regression tracker.

I noticed a regression report in bugzilla.kernel.org. As many (most?)
kernel developers don't keep an eye on it, I decided to forward it by mail.

Note, you have to use bugzilla to reach the reporter, as I sadly[1] can
not CCed them in mails like this.

Petr, I CCed you because you apparently dealt with another case with a
similar error message.

Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217310 :

>  Mike Lothian 2023-04-08 12:03:01 UTC
> 
> Created attachment 304097 [details]
> dmesg
> 
> Since the start of the 6.3 kernel cycle I've been having issues with my
> wifi when it's been going at high speeds, which usually requires me
> having to disable and re enable wifi to get it going again
> 
> When this happens I see this in the logs:
> 
> mt7921e 0000:05:00.0: swiotlb buffer is full (sz: 4096 bytes), total
> 32768 (slots), used 32160 (slots)
> 
> I'm running the latest firmware from
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> 
> And I don't see this on 6.2
> 
> I've attached my dmesg and the device is listed as:
> 
> 05:00.0 Network controller [0280]: MEDIATEK Corp. MT7921 802.11ax PCI
> Express Wireless Network Adapter [14c3:7961]

And later:

> I managed to work around it by setting swiotlb=131072

See the ticket for more details.


[TLDR for the rest of this mail: I'm adding this report to the list of
tracked Linux kernel regressions; the text you find below is based on a
few templates paragraphs you might have encountered already in similar
form.]

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: v6.2..v6.3-rc6
https://bugzilla.kernel.org/show_bug.cgi?id=217310
#regzbot title: dma-mapping: / net: wireless: mt7921e swiotlb buffer is full
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (e.g. the buzgzilla ticket and maybe this mail as well, if
this thread sees some discussion). See page linked in footer for details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

[1] because bugzilla.kernel.org tells users upon registration their
"email address will never be displayed to logged out users"

                 reply	other threads:[~2023-04-12 10:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=c63dab2b-906d-5383-39f9-b02e7d7d2659@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=nbd@nbd.name \
    --cc=petr.tesarik.ext@huawei.com \
    --cc=regressions@lists.linux.dev \
    --cc=ryder.lee@mediatek.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;
as well as URLs for NNTP newsgroup(s).