From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Cc: amol.jawale@candelatech.com,
Gregory Greenman <gregory.greenman@intel.com>
Subject: Re: ax200 reliable crash in 100Mbps bi-directional traffic test.
Date: Tue, 11 Apr 2023 11:34:45 -0700 [thread overview]
Message-ID: <3b69f7f8-ff7f-aad3-e344-db4e69b85331@candelatech.com> (raw)
In-Reply-To: <14dacce8ccf2f6b69fbeb49b92f864de9bdd216d.camel@sipsolutions.net>
On 4/11/23 11:00, Johannes Berg wrote:
> On Tue, 2023-04-11 at 10:09 -0700, Ben Greear wrote:
>> Hello,
>>
>> Our test team reports that they get reliable firmware crashes on ax200 radios against multiple
>> APs when running 100Mbps UL + DL traffic (100Mbps in both directions).
>>
>> This happens on 5.19-ish kernels as well as 6.2.9+.
>> ax210 radios in same setup are much more stable.
>>
>> Please let us know if you would like additional debug information, including binary
>> crash dump files from the radio....
>>
>> [19241.588542] sta0001: Limiting TX power to 27 (30 - 3) dBm as advertised by 28:80:88:f3:b2:00
>> 4[19245.998099] iwlwifi 0000:12:00.0: Microcode SW error detected. Restarting 0x0.
>> 5[19246.004160] iwlwifi 0000:12:00.0: Start IWL Error Log Dump:
>> 6[19246.008457] iwlwifi 0000:12:00.0: Transport status: 0x0000004B, valid: 6
>> 7[19246.013867] iwlwifi 0000:12:00.0: Loaded firmware version: 72.daa05125.0 cc-a0-72.ucode
>> 8[19246.020573] iwlwifi 0000:12:00.0: 0x000022CE | ADVANCED_SYSASSERT
>>
>
> Pretty sure this means that the RX was faster than the CPU was
> processing, but why would that happen at 100 Mbps?
The system should not be overly stressed in this case, and the hardware in general can run
at multi-gig speeds. But, the CPU could be slowed down periodically for some other reason,
and possibly there were several other radios in the system. We'll provide some better details
on the hardware setup.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2023-04-11 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 17:09 ax200 reliable crash in 100Mbps bi-directional traffic test Ben Greear
2023-04-11 18:00 ` Johannes Berg
2023-04-11 18:34 ` Ben Greear [this message]
2023-04-13 18:25 ` Ben Greear
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=3b69f7f8-ff7f-aad3-e344-db4e69b85331@candelatech.com \
--to=greearb@candelatech.com \
--cc=amol.jawale@candelatech.com \
--cc=gregory.greenman@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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).