linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: "Íñigo Huguet" <ihuguet@redhat.com>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	sean.wang@mediatek.com,
	Linux List Kernel Mailing <linux-wireless@vger.kernel.org>,
	objelf@gmail.com, lorenzo@kernel.org, Soul.Huang@mediatek.com,
	nbd@nbd.name, linux-pci@vger.kernel.org
Subject: Re: [Bug] Driver mt7921e cause computer reboot.
Date: Mon, 27 Dec 2021 16:30:11 +0500	[thread overview]
Message-ID: <CABXGCsOX72u3yDcGNF64zbm5mC+Z=_8rxKM0cu7m4i1D8iWvbA@mail.gmail.com> (raw)
In-Reply-To: <CACT4oud-7rpKgcapoNY7Ywd0socwQ-5BPteOxe7S7RNCaUzN+A@mail.gmail.com>

On Mon, 27 Dec 2021 at 15:11, Íñigo Huguet <ihuguet@redhat.com> wrote:
> I've been experiencing similar problems, but they're solved at v5.15
> version, at least for me.
>
> How are you installing the kernel? Custom build? Have you updated the
> firmware to latest versions, as well?

I use Fedora Rawhide with default kernel and firmware packages.

$ uname -r
5.16.0-0.rc6.20211223gitbc491fb12513.44.fc36.x86_64
$ rpm -q linux-firmware
linux-firmware-20211027-126.fc36.noarch

>
> For me, these differences seem to be the normal effect of the driver
> not recognizing the device.

By the kernel logs, it looks like this:
After reboot:
$ dmesg | grep mt7921e
[    8.629358] mt7921e 0000:05:00.0: enabling device (0000 -> 0002)
[    8.630229] mt7921e 0000:05:00.0: ASIC revision: 79610010
[    9.687652] mt7921e: probe of 0000:05:00.0 failed with error -110

# rmmod mt7921e
# modprobe mt7921e

[  215.514503] mt7921e 0000:05:00.0: ASIC revision: feed0000
[  216.604741] mt7921e: probe of 0000:05:00.0 failed with error -110

After cold boot after shutdown:
$ dmesg | grep mt7921e
[    8.545171] mt7921e 0000:05:00.0: enabling device (0000 -> 0002)
[    8.545757] mt7921e 0000:05:00.0: ASIC revision: 79610010
[    8.631156] mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build
Time: 20211014150838a
[    8.912687] mt7921e 0000:05:00.0: WM Firmware Version: ____010000,
Build Time: 20211014150922
[    8.938756] mt7921e 0000:05:00.0: Firmware init done
[    9.753257] mt7921e 0000:05:00.0 wlp5s0: renamed from wlan0

It looks like something is not re-initialized after a reboot.
Laptop BIOS is latest: Version 316
https://dlcdnets.asus.com/pub/ASUS/GamingNB/G513QY/G513QYAS316.zip

Maybe anyone from the pci mailing list can lid some light why pci
device not re-initialized after a reboot?

-- 
Best Regards,
Mike Gavrilov.

  reply	other threads:[~2021-12-27 11:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21  9:33 [Bug] Driver mt7921e cause computer reboot Mikhail Gavrilov
2021-10-04 20:40 ` Mikhail Gavrilov
2021-11-25 22:39   ` Mikhail Gavrilov
2021-12-27 10:11     ` Íñigo Huguet
2021-12-27 11:30       ` Mikhail Gavrilov [this message]
2021-12-30  0:21         ` Bjorn Helgaas

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='CABXGCsOX72u3yDcGNF64zbm5mC+Z=_8rxKM0cu7m4i1D8iWvbA@mail.gmail.com' \
    --to=mikhail.v.gavrilov@gmail.com \
    --cc=Soul.Huang@mediatek.com \
    --cc=ihuguet@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=nbd@nbd.name \
    --cc=objelf@gmail.com \
    --cc=sean.wang@mediatek.com \
    /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).