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

Bug#1031391: /lib/modules/6.0.0-12parrot1-amd64/kernel/drivers/net/wireless/ath/ath10k/ath10k_core.ko: Firmware crashed



Control: tags -1 + moreinfo

On Thu, Feb 16, 2023 at 12:38:03PM +0100, Marek Küthe wrote:
> Package: src:linux
> Version: 6.0.12-1parrot1
> Severity: important
> File: /lib/modules/6.0.0-12parrot1-amd64/kernel/drivers/net/wireless/ath/ath10k/ath10k_core.ko
> X-Debbugs-Cc: m.k@mk16.de
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> I have no idea how this situation comes about. 
> * What exactly did you do (or not do) that was effective (or
>      ineffective)
>    * What was the outcome of this action?
>    * What outcome did you expect instead?
> 
> The firmware crashes (judging by the log). After that, the computer becomes enormously slow, the mouse does not move for a few seconds. After that it works again. After that, Network Manager says "disconnect". When I restart the Network Manager, "Device not available" appears.
> 
> -- Package-specific info:
> ** Version:
> Linux version 6.0.0-12parrot1-amd64 (team@parrotsec.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Parrot) 2.37.90.20220130) #1 SMP PREEMPT_DYNAMIC Debian 6.0.12-1parrot1 (2023-01-12)
> 
> ** Command line:
> BOOT_IMAGE=/@/boot/vmlinuz-6.0.0-12parrot1-amd64 root=UUID=4c28bef4-77fd-4464-9cd5-5b0bcc104742 ro rootflags=subvol=@ quiet cryptdevice=UUID=fed0c2db-58a8-4f7b-9ba2-9321b4f7a550:luks-fed0c2db-58a8-4f7b-9ba2-9321b4f7a550 root=/dev/mapper/luks-fed0c2db-58a8-4f7b-9ba2-9321b4f7a550 splash resume=/dev/mapper/luks-5090abc4-1254-4f9f-8ae8-2f7e0cd2bd55
> 
> ** Tainted: PWO (4609)
>  * proprietary module was loaded
>  * kernel issued warning
>  * externally-built ("out-of-tree") module was loaded

While this might not be the issue, two observation: does this happens
with the Debian kernel? Otherwise report it please to the derivative.
There are proprietary out of tree modules loaded, does that happens
as well without? 

In any case can you please if you can reproduce this with plain Debian
unstable (upate as well the firmware packages to their current versions)?

Regards,
Salvatore


Reply to: