From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Lukas Redlinger <lukas.redlinger@agilox.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] regular scan timed out
Date: Thu, 7 Feb 2019 23:07:54 +0200 [thread overview]
Message-ID: <CANUX_P1DpjTU4RQcnu9uzUa8xABwOe_Yc-QEjM5jWYB-3FbbDw@mail.gmail.com> (raw)
In-Reply-To: <588b2e78-a2f1-49f7-4a15-baa4f8658cc1@agilox.net>
>
> Hi there,
>
> Debian 10 testing, Intel 8265, firmware 36.9f0a2d68.0
>
> 2 interfaces on 1 phy: 1 managed, 1 AP
Fun, and you expect the AP to send NOAs when it goes away? (This is
what will happen I believe).
You can open a bug on bugzilla.kernel.org, refer to [1] to do so.
Please look at the 'Firmware debugging' section in [2] and provide a
firmware dump with the debug firmware you'll find there.
Note that this involves private data collection, you can read the
privacy notice [3] for further information.
Keep in mind that this is not exactly a common scenario and that
impacts the priority of the bug...
> ----------
>
> [ 715.890990] iwlwifi 0000:01:00.0: regular scan timed out
I am not really surprised although this should work I supposed
> [ 715.891047] iwlwifi 0000:01:00.0: Microcode SW error detected.
> Restarting 0x2000000.
> [ 715.891172] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
>
> [ 715.891175] iwlwifi 0000:01:00.0: Status: 0x00000100, count: 6
> [ 715.891177] iwlwifi 0000:01:00.0: Loaded firmware version: 36.9f0a2d68.0
> [ 715.891180] iwlwifi 0000:01:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
This event will automatically create a firmware dump.
[1] - https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#how_to_report
[2] - https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#firmware_debugging
[3] - https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#privacy_aspects
prev parent reply other threads:[~2019-02-07 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 15:04 [BUG] regular scan timed out Lukas Redlinger
2019-02-07 21:07 ` Emmanuel Grumbach [this message]
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=CANUX_P1DpjTU4RQcnu9uzUa8xABwOe_Yc-QEjM5jWYB-3FbbDw@mail.gmail.com \
--to=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lukas.redlinger@agilox.net \
/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.