Bug 219856
| Summary: | iwlwifi: 8265: UMAC ASSERT 0x67 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Maxim (gudvinr+kernelorg) |
| Component: | network-wireless-intel | Assignee: | Default virtual assignee for network-wireless-intel (drivers_network-wireless-intel) |
| Status: | NEEDINFO --- | ||
| Severity: | high | CC: | emmanuel.grumbach, kernel |
| Priority: | P3 | ||
| Hardware: | Intel | ||
| OS: | Linux | ||
| See Also: |
https://bugzilla.kernel.org/show_bug.cgi?id=218946 https://bugzilla.kernel.org/show_bug.cgi?id=215635 |
||
| Kernel Version: | Subsystem: | ||
| Regression: | No | Bisected commit-id: | |
| Attachments: |
dmesg
latest firmware new error f82a4177 ucode dmesg |
||
|
Description
Maxim
2025-03-11 13:02:09 UTC
Created attachment 307834 [details]
latest firmware
Hi Maxim,
Can you please try the firmware attached?
Just copy it to /lib/firmware.
Your problem seems to be a firmware problem, and there were a few changes that are not included in your version.
I can't tell that your issues will be fixed, but since you reproduce easily, it's worth trying.
Thanks!
Created attachment 307839 [details] new error (In reply to Emmanuel Grumbach from comment #1) > Can you please try the firmware attached? > Just copy it to /lib/firmware. Can't say yet that it fixes the issue but it now fails at the start, which wasn't the case for older firmware. See an attachment. Wifi still works after the fail but I don't think it's the intended behaviour. It is different failure though. Firmware does change: [ 20.033550] iwlwifi 0000:06:00.0: loaded firmware version 36.f82a4177.0 8265-36.ucode op_mode iwlmvm Old one: [ 42.279192] iwlwifi 0000:06:00.0: loaded firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm Very strange... Can you tell what happened on October 25th? Firmware update? Kernel update? New router? Created attachment 307841 [details] f82a4177 ucode dmesg (In reply to Emmanuel Grumbach from comment #1) > Created attachment 307834 [details] > latest firmware Doesn't seem to be helping. New error log from dmesg in attachment. > Can you tell what happened on October 25th? Not sure if it has any meaning. Could be just journald not having logs any earlier. But at 24th there was a kernel upgrade: linux (6.11.4.arch2-1 -> 6.11.5.arch1-1) linux-lts (6.6.57-1 -> 6.6.58-1) And firmware upgrade on 18th: linux-firmware (20240909.552ed9b8-1 -> 20241017.22a6c7dc-1) Router is the same, but there was a relatively big fw upgrade month before: https://mikrotik.com/download/changelogs#c-stable-v7_16 Can't say for sure if I updated the same day or a month before so it could be the reason too. I talked to the firmware team and they think this problem is caused by a frame that we started to receive. This device is fairly old but I can try to see if we can get some attention from them. We'd need a firmware dump: https://wireless.docs.kernel.org/en/latest/en/users/drivers/iwlwifi/debugging.html#firmware-debugging Note the privacy implications. You can encrypt the data if you want. I've installed debug firmware (36.9f0a2d68.0) from this page. When there's enough info I will report. Also FYI intel cards, even newer ax200/ax201 do seem to be flacky with routeros: https://forum.mikrotik.com/viewtopic.php?p=1129079 https://forum.mikrotik.com/viewtopic.php?p=1117936 I am not implying that my issue is the same though. But thought it is worth to note. (In reply to Emmanuel Grumbach from comment #5) > Note the privacy implications. You can encrypt the data if you want. https://www.dropbox.com/scl/fi/hwchj1xfwnu7ofd39qpme/iwl-fw-error.zip.asc?rlkey=mygycl0ucnsgon094zqa49q3q&st=ibc7twvc&dl=0 Here's encrypted dumps. |