Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Jennifer Riley Newsgroups: linux.debian.bugs.dist,linux.debian.kernel Subject: Bug#1109900: linux-image-6.16-rc7-amd64: Intel Wi-Fi broken on Linux 6.16-rc7 with firmware 99 causing iwlwifi microcode errors Date: Fri, 10 Oct 2025 19:40:02 +0200 Message-ID: References: X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Fri Oct 10 17:35:08 2025 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -1.245 Reply-To: Jennifer Riley , 1109900@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: debian-kernel@lists.debian.org X-Debian-Pr-Message: followup 1109900 X-Debian-Pr-Package: src:linux X-Debian-Pr-Keywords: moreinfo X-Debian-Pr-Source: linux X-Gm-Message-State: AOJu0Yxtz6RkkFZ6XGjiKk/Z3cM4OJ5bETpxxmLz0QC/ewkJFP6cqZ1i ONaSgVzcQXuJRZ8ZRFoBqQTfsnFUTiErv2eZ+27+MjsrRFI36M/ocgPg8OvUWVwuJ4pVZBZO8OJ HJ8NXq7axQjlX6lBj9NUXKWNDXBxT6yY= X-Gm-Gg: ASbGnctPZB263x5n31yUq/RypzjunvmF5xlRPLQFWd0yGcVbsPxfWdCYsXPV6j0DqUe gWZHJFBdmebn1+WLnKRroJQgMV2gjUNh+HgQYtukdmhawY3Y8uPtoUKC7bkwbrplASB2IivyQSX Cx69BDNBuTpFY23poSB2VSJPlCUyd0B4TSFjmXRzVfSVbbx3E4Z8m5zjAS7IUMZdYf98ZIk7dPn i4Jtr54URdNDyA4Enrd0iK54StqDKsGRui4WSuAklvKZ17FntiLtFE9dJ59IVHosginWSZUqzk5 BrqtISua3hCX X-Google-SMTP-Source: AGHT+IEmfh4lKdSFBvrdhI+iHJZpZj8KMgjztIfe44AM3QTsNlmFlfhMmgu7Eehg0psiq0SDQh/ZvNyzVjL7hGb9uBk= X-Received: by 2002:a53:ba8b:0:b0:636:875:62b6 with SMTP id 956f58d0204a3-63ccb86051dmr9029122d50.18.1760117628890; Fri, 10 Oct 2025 10:33:48 -0700 (PDT) MIME-Version: 1.0 X-Gm-Features: AS18NWBHoOltJd7kXR7CsNq6MHlb2rFKbtvHBX7JoGumzWZB1_nSXFsTyon5Crc Content-Type: multipart/alternative; boundary="0000000000000873110640d15279" X-Debian-Message: from BTS X-Mailing-List: archive/latest/1930526 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 136 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: 1109900@bugs.debian.org X-Original-Date: Fri, 10 Oct 2025 10:33:38 -0700 X-Original-Message-ID: X-Original-References: <175349006887.5677.15288976639472033240.reportbug@iCube> <175349006887.5677.15288976639472033240.reportbug@iCube> Xref: csiph.com linux.debian.bugs.dist:1265543 linux.debian.kernel:89537 --0000000000000873110640d15279 Content-Type: text/plain; charset="UTF-8" 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 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 > --0000000000000873110640d15279 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The firmware worked normally once it was moved into the s= table kernel branch, there was a bug with that specific iwlwifi firmware up= date that was retracted. I have not encountered this again.

<= div class=3D"gmail_quote">
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: k= lipo89@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 0x200000= 0.
> 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 fo= r 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 funct= ionality.
> 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
--0000000000000873110640d15279--