-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APB: Check your mt7612u and mt7610u based adapters with Linux kernel 6.1 rc* #142
Comments
Note: This could be something else going on in this specific test system so I am asking others that have the ability to upgrade to kernel 6.1 to test before I spend time gathering info to file a bug report. |
I have that problem too, but i was thinking was another patch i was tested. Can this be related some how? |
I don't know but I don't think so. The problem I am seeing is only with adapters based on the mt7612u and mt7610u chipsets. My adapter with a mt7921au chipset is working better than ever on the same kernel 6.1. In fact, I have several adapters with various chipsets and I am only seeing this lock up problem with mt7612u and mt7610u chipset based adapters on kernel 6.1. Hopefully we have some other folks roll in with additional information so we can see if this is widespread and speciifc to the chipset and kernel we are talking about. There could have been a patch that is not working well with the mt761Xu chipsets. |
This was before I associated:
That is the Alfa. I associated and the system locked up within seconds. |
Exactly what I am seeing. Within seconds of association, hard lock, pull the plug. The only combination I am seeing this with is kernel 6.1 and mt761Xu chipsets. We really don't want 6.1 (LTS) released with this issue. @bjlockie , do you have time to post a [bug - mt7612u] to linux-wireless? You can reference this thread. |
More testing: This time with a mt7610u chipset based adapter (Alfa ACHM to be exact). With kernel 6.1, I am seeing the same problem-- about 3-4 seconds after association with an AP, hard lock, plug the plug. So this issue appears to not just be with the mt7612u chipset. It appears with both the mt7612u and mt7610u chipsets. |
Thanks for posting the bug. I guess with recent guidance it should have been [BUG] wifi: MT761Xu. It sure looks to me at this point that some patch for 6.1 is causing a problem. |
This morning I saw the following patch on linux-wireless. I see it is cc'ed to you but others might be interested. We really need this problem fixed before 6.1 is released.
|
Thanks, I missed that because I delete all the patches on that list. :-) |
I don't think it will be in RC4. There are follow on messages now where another guy is questioning whether mac80211 is the right place to fix the problem. I'm reading between the lines here but I get the feeling that a mac80211 patch has broken a few drivers and Lorenzo is patching mac80211 as a short term solution because the real fix may require firmware patches which come from the company. I suspect there are more than MT76 drivers that are broken. In fact, if I have time this week, I'm going to test everything I have here which is a significant job. I don't like hard lock, pull the plug situations. |
I just tested with 6.1 rc5 and hard lock, pull the plug. This is a nasty bug. I haven't seen a V2 of the initial patch come through on linux-wireless. No idea what the status is. Nick |
Is the patch definitely in 6.1rc5?
|
No, the patch is not in rc5. Not sure what the status is. |
So i'm using a MT7610U and updated to 6.1.1 in Arch Linux and it's a complete lockup a few seconds after connecting as other people have said, i'll use the LTS kernel (5.15) in the meanwhile but this is probably going to get a lot of people that use distros with newer kernels. |
I had hoped it would be fixed by now.
I'm surprised the primary developer hasn't seen it, it is easy to reproduce.
Dec. 23, 2022 12:54:53 randomcodepanda ***@***.***>:
… So i'm using a MT7610U and updated to 6.1.1 in Arch Linux and it's a complete lockup a few seconds after connecting as other people have said, i'll use the LTS kernel (5.15) in the meanwhile but this is probably going to get a lot of people that use distros with newer kernels.
—
Reply to this email directly, view it on GitHub[#142 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AACKGAOVCCEUZ5AYXA6CCQLWOXRORANCNFSM6AAAAAARSWFNXU].
You are receiving this because you were mentioned.[Tracking image][https://github.com/notifications/beacon/AACKGAKEL5EKDEU53FY4CXTWOXRORA5CNFSM6AAAAAARSWFNXWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSRJ5GGU.gif]
|
Me too. I'm reopening this issue so folks can see it. Are you able to grab your old report to linux-wireless and add the above report to it while pointing out that this is a show stopper? |
I think the proper title for a report like something like this would be: [bug report} wifi: mt76: mt7612u/mt7610u 6.1.x - hard locking systems |
If you are busy, I can send the report. Let me know. |
I have some time this afternoon so I'll go ahead and report this. |
I'm slow, thanks for doing that.
I see there is a kernel patch.
Does the patch only get in a released kernel only after someone verifies the patch fixes the problem?
|
No problem. It is a time of year when most of us are busy to one degree or another.
I've been looking at the patch. The patch is not to the mt76 driver. It is a patch to mac80211 which affects almost all wireless so it has to be approved. I'm traveling so it is not a good time for me to test the patch. |
The proposed patch has to be approved by Johannes Berg as it is not a patch to the mt76 driver. It is a patch to the mac80211 driver which is a system wide wifi driver so care has to be taken. The patch was provided by a Mediatek dev. I can't say how much time this will take but the devs are very aware of it. Nick |
I had time to apply the patch that needed to be tested. It worked. I could not see any side effects so we'll just have to see. I'll recommend to stay with kernel 6.0 or earlier until such time as that patch works its way into 6.1 and later. For what its worth. That patch is not to the Mediatek driver. That patch is to the mac80211 driver which is part of the wifi supporting stack. The patch was written by a Mediatek dev. Nick |
Why did the bug only affect mediatek devises?
|
It may not just affect Mediatek devices. I looked at the patch and it is not a trivial patch. We need more testing. I'm wondering if it would help if I posted a guide that would give specific instructions how to test. |
If mediatek devices are the only ones that cause a crash then wouldn't the developers know?
Can this be tested in a VM?
|
Depends on what the devs are working on and whether what caused the problem is something that came from them. This problem does not appear to have been caused by a patch from a Mediatek dev.
It probably can but I'm the wrong person to answer as I run 100% bare metal here. |
V5 of the patch was submitted today. Not sure when it will be accepted: [PATCH v5] wifi: mac80211: fix initialization of rx->link and rx->link_sta
|
Updated today to 6.1.2 and it's still freezing, hopefully it makes it on the next release. |
It sure would be good for the patch to go into 6.1 and 6.2 as soon as possible but we need to respect that this is going into a part if the kernel that is heavily used by many drivers so a mistake would not be good. |
Could this apply to mt7921 as well? I have a recently acquired wifi adapter that I can't get to work. I'm trying to use it in ap mode, hostapd runs fine but when another computer tries to connect the AP freezes. |
I have not seen this problem with the mt7921. Recommend you start a new issue and describe what you are seeing. A new issue with a good title will attract users that may be able to help. |
Hello, I am using Arch Linux 6.1.4 with a new Alfa AWUS036ACM and am experiencing a crash within a few seconds of logging in. What can I do until the issue is fixed? Is there any way that I can downgrade to 6.0? |
Hi @sha5672
Yes, this is an ugly issue. Programmers call it a null pointer dereference. On my systems, it is pull the plug time...and remove the adapter before rebooting. The problem is happening with the 7612u and 7610u chipsets. This started with kenel 6.1 by a patch from a Intel dev. A patch I will link below has been submitted by a Mediatel dev but the patch is not to a Mediatek driver, it is to mac80211 which is a Linux Wireless system stack driver and that is delaying the merging to mainline as a gatekeeper has to be satisfied it it not going to cause system wide problems. In looking at the patch and the reasons behind it, I tend to agree with what is being done. It would have helped if it had not happened during the holiday season. Hopefully the patch will be merged soon.
Downgrade to any kernel prior to 6.1.
I'm sure there is but my expertise is with Debian/Ubuntu based systems so you don't want me to help you downgrade your kernel. You probably should go to the appropriate Arch forum and ask how to downgrade. Below is a link to the patch: https://lore.kernel.org/all/20221230200747.19040-1-nbd@nbd.name/ I have tested it on 6.1 and 6.2-rc2 and it works. I hope it is merged soon as this could get ugly as more distros upgrade to 6.1. Nick |
If you are not on some bleeding edge hardware that needs newer kernels the best bet for stability in Arch right now would be to install the linux-lts package and update your bootloader so you can boot with linux-lts which is on 5.15. It is possible to downgrade to 6.0 if you still have the old package on your cache or if you download it from the arch archive and install it with pacman -U, but then you would have to add the linux package to the ignorepkg line in pacman.conf so it doesn't get upgraded on a regular upgrade. It's easier to just use the linux-lts kernel if that is compatible with the rest of your hardware. |
This is now fixed in Debian kernel 6.1.8-1. From the changelog: |
I can confirm that linux-6.1.8 fixes it. |
This reason for this message is that I am seeing a system lockup when trying to use mt7612u based adapters. Yes, device drivers can do that. I was seeing it in kernel 6.1 rc1 and am still seeing it in 6.1 rc3. Would like confirmation. This only started with kernel 6.1.
Thanks,
Nick
The text was updated successfully, but these errors were encountered: