[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1109900: linux-image-6.16-rc7-amd64: Intel Wi-Fi broken on Linux 6.16-rc7 with firmware 99 causing iwlwifi microcode errors



The firmware worked normally once it was moved into the stable kernel branch, there was a bug with that specific iwlwifi firmware update that was retracted. I have not encountered this again.

On Fri, Oct 10, 2025 at 7:33 AM Salvatore Bonaccorso <carnil@debian.org> wrote:
Control: tags -1 + moreinfo

Hi Jennifer,

On Fri, Jul 25, 2025 at 05:34:28PM -0700, Jennifer Riley wrote:
> Package: src:linux
> Version: 6.16~rc7-1~exp1
> Severity: important
> X-Debbugs-Cc: klipo89@gmail.com
>
> Dear Maintainer,
>
> What led up to the situation?
> Upgraded from Linux 6.15 to 6.16-rc7 kernel.
> iwlwifi 0000:08:00.0: microcode SW error detected. Restarting 0x2000000.
> iwlwifi 0000:08:00.0: Failed to start RT ucode: -110
>
> What exactly did you do (or not do) that was effective (or ineffective)?
> Booted into Linux 6.16-rc7, where iwlwifi loads firmware version 99 for the
> Intel BE200 device. This causes microcode software errors and prevents the Wi-
> Fi interface from initializing. Reverting to Linux 6.15 loads firmware version
> 98, which initializes the device properly and Wi-Fi works as expected. Manually
> copying firmware version 98 over the 99 file forces the driver to load the
> older, working firmware on 6.16-rc7, temporarily restoring Wi-Fi functionality.
> This indicates firmware 99 is likely buggy.
>
> Full firmware 99 dmesg 'iwl|firmware' log here
> https://pastebin.com/raw/9TBdP50w
>
> dmesg 'iwl|firmware' log with 98 override here
> https://pastebin.com/raw/dDQA0Csd
>
> What was the outcome of this action?
> Wi-Fi broken on 6.16-rc7; works fine on 6.15.
>
> What outcome did you expect instead?
> Wi-Fi should work on 6.16-rc7 as it did on 6.15.

While not identical, I suspect the issue might be releated to same
issues as for #1115268.

Could you please explicitly test 6.16.10-1 now and report back if the
issue is gone?

Regards,
Salvatore

Reply to: