Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Mingyen Hsieh <mingyen.hsieh@mediatek.com>,
	nbd@nbd.name,  lorenzo@kernel.org
Cc: deren.wu@mediatek.com, Sean.Wang@mediatek.com,
	Leon.Yen@mediatek.com,  Michael.Lo@mediatek.com,
	allan.wang@mediatek.com, Eric-SY.Chang@mediatek.com,
		km.lin@mediatek.com, Quan.Zhou@mediatek.com,
	Ryder.Lee@mediatek.com, 	Shayne.Chen@mediatek.com,
	linux-wireless@vger.kernel.org,
		linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2] wifi: mt76: mt7921: Add PCIe AER handler support to prevent system crash
Date: Wed, 08 Oct 2025 11:12:04 +0200	[thread overview]
Message-ID: <d7eb196b01003a1de70456d5a31d9b4a37d555bd.camel@sipsolutions.net> (raw)
In-Reply-To: <20251008085916.1626952-1-mingyen.hsieh@mediatek.com>

Hi,

So ... yeah it's your driver, and yes it's already at v2, but ... this
still seems very much papering over a problem?

On Wed, 2025-10-08 at 16:59 +0800, Mingyen Hsieh wrote:
> 
> Unable to handle kernel paging request at virtual address ffffffc01099eac0
> pc : mt76_dma_add_buf+0x124/0x188 [mt76]

Why does it even crash there?

> +++ b/drivers/net/wireless/mediatek/mt76/agg-rx.c
> @@ -96,6 +96,9 @@ mt76_rx_aggr_reorder_work(struct work_struct *work)
>  	struct sk_buff_head frames;
>  	int nframes;
>  
> +	if (atomic_read(&dev->bus_hung) == 1)
> +		return;

And how does sprinkling this "magic dust" all over even do anything?


This sounds a bit like the driver isn't able to deal with surprise
removal, what happens if you e.g. rmmod it while running traffic? I
believe the effect of the error recovery would be similar, if you don't
handle it, so are you sure there's not a completely different underlying
bug?

johannes


  reply	other threads:[~2025-10-08  9:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08  8:59 [PATCH v2] wifi: mt76: mt7921: Add PCIe AER handler support to prevent system crash Mingyen Hsieh
2025-10-08  9:12 ` Johannes Berg [this message]
2026-07-14  1:21   ` Eason Lai (賴易聖)

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=d7eb196b01003a1de70456d5a31d9b4a37d555bd.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Eric-SY.Chang@mediatek.com \
    --cc=Leon.Yen@mediatek.com \
    --cc=Michael.Lo@mediatek.com \
    --cc=Quan.Zhou@mediatek.com \
    --cc=Ryder.Lee@mediatek.com \
    --cc=Sean.Wang@mediatek.com \
    --cc=Shayne.Chen@mediatek.com \
    --cc=allan.wang@mediatek.com \
    --cc=deren.wu@mediatek.com \
    --cc=km.lin@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=mingyen.hsieh@mediatek.com \
    --cc=nbd@nbd.name \
    /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