From: Luca Coelho <luca@coelho.fi>
To: Seraphime Kirkovski <kirkseraph@gmail.com>,
linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 4.14.0-rc3 iwlwifi: Hardware became unavailable during restart
Date: Wed, 11 Oct 2017 10:47:50 +0300 [thread overview]
Message-ID: <1507708070.908.216.camel@coelho.fi> (raw)
In-Reply-To: <20171010074414.x3uqv27prkqov45v@macchiaveli>
On Tue, 2017-10-10 at 09:44 +0200, Seraphime Kirkovski wrote:
> Hello,
Hi Seraphime,
> I've got this splat after a couple of suspend-resume cycles on my
> HP-laptop. I haven't had the time to bisect or test other rcs for now.
> Pasting some logs before the actual WARN_ON, as they may be relevant.
> Just after the splat the connection is successfully reestablished.
>
> [14293.758404] iwlwifi 0000:24:00.0: Error sending REPLY_SCAN_ABORT_CMD:
> time out after 2000ms.
> [14293.758429] iwlwifi 0000:24:00.0: Current CMD queue read_ptr 67 write_ptr 68
> [14293.758518] iwlwifi 0000:24:00.0: Loaded firmware version: 18.168.6.1
This seems to be a DVM device (iwldvm). What is the exact device
model? And you have never noticed this problem before?
Unfortunately this is a very old device and we don't support it
actively anymore. Hopefully this will turn out to be a trivial fix in
the driver side, so we can get it solved for you.
The best way to track this is to report it in
https://bugzilla.kernel.org.
--
Cheers,
Luca.
prev parent reply other threads:[~2017-10-11 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 7:44 4.14.0-rc3 iwlwifi: Hardware became unavailable during restart Seraphime Kirkovski
2017-10-11 7:47 ` Luca Coelho [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=1507708070.908.216.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=kirkseraph@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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