From: Sasha Levin <sashal@kernel.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.19] mt76: mt76x0u: do not reset radio on resume
Date: Wed, 4 Sep 2019 07:59:35 -0400 [thread overview]
Message-ID: <20190904115935.GV5281@sasha-vm> (raw)
In-Reply-To: <20190904080704.GA2704@redhat.com>
On Wed, Sep 04, 2019 at 10:07:10AM +0200, Stanislaw Gruszka wrote:
>commit 8f2d163cb26da87e7d8e1677368b8ba1ba4d30b3 upstream.
>
>On some machines mt76x0u firmware can hung during resume,
>what result on messages like below:
>
>[ 475.480062] mt76x0 1-8:1.0: Error: MCU response pre-completed!
>[ 475.990066] mt76x0 1-8:1.0: Error: send MCU cmd failed:-110
>[ 475.990075] mt76x0 1-8:1.0: Error: MCU response pre-completed!
>[ 476.500003] mt76x0 1-8:1.0: Error: send MCU cmd failed:-110
>[ 476.500012] mt76x0 1-8:1.0: Error: MCU response pre-completed!
>[ 477.010046] mt76x0 1-8:1.0: Error: send MCU cmd failed:-110
>[ 477.010055] mt76x0 1-8:1.0: Error: MCU response pre-completed!
>[ 477.529997] mt76x0 1-8:1.0: Error: send MCU cmd failed:-110
>[ 477.530006] mt76x0 1-8:1.0: Error: MCU response pre-completed!
>[ 477.824907] mt76x0 1-8:1.0: Error: send MCU cmd failed:-71
>[ 477.824916] mt76x0 1-8:1.0: Error: MCU response pre-completed!
>[ 477.825029] usb 1-8: USB disconnect, device number 6
>
>and possible whole system freeze.
>
>This can be avoided, if we do not perform mt76x0_chip_onoff() reset.
>
>Cc: stable@vger.kernel.org
>Fixes: 134b2d0d1fcf ("mt76x0: init files")
>Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
>Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Queued up for 4.19, thank you!
--
Thanks,
Sasha
prev parent reply other threads:[~2019-09-04 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 8:07 [PATCH 4.19] mt76: mt76x0u: do not reset radio on resume Stanislaw Gruszka
2019-09-04 11:59 ` Sasha Levin [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=20190904115935.GV5281@sasha-vm \
--to=sashal@kernel.org \
--cc=sgruszka@redhat.com \
--cc=stable@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 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.