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]

Message-ID: <CACT4oud-7rpKgcapoNY7Ywd0socwQ-5BPteOxe7S7RNCaUzN+A@mail.gmail.com>
Date:   Mon, 27 Dec 2021 11:11:17 +0100
From:   Íñigo Huguet <ihuguet@...hat.com>
To:     Mikhail Gavrilov <mikhail.v.gavrilov@...il.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
Subject: Re: [Bug] Driver mt7921e cause computer reboot.

Hi,

On Thu, Nov 25, 2021 at 11:43 PM Mikhail Gavrilov
<mikhail.v.gavrilov@...il.com> wrote:
> With recent kernel 5.16.0-0.rc2 commit 5d9f4cf36721 the behavior has
> been changed for the better, but the WiFi adapter still works with
> bugs.
>
> Now spontaneous endless reboots do not occur. But if I restart the
> laptop instead of shutting down, then the next time I boot, the WiFi
> adapter disappears. In order for the WiFi adapter to appear again, it
> needs to turn off the laptop and then turn on. Can this be somehow
> fixed?
> lspci output after reboot and boot after shutdown is different:

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?

> After reboot:
> Subsystem: AzureWave Device 4680
> Flags: fast devsel, IRQ 84, IOMMU group 14
> Memory at fc30300000 (64-bit, prefetchable) [size=1M]
> Memory at fc30400000 (64-bit, prefetchable) [size=16K]
> Memory at fc30404000 (64-bit, prefetchable) [size=4K]
> Capabilities: [80] Express Endpoint, MSI 00
> Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
> Capabilities: [f8] Power Management version 3
> Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
> Capabilities: [108] Latency Tolerance Reporting
> Capabilities: [110] L1 PM Substates
> Capabilities: [200] Advanced Error Reporting
> Kernel modules: mt7921e
>
> After shutdown:
> 05:00.0 Network controller: MEDIATEK Corp. Device 7961
> Subsystem: AzureWave Device 4680
> Flags: bus master, fast devsel, latency 0, IRQ 85, IOMMU group 14
> Memory at fc30300000 (64-bit, prefetchable) [size=1M]
> Memory at fc30400000 (64-bit, prefetchable) [size=16K]
> Memory at fc30404000 (64-bit, prefetchable) [size=4K]
> Capabilities: [80] Express Endpoint, MSI 00
> Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+
> Capabilities: [f8] Power Management version 3
> Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
> Capabilities: [108] Latency Tolerance Reporting
> Capabilities: [110] L1 PM Substates
> Capabilities: [200] Advanced Error Reporting
> Kernel driver in use: mt7921e
> Kernel modules: mt7921e
>
> Screen of a visual comparison of lspci in meld: https://postimg.cc/642NKJ5Y

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

Regards
-- 
Íñigo Huguet