From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: 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
Subject: Re: [Bug] Driver mt7921e cause computer reboot.
Date: Fri, 26 Nov 2021 03:39:03 +0500 [thread overview]
Message-ID: <CABXGCsMJOfGU8axS4FdGfPCgcPL5iuedpZxa4PETSyFHDckOAg@mail.gmail.com> (raw)
In-Reply-To: <CABXGCsMc1_-s5vVv=XVuMJaAtntrfHpCeT3h7wKkK71NuY-izw@mail.gmail.com>
On Tue, 5 Oct 2021 at 01:40, Mikhail Gavrilov
<mikhail.v.gavrilov@gmail.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:
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
--
Best Regards,
Mike Gavrilov.
next prev parent reply other threads:[~2021-11-25 22:42 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 [this message]
2021-12-27 10:11 ` Íñigo Huguet
2021-12-27 11:30 ` Mikhail Gavrilov
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=CABXGCsMJOfGU8axS4FdGfPCgcPL5iuedpZxa4PETSyFHDckOAg@mail.gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=Soul.Huang@mediatek.com \
--cc=linux-kernel@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