public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Bernhard Bitsch <bbitsch@ipfire.org>
To: development@lists.ipfire.org
Subject: Errors for WLAN card since CU189
Date: Wed, 16 Oct 2024 17:02:47 +0200	[thread overview]
Message-ID: <64d60b6f-f36c-477c-99f6-73c4cb3b0bab@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2844 bytes --]

Hi,

since some time I noticed strange messages according to my WLAN card.
With CU189 these are very frequently.

An extract from now:

...
Oct 16 16:09:17 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
increase tx pending count: -16, dropping
Oct 16 16:10:39 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
increase tx pending count: -16, dropping
Oct 16 16:11:20 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:13:45 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
increase tx pending count: -16, dropping
Oct 16 16:18:47 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:18:52 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:19:13 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:19:28 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:19:33 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:19:38 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:19:43 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:19:48 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:19:54 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:19:59 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:20:04 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:20:09 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:20:24 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:20:40 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:21:10 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:21:16 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:21:41 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:21:46 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
Oct 16 16:21:51 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to 
flush transmit queue (skip 0 ar-state 1): 0
............

Regards,
Bernhard

BTW: I'm missing the status part of the hostapd WUI page.

             reply	other threads:[~2024-10-16 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16 15:02 Bernhard Bitsch [this message]
2024-10-16 15:05 ` Michael Tremer
2024-10-16 16:04   ` Bernhard Bitsch
2024-10-16 16:20   ` Bernhard Bitsch
2024-10-16 19:04     ` Bernhard Bitsch
2024-10-17  9:33       ` Michael Tremer
2024-10-17  9:43         ` Bernhard Bitsch
     [not found] <920bf76e-5baf-4cb5-9a47-26b69a801c81@ipfire.org>
2024-10-16 16:03 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=64d60b6f-f36c-477c-99f6-73c4cb3b0bab@ipfire.org \
    --to=bbitsch@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox