linux-kernel - Re: [Bug] Driver mt7921e cause computer reboot.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 27 Dec 2021 16:30:11 +0500
From:   Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To:     Íñigo Huguet <ihuguet@...hat.com>
Cc:     Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        sean.wang@...iatek.com,
        Linux List Kernel Mailing <linux-wireless@...r.kernel.org>,
        objelf@...il.com, lorenzo@...nel.org, Soul.Huang@...iatek.com,
        nbd@....name, linux-pci@...r.kernel.org
Subject: Re: [Bug] Driver mt7921e cause computer reboot.

On Mon, 27 Dec 2021 at 15:11, Íñigo Huguet <ihuguet@...hat.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.