linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: linux-kernel@vger.kernel.org,  linux-wireless@vger.kernel.org,
	 "Linux regression tracking (Thorsten Leemhuis)"
	<regressions@leemhuis.info>,
	linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	 Felix Fietkau <nbd@nbd.name>,
	Lorenzo Bianconi <lorenzo@kernel.org>,
	 Ryder Lee <ryder.lee@mediatek.com>,
	 Shayne Chen <shayne.chen@mediatek.com>,
	 Sean Wang <sean.wang@mediatek.com>,
	 Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Peter Chiu <chui-hao.chiu@mediatek.com>,
	 StanleyYP Wang <StanleyYP.Wang@mediatek.com>,
	 Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] MT7915E doesn't work any more with v6.9
Date: Wed, 15 May 2024 08:18:16 +0300	[thread overview]
Message-ID: <87le4birfr.fsf@kernel.org> (raw)
In-Reply-To: <6061263.lOV4Wx5bFT@natalenko.name> (Oleksandr Natalenko's message of "Wed, 15 May 2024 00:43:40 +0200")

Oleksandr Natalenko <oleksandr@natalenko.name> writes:

> Hello Felix, Lorenzo et al.
>
> With v6.9 kernel the following card:
>
> 01:00.0 Unclassified device [0002]: MEDIATEK Corp. MT7915E 802.11ax
> PCI Express Wireless Network Adapter [14c3:7915]
>
> doesn't work any more. Upon mt7915e module insertion the following splat happens:
>
> mt7915e 0000:01:00.0: enabling device (0000 -> 0002)
> WARNING: CPU: 3 PID: 1648 at net/mac80211/main.c:794
> ieee80211_alloc_hw_nm+0x9a3/0x9f0 [mac80211]
> Call Trace:
>  <TASK>
>  mt76_alloc_device+0x24/0x290 [mt76 46e2c4f11be089903469a4d6045c71cb7842b4cd]
>  mt7915_mmio_probe+0x33/0x1d0 [mt7915e 9657e1926e619568545a08636674805d5e665c85]
>  mt7915_pci_probe+0xe1/0x3a0 [mt7915e 9657e1926e619568545a08636674805d5e665c85]
>  pci_device_probe+0xf0/0x2d0
>  really_probe+0xde/0x3b0
>  __driver_probe_device+0x78/0x110
>  driver_probe_device+0x1f/0x130
>  __driver_attach+0x91/0x1e0
>  bus_for_each_dev+0x105/0x160
>  bus_add_driver+0x137/0x270
>  driver_register+0x72/0xd0
>  mt7915_init+0x44/0xff0 [mt7915e 9657e1926e619568545a08636674805d5e665c85]
>  do_one_initcall+0x5b/0x310
>  do_init_module+0x60/0x220
>  init_module_from_file+0x89/0xe0
>  idempotent_init_module+0x121/0x2b0
>  __x64_sys_finit_module+0x5e/0xb0
>  do_syscall_64+0x82/0x160
>  entry_SYSCALL_64_after_hwframe+0x76/0x7e
> mt7915e 0000:01:00.0: probe with driver mt7915e failed with error -12
>
> and the card stays non-functional. Re-inserting the module triggers
> the same behaviour.
>
> The following condition is triggered:
>
>  794                 if (WARN_ON(!ops->add_chanctx ||
>  795                             !ops->remove_chanctx ||
>  796                             !ops->change_chanctx ||
>  797                             !ops->assign_vif_chanctx ||
>  798                             !ops->unassign_vif_chanctx))
>  799                         return NULL;
>
> This worked with v6.8 and earlier just fine.

Thanks for the report. I'll add this to regzbot for easier tracking:

#regzbot introduced: v6.8..v6.9 ^

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2024-05-15  5:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 22:43 [REGRESSION] MT7915E doesn't work any more with v6.9 Oleksandr Natalenko
2024-05-14 22:51 ` Oleksandr Natalenko
2024-05-15  5:20   ` Kalle Valo
2024-05-15  6:23   ` Johannes Berg
2024-05-15  7:15     ` Oleksandr Natalenko
2024-05-15  7:40       ` Linux regression tracking (Thorsten Leemhuis)
2024-05-15  7:56         ` Greg KH
2024-05-15  7:48       ` Kalle Valo
2024-05-15  7:44     ` Kalle Valo
2024-05-25  6:26     ` Kalle Valo
2024-05-25  6:35       ` Kalle Valo
2024-05-27 18:29       ` Greg KH
2024-05-27 18:30         ` Johannes Berg
2024-05-15  5:18 ` Kalle Valo [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=87le4birfr.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=StanleyYP.Wang@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chui-hao.chiu@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=nbd@nbd.name \
    --cc=oleksandr@natalenko.name \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).