From: "Michael Büsch" <m@bues.ch>
To: Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>,
Ryder Lee <ryder.lee@mediatek.com>,
Shayne Chen <shayne.chen@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mt7921: Oops in mt76_dma_rx_fill
Date: Wed, 9 Mar 2022 20:57:26 +0100 [thread overview]
Message-ID: <20220309205726.35337cb7@barney> (raw)
In-Reply-To: <20220209170550.0a73ebe4@barney>
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
Does anybody have an idea why this driver crashes?
I tried to bisect it. But that turns out to be very hard as the
intermediate versions are all very unstable, too. For various reasons.
Therefore, I aborted my bisect attempt.
But if you have an idea what patch I could try, I'd be very happy to
do so.
--
Michael Büsch
https://bues.ch/
On Wed, 9 Feb 2022 17:05:50 +0100
Michael Büsch <m@bues.ch> wrote:
> Hi,
>
> on the latest stable 5.16.8 (df659ebe) the Mediatek WLAN driver
> crashes on my machine in a DMA function.
>
> Please excuse me for the crappy photos. The first one has been
> captured out of a video. Therefore it's partially interleaved with the
> predecessor frame.
>
> https://bues.ch/misc/mt7921/mt7921_oops1.jpg
> https://bues.ch/misc/mt7921/mt7921_oops2.jpg
>
> Most of the time the crash happens right during system boot.
>
> The stable kernel 5.15.y does not crash. (However, I frequently get
> connection interruptions. But I'm not sure whether that's related to
> the driver.)
>
> 03:00.0 Network controller: MEDIATEK Corp. MT7921 802.11ax PCI
> Express Wireless Network Adapter
>
> 03:00.0 0280: 14c3:7961
> Subsystem: 17aa:e0bc
> Physical Slot: 0
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF-
> FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed
> to IRQ 94 IOMMU group: 11
> Region 0: Memory at 670200000 (64-bit, prefetchable) [size=1M]
> Region 2: Memory at 670300000 (64-bit, prefetchable)
> [size=16K] Region 4: Memory at 670304000 (64-bit, prefetchable)
> [size=4K] Capabilities: <access denied>
> Kernel driver in use: mt7921e
> Kernel modules: mt7921e
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-03-09 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 16:05 mt7921: Oops in mt76_dma_rx_fill Michael Büsch
2022-03-09 19:57 ` Michael Büsch [this message]
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=20220309205726.35337cb7@barney \
--to=m@bues.ch \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.