Hello Tim and Juerg, thank you for your responses! I am attaching the kernel
logs from boot that show
the two different problems ("Microcode SW error" and asm_exc_invalid_op
followed by oom). I extracted them
with: journalctl --facility=kern.
We used the HWE kernel as-is at the time these logs were recorded.
The new setup with the out-of-tree backport of iwlwifi has now completed the
second 24h stress test
without error, which makes use pretty confident in it. I provided the git
repositories and commit hashes
that we currently test in the OP.
Previously, we struggled to produce even one successful run of these tests.
I tried to build the backport-iwlwifi-dkms from proposed as it was newer than
the one in jammy-updates
but it didn't seem to build against the HWE kernel ("unknown symbol" messages
when I tried to insmod).
If it helps you, I could try to build the backport-iwlwifi-dkms from
jammy-updates and test that, but
it seems to be from June '24 and there have been a lot of changes to the
backport since then.
** Attachment added: "kern.zip"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.8/+bug/2100280/+attachment/5861019/+files/kern.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100280
Title:
invalid opcode and "Microcode SW error detected" in iwlwifi during
extended WiFi stress test may trigger oom
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2100280/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
