Describe the bug
The mt7921 driver in 6.12 has a null pointer dereference bug which is affecting my setup (wifi antenna is totally unusable as an AP, it crashes on first connection and requires reboot).
The bug has already been fixed in the stable 6.12 branch: gregkh/linux@adc3fd2
Any chance the stable 6.12.y branch can be merged into the raspberrypi tree? Last merge seems to have been 6.12.22, and fixing this would require 6.12.23+. I need to move from 6.6 to 6.12 for other reasons - I can rebuilt it myself, but wondering whether I should wait for that commit to make it to the raspberrypi tree. Another alternative would be to use 6.12.x with x<13 as the regression was introduced with 6.12.13 but that's also slightly inconvenient
Thanks!
Steps to reproduce the behaviour
Expose AP with NetworkManager with default settings, then connect a device to it.
Device (s)
Raspberry Pi 5
System
I don't have this handy as I reverted back to 6.6. I assume you don't need the info since the bug has already been confirmed and fixed upstream. But if you still want me to repro for any reason I'd be happy to.
Logs
No response
Additional context
No response
Describe the bug
The mt7921 driver in 6.12 has a null pointer dereference bug which is affecting my setup (wifi antenna is totally unusable as an AP, it crashes on first connection and requires reboot).
The bug has already been fixed in the stable 6.12 branch: gregkh/linux@adc3fd2
Any chance the stable 6.12.y branch can be merged into the raspberrypi tree? Last merge seems to have been 6.12.22, and fixing this would require 6.12.23+. I need to move from 6.6 to 6.12 for other reasons - I can rebuilt it myself, but wondering whether I should wait for that commit to make it to the raspberrypi tree. Another alternative would be to use 6.12.x with x<13 as the regression was introduced with 6.12.13 but that's also slightly inconvenient
Thanks!
Steps to reproduce the behaviour
Expose AP with NetworkManager with default settings, then connect a device to it.
Device (s)
Raspberry Pi 5
System
I don't have this handy as I reverted back to 6.6. I assume you don't need the info since the bug has already been confirmed and fixed upstream. But if you still want me to repro for any reason I'd be happy to.
Logs
No response
Additional context
No response