Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #90103 > unrolled thread

Bug#1120822: linux-image-6.1.0-41-amd64: ath10k_pci device no longer usable

Started bySalvatore Bonaccorso <carnil@debian.org>
First post2025-11-17 15:20 +0100
Last post2025-11-18 08:40 +0100
Articles 2 — 1 participant

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1120822: linux-image-6.1.0-41-amd64: ath10k_pci device no longer usable Salvatore Bonaccorso <carnil@debian.org> - 2025-11-17 15:20 +0100
    Bug#1120822: linux-image-6.1.0-41-amd64: ath10k_pci device no longer usable Salvatore Bonaccorso <carnil@debian.org> - 2025-11-18 08:40 +0100

#90103 — Bug#1120822: linux-image-6.1.0-41-amd64: ath10k_pci device no longer usable

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-11-17 15:20 +0100
SubjectBug#1120822: linux-image-6.1.0-41-amd64: ath10k_pci device no longer usable
Message-ID<LS8ff-dEop-5@gated-at.bofh.it>
Hi Etienne,

On Sun, Nov 16, 2025 at 11:53:23PM +0100, Etienne Dysli Metref wrote:
> Package: src:linux
> Version: 6.1.158-1
> Severity: important
> 
> Dear Maintainer,
> 
> I've upgraded my kernel package from linux-image-6.1.0-40-amd64 6.1.153-1 to
> linux-image-6.1.0-41-amd64 6.1.158-1, and after a reboot, my Wifi card is no
> longer usable. hostapd cannot use it, and it doesn't appear in the output of
> `ip l`. The PCI device is still visible though (05:00.0).
> 
> Rebooting on the previous kernel version 6.1.153-1 fixes the issue, my wifi
> card is usable again.
> 
> It seems to be related to this kernel bug:
> https://bugzilla.kernel.org/show_bug.cgi?id=220671. Could you please revert
> the change that caused it, if upstream hasn't done that yet?

Yes, thanks for your report. This is the same as #1120680 (merging
both bugs). The fix is going to land in the next update for both
bookworm and for trixie, which both are yet affected.

Regards,
Salvatore

[toc] | [next] | [standalone]


#90128

FromSalvatore Bonaccorso <carnil@debian.org>
Date2025-11-18 08:40 +0100
Message-ID<LSotH-dPzI-9@gated-at.bofh.it>
In reply to#90103
Hi Etienne,

On Tue, Nov 18, 2025 at 08:16:30AM +0100, Etienne Dysli Metref wrote:
> On 17/11/2025 14.23, Salvatore Bonaccorso wrote:
> > Yes, thanks for your report. This is the same as #1120680 (merging
> > both bugs). The fix is going to land in the next update for both
> > bookworm and for trixie, which both are yet affected.
> 
> Hi Salvatore,
> 
> Thanks for your reply. :) I'm sorry for the duplicate report.

Very welcome and no worry, it is difficult to find a duplicate in the
long list of bugreports! I merged them.

> Do you mean in the next point update, like 13.3?

I meant, whatever comes first either a point release update or a
security update released via security.d.o for the kernel. For 6.12.y
it was already released with 6.12.58, for 6.1.y I need to check if it
was walready queued as well.

Regards,
Salvatore

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web