From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: intel AX200 crash on 5.2.7+
Date: Mon, 9 Sep 2019 10:54:32 -0700 [thread overview]
Message-ID: <9eae12b1-a5da-1943-0f81-90e05308ec82@candelatech.com> (raw)
In-Reply-To: <2e30e4df1eb69362f00db89efb133856ec96b755.camel@sipsolutions.net>
On 9/9/19 10:40 AM, Johannes Berg wrote:
> On Mon, 2019-09-09 at 10:03 -0700, Ben Greear wrote:
>> Hello,
>>
>> Looks like we managed to crash the AX200 firmware. This was running 5.2.7+ kernel
>> in an apu2 platform.
>>
>> Is there a better place to report/discuss this?
>
> This is OK for first reports, but usually we'll ask to file a bug on
> bugzilla.kernel.org (and assign to linuxwifi@intel.com if you can? Not
> sure it's possible - or add that to CC at least)
>
>> [ 6066.180908] iwlwifi 0000:01:00.0: 0x00000942 | ADVANCED_SYSASSERT
>
> Hmm, that's a calibration failure.
>
> Did you do anything special in that environment?
Nothing that I'm aware of. The person who found the crash said they had
run some throughput tests, and then the radio went away.
We put one of the radios in a more powerful system, and will continue
testing.
>
> I guess filing a bug would be best, so we have a record for it and can
> hand it off to the firmware team or similar.
I was able to add them to CC I think, but don't think I can re-assign the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=204801
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2019-09-09 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 17:03 intel AX200 crash on 5.2.7+ Ben Greear
2019-09-09 17:40 ` Johannes Berg
2019-09-09 17:54 ` Ben Greear [this message]
2019-10-03 17:51 ` 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=9eae12b1-a5da-1943-0f81-90e05308ec82@candelatech.com \
--to=greearb@candelatech.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).