From: Kalle Valo <kvalo@kernel.org>
To: Chris Bainbridge <chris.bainbridge@gmail.com>
Cc: linux-wireless@vger.kernel.org, benjamin.berg@intel.com,
miriam.rachel.korenblit@intel.com, regressions@lists.linux.dev,
johannes@sipsolutions.net
Subject: Re: [REGRESSION] bisected: iwlwifi: use already mapped data when TXing an AMSDU
Date: Wed, 07 Aug 2024 16:49:32 +0300 [thread overview]
Message-ID: <87o7644f4j.fsf@kernel.org> (raw)
In-Reply-To: <CAP-bSRboZLWg4pzHHrD66NFeKKbsX0z-wUcxJS4OYmzcHXdG1w@mail.gmail.com> (Chris Bainbridge's message of "Wed, 7 Aug 2024 13:34:38 +0100")
Chris Bainbridge <chris.bainbridge@gmail.com> writes:
> On Wed, 7 Aug 2024 at 13:10, Kalle Valo <kvalo@kernel.org> wrote:
>>
>> Chris Bainbridge <chris.bainbridge@gmail.com> writes:
>>
>> > I hit the following bug in 6.11.0-rc2. Reverting the offending commit
>> > fixes the issue. This happens immediately when I run `iperf3 -bidir`.
>>
>> [...]
>>
>> > [ 42.873868] ------------[ cut here ]------------
>> > [ 42.873989] WARNING: CPU: 1 PID: 529 at
>> > drivers/net/wireless/intel/iwlwifi/pcie/tx.c:1836
>> > iwl_pcie_get_sgt_tb_phys
>> > (drivers/net/wireless/intel/iwlwifi/pcie/tx.c:1836) iwlwifi
>>
>> Does the connection still work after the warning?
>
> Not really. It is functional but tx throughput is severely degraded,
> iperf shows ~1mbit/sec instead of the usual ~600mbit. Rx throughput
> (measured with `iperf -c ... -R`) doesn't seem to be affected.
Ok, so a quite severe issue. Hopefully Intel can find a fix, otherwise
we need to consider should we revert commit 90db50755228 ("wifi:
iwlwifi: use already mapped data when TXing an AMSDU") for v6.11.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-08-07 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 10:51 [REGRESSION] bisected: iwlwifi: use already mapped data when TXing an AMSDU Chris Bainbridge
2024-08-07 12:10 ` Kalle Valo
2024-08-07 12:34 ` Chris Bainbridge
2024-08-07 13:49 ` Kalle Valo [this message]
2024-08-07 13:59 ` Berg, Benjamin
2024-08-07 14:18 ` Kalle Valo
2024-08-07 12:42 ` Berg, Benjamin
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=87o7644f4j.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=benjamin.berg@intel.com \
--cc=chris.bainbridge@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=regressions@lists.linux.dev \
/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 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.