Bug 218731
| Summary: | Tri-band AMD RZ608 (MediaTek MT7921K) has 6GHz band disabled in kernel 6.7+ despite working in <=6.6 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | AlexDeLorenzo.dev (kernel) |
| Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | pmenzel+bugzilla.kernel.org, regressions |
| Priority: | P3 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | Subsystem: | ||
| Regression: | No | Bisected commit-id: | |
| Attachments: |
Kernel 6.6 dmesg
Kernel 6.6 iw list Kernel 6.6 iw reg get Kernel 6.8 dmesg Kernel 6.8 iw list Kernel 6.8 iw reg get |
||
Created attachment 306162 [details]
Kernel 6.6 dmesg
Created attachment 306163 [details]
Kernel 6.6 iw list
Created attachment 306164 [details]
Kernel 6.6 iw reg get
Created attachment 306165 [details]
Kernel 6.8 dmesg
Created attachment 306166 [details]
Kernel 6.8 iw list
Created attachment 306167 [details]
Kernel 6.8 iw reg get
Forwarded by mail: https://lore.kernel.org/regressions/e17e5bf2-657a-4a22-a925-94db95fe8ca1@leemhuis.info/T/#u Still an issue in 6.8.7 I am sorry, that you experience an regression. This should not happen, so thank you for reporting it.
> I can provide more logs or help debug the issue if needed.
As no developer has responded yet, bisecting the issue would in my opinion really help. As you can easily reproduce the issue, it’d be great if you could find the commit introducing the regression. If you are more experienced, to avoid rebooting you could pass the WLAN device to a QEMU virtual machine, and quickly boot the Linux kernels. In either case, it should not be more than 20 regression steps, I assume.
(In reply to Paul Menzel from comment #9) > As no developer has responded yet, Maybe waiting a day or two more if the forwarding mentioned earlier leads to some results might be wise, maybe it's known by some developer that was out of office in the past few days. > bisecting the issue would in my opinion really help. FWIW, there is a guide: https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html > If you are more experienced, to avoid rebooting you could pass the WLAN > device to a QEMU virtual machine [off topic: maybe it would be wise to add instructions about that to above document, too; not sure.] (In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #10) > > > bisecting the issue would in my opinion really help. > FWIW, there is a guide: > https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html No developer responded, so this is likely needed. Knowing is latest mainline is affected (which the guide makes you check) would be a good start, as that might make some developer look into this. (In reply to Paul Menzel from comment #9) > I am sorry, that you experience an regression. This should not happen, so > thank you for reporting it. > > > I can provide more logs or help debug the issue if needed. > > As no developer has responded yet, bisecting the issue would in my opinion > really help. As you can easily reproduce the issue, it’d be great if you > could find the commit introducing the regression. If you are more > experienced, to avoid rebooting you could pass the WLAN device to a QEMU > virtual machine, and quickly boot the Linux kernels. In either case, it > should not be more than 20 regression steps, I assume. Thanks for the response, I'll look into doing this as the issue persists. (In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #11) > (In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from > comment #10) > > > > > bisecting the issue would in my opinion really help. > > FWIW, there is a guide: > > https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html > > No developer responded, so this is likely needed. Knowing is latest mainline > is affected (which the guide makes you check) would be a good start, as that > might make some developer look into this. Will do, as well. (In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #11) > (In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from > comment #10) > > > > > bisecting the issue would in my opinion really help. > > FWIW, there is a guide: > > https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html > > No developer responded, so this is likely needed. Knowing is latest mainline > is affected (which the guide makes you check) would be a good start, as that > might make some developer look into this. Compiled and booted into mainline 6.9-rc6 and this problem is still present. I'm unable to use the 6GHz radio. Built and ran a bunch of kernels, looks like the regression begins to appear in kernel 6.7.0 while it isn't present in 6.6.30. None of the developers responded, so they have no idea; in that case to get some results you most likely have to use a bisection to find the change that introduced the problem (developers then will be obliged to fix this): https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html |
On kernel 6.6.27-1-lts, running `iw list` shows that 6GHz channels are supported: Frequencies: * 5955.0 MHz [1] (12.0 dBm) (no IR) * 5975.0 MHz [5] (12.0 dBm) (no IR) * 5995.0 MHz [9] (12.0 dBm) (no IR) * 6015.0 MHz [13] (12.0 dBm) (no IR) * 6035.0 MHz [17] (12.0 dBm) (no IR) * 6055.0 MHz [21] (12.0 dBm) (no IR) * 6075.0 MHz [25] (12.0 dBm) (no IR) * 6095.0 MHz [29] (12.0 dBm) (no IR) * 6115.0 MHz [33] (12.0 dBm) (no IR) * 6135.0 MHz [37] (12.0 dBm) (no IR) * 6155.0 MHz [41] (12.0 dBm) (no IR) * 6175.0 MHz [45] (12.0 dBm) (no IR) * 6195.0 MHz [49] (12.0 dBm) (no IR) * 6215.0 MHz [53] (12.0 dBm) (no IR) * 6235.0 MHz [57] (12.0 dBm) (no IR) * 6255.0 MHz [61] (12.0 dBm) (no IR) * 6275.0 MHz [65] (12.0 dBm) (no IR) * 6295.0 MHz [69] (12.0 dBm) (no IR) * 6315.0 MHz [73] (12.0 dBm) (no IR) * 6335.0 MHz [77] (12.0 dBm) (no IR) * 6355.0 MHz [81] (12.0 dBm) (no IR) * 6375.0 MHz [85] (12.0 dBm) (no IR) * 6395.0 MHz [89] (12.0 dBm) (no IR) * 6415.0 MHz [93] (12.0 dBm) (no IR) * 6435.0 MHz [97] (12.0 dBm) (no IR) * 6455.0 MHz [101] (12.0 dBm) (no IR) * 6475.0 MHz [105] (12.0 dBm) (no IR) * 6495.0 MHz [109] (12.0 dBm) (no IR) * 6515.0 MHz [113] (12.0 dBm) (no IR) * 6535.0 MHz [117] (12.0 dBm) (no IR) * 6555.0 MHz [121] (12.0 dBm) (no IR) * 6575.0 MHz [125] (12.0 dBm) (no IR) * 6595.0 MHz [129] (12.0 dBm) (no IR) * 6615.0 MHz [133] (12.0 dBm) (no IR) * 6635.0 MHz [137] (12.0 dBm) (no IR) * 6655.0 MHz [141] (12.0 dBm) (no IR) * 6675.0 MHz [145] (12.0 dBm) (no IR) * 6695.0 MHz [149] (12.0 dBm) (no IR) * 6715.0 MHz [153] (12.0 dBm) (no IR) * 6735.0 MHz [157] (12.0 dBm) (no IR) * 6755.0 MHz [161] (12.0 dBm) (no IR) * 6775.0 MHz [165] (12.0 dBm) (no IR) * 6795.0 MHz [169] (12.0 dBm) (no IR) * 6815.0 MHz [173] (12.0 dBm) (no IR) * 6835.0 MHz [177] (12.0 dBm) (no IR) * 6855.0 MHz [181] (12.0 dBm) (no IR) * 6875.0 MHz [185] (12.0 dBm) (no IR) * 6895.0 MHz [189] (12.0 dBm) (no IR) * 6915.0 MHz [193] (12.0 dBm) (no IR) * 6935.0 MHz [197] (12.0 dBm) (no IR) * 6955.0 MHz [201] (12.0 dBm) (no IR) * 6975.0 MHz [205] (12.0 dBm) (no IR) * 6995.0 MHz [209] (12.0 dBm) (no IR) * 7015.0 MHz [213] (12.0 dBm) (no IR) * 7035.0 MHz [217] (12.0 dBm) (no IR) * 7055.0 MHz [221] (12.0 dBm) (no IR) * 7075.0 MHz [225] (12.0 dBm) (no IR) * 7095.0 MHz [229] (12.0 dBm) (no IR) * 7115.0 MHz [233] (12.0 dBm) (no IR) Similarly, discovering and connecting to 6GHz APs works fine. However, in recent kernel 6.8.5, running `iw list` shows that 6GHz channels are disabled: Frequencies: * 5955.0 MHz [1] (disabled) * 5975.0 MHz [5] (disabled) * 5995.0 MHz [9] (disabled) * 6015.0 MHz [13] (disabled) * 6035.0 MHz [17] (disabled) * 6055.0 MHz [21] (disabled) * 6075.0 MHz [25] (disabled) * 6095.0 MHz [29] (disabled) * 6115.0 MHz [33] (disabled) * 6135.0 MHz [37] (disabled) * 6155.0 MHz [41] (disabled) * 6175.0 MHz [45] (disabled) * 6195.0 MHz [49] (disabled) * 6215.0 MHz [53] (disabled) * 6235.0 MHz [57] (disabled) * 6255.0 MHz [61] (disabled) * 6275.0 MHz [65] (disabled) * 6295.0 MHz [69] (disabled) * 6315.0 MHz [73] (disabled) * 6335.0 MHz [77] (disabled) * 6355.0 MHz [81] (disabled) * 6375.0 MHz [85] (disabled) * 6395.0 MHz [89] (disabled) * 6415.0 MHz [93] (disabled) * 6435.0 MHz [97] (disabled) * 6455.0 MHz [101] (disabled) * 6475.0 MHz [105] (disabled) * 6495.0 MHz [109] (disabled) * 6515.0 MHz [113] (disabled) * 6535.0 MHz [117] (disabled) * 6555.0 MHz [121] (disabled) * 6575.0 MHz [125] (disabled) * 6595.0 MHz [129] (disabled) * 6615.0 MHz [133] (disabled) * 6635.0 MHz [137] (disabled) * 6655.0 MHz [141] (disabled) * 6675.0 MHz [145] (disabled) * 6695.0 MHz [149] (disabled) * 6715.0 MHz [153] (disabled) * 6735.0 MHz [157] (disabled) * 6755.0 MHz [161] (disabled) * 6775.0 MHz [165] (disabled) * 6795.0 MHz [169] (disabled) * 6815.0 MHz [173] (disabled) * 6835.0 MHz [177] (disabled) * 6855.0 MHz [181] (disabled) * 6875.0 MHz [185] (disabled) * 6895.0 MHz [189] (disabled) * 6915.0 MHz [193] (disabled) * 6935.0 MHz [197] (disabled) * 6955.0 MHz [201] (disabled) * 6975.0 MHz [205] (disabled) * 6995.0 MHz [209] (disabled) * 7015.0 MHz [213] (disabled) * 7035.0 MHz [217] (disabled) * 7055.0 MHz [221] (disabled) * 7075.0 MHz [225] (disabled) * 7095.0 MHz [229] (disabled) * 7115.0 MHz [233] (disabled) And scanning or connecting to 6GHz APs does not work. There's nothing in `dmesg` that differs between boots of the two kernels. On 6.8.5, 6GHz band doesn't work like it did on previous kernels. I can provide more logs or help debug the issue if needed.