From: cantabile <cantabile.desu@gmail.com>
To: Jakub Kicinski <kubakici@wp.pl>, "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mt7601u: Fix system freeze after resuming from hibernation
Date: Tue, 27 Feb 2018 14:25:55 +0200 [thread overview]
Message-ID: <3382fa4d-c652-68eb-13c3-12dc84ba0dd5@gmail.com> (raw)
In-Reply-To: <20180226182859.03184215@cakuba.netronome.com>
On 27/02/18 04:28, Jakub Kicinski wrote:
> On Sun, 25 Feb 2018 17:54:25 +0000, Luis R. Rodriguez wrote:
>> I want to understand the case where the firmware is *not* available on resume?
>> Why did that happen? I seem to have read that on a fresh reboot the firmware
>> was not needed, and so on probe request_firmware() was not called? Why would
>> firmware not be required on a reboot?
>
> Yes, that is a good question.. John, do you have a theory? My initial
> thought was that the UEFI/BIOS loads it during pre-boot, but this is a
> USB card, so it's a bit unlikely that UEFI will have a driver for it...
> Does this happen when rebooting maybe?
>
Yes, it happens when rebooting:
1) Plug in the dongle. Message about firmware appears in dmesg:
mt7601u 2-3:1.0: ASIC revision: 76010001 MAC revision: 76010500
mt7601u 2-3:1.0: Firmware Version: 0.1.00 Build: 7640 Build time:
201302052146____
mt7601u 2-3:1.0: Warning: unsupported EEPROM version 0d
2) `systemctl reboot`. Message about firmware does not appear in dmesg:
mt7601u 2-3:1.0: ASIC revision: 76010001 MAC revision: 76010500
mt7601u 2-3:1.0: Warning: unsupported EEPROM version 0d
The dongle is nevertheless perfectly functional after rebooting.
I have no idea why it works like this.
This is an older laptop, no UEFI.
next prev parent reply other threads:[~2018-02-27 12:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 11:34 [PATCH] mt7601u: Fix system freeze after resuming from hibernation cantabile
2018-02-15 0:45 ` Jakub Kicinski
2018-02-15 11:38 ` cantabile
2018-02-15 21:47 ` Jakub Kicinski
2018-02-17 11:23 ` cantabile
2018-02-19 5:55 ` Jakub Kicinski
2018-02-19 15:01 ` cantabile
2018-02-25 17:54 ` Luis R. Rodriguez
2018-02-27 2:28 ` Jakub Kicinski
2018-02-27 12:25 ` cantabile [this message]
2018-02-27 16:54 ` Luis R. Rodriguez
2018-02-27 18:22 ` Jakub Kicinski
2018-02-27 20:42 ` Luis R. Rodriguez
2018-02-28 18:02 ` cantabile
2018-02-28 18:48 ` Luis R. Rodriguez
2018-02-28 19:18 ` Arend van Spriel
2018-02-28 20:41 ` Luis R. Rodriguez
2018-02-28 21:18 ` cantabile
2018-03-01 0:28 ` Luis R. Rodriguez
2018-03-01 14:05 ` cantabile
2018-03-01 17:29 ` Luis R. Rodriguez
2018-03-01 20:11 ` cantabile
2018-03-01 21:01 ` Luis R. Rodriguez
2018-03-02 10:43 ` cantabile
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=3382fa4d-c652-68eb-13c3-12dc84ba0dd5@gmail.com \
--to=cantabile.desu@gmail.com \
--cc=kubakici@wp.pl \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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).