* Errors for WLAN card since CU189
@ 2024-10-16 15:02 Bernhard Bitsch
2024-10-16 15:05 ` Michael Tremer
0 siblings, 1 reply; 8+ messages in thread
From: Bernhard Bitsch @ 2024-10-16 15:02 UTC (permalink / raw)
To: development
[-- 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.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors for WLAN card since CU189
2024-10-16 15:02 Errors for WLAN card since CU189 Bernhard Bitsch
@ 2024-10-16 15:05 ` Michael Tremer
2024-10-16 16:04 ` Bernhard Bitsch
2024-10-16 16:20 ` Bernhard Bitsch
0 siblings, 2 replies; 8+ messages in thread
From: Michael Tremer @ 2024-10-16 15:05 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 3701 bytes --]
I believe this is a known bug in the driver. You can fix this by turning the IRQ mode to legacy. It is a setting of the module:
[root(a)fw01 ~]# modinfo ath10k_pci
filename: /lib/modules/6.6.47-ipfire/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko.xz
firmware: ath10k/QCA9377/hw1.0/board.bin
firmware: ath10k/QCA9377/hw1.0/firmware-5.bin
firmware: ath10k/QCA9377/hw1.0/firmware-6.bin
firmware: ath10k/QCA6174/hw3.0/board-2.bin
firmware: ath10k/QCA6174/hw3.0/board.bin
…
parm: irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint)
…
This is most likely because of updating the firmware for your card.
-Michael
> On 16 Oct 2024, at 16:02, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>
> 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.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors for WLAN card since CU189
2024-10-16 15:05 ` Michael Tremer
@ 2024-10-16 16:04 ` Bernhard Bitsch
2024-10-16 16:20 ` Bernhard Bitsch
1 sibling, 0 replies; 8+ messages in thread
From: Bernhard Bitsch @ 2024-10-16 16:04 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 3964 bytes --]
I also cannot set the channel. Only automatic channel select available.
/etc/init.d/hostapd restart functions at the second restart only.
Am 16.10.2024 um 17:05 schrieb Michael Tremer:
> I believe this is a known bug in the driver. You can fix this by turning the IRQ mode to legacy. It is a setting of the module:
>
> [root(a)fw01 ~]# modinfo ath10k_pci
> filename: /lib/modules/6.6.47-ipfire/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko.xz
> firmware: ath10k/QCA9377/hw1.0/board.bin
> firmware: ath10k/QCA9377/hw1.0/firmware-5.bin
> firmware: ath10k/QCA9377/hw1.0/firmware-6.bin
> firmware: ath10k/QCA6174/hw3.0/board-2.bin
> firmware: ath10k/QCA6174/hw3.0/board.bin
> …
> parm: irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint)
> …
>
> This is most likely because of updating the firmware for your card.
>
> -Michael
>
>> On 16 Oct 2024, at 16:02, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>>
>> 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.
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors for WLAN card since CU189
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
1 sibling, 1 reply; 8+ messages in thread
From: Bernhard Bitsch @ 2024-10-16 16:20 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 4280 bytes --]
I also cannot set the channel. Only automatic channel select available.
/etc/init.d/hostapd restart functions at the second restart only.
Messages:
/etc/init.d/hostapd restart
Stopping hostapd... [
Starting hostapd...
blue0: interface state UNINITIALIZED->COUNTRY_UPDATE
ACS: Automatic channel selection started, this may take a bit
blue0: interface state COUNTRY_UPDATE->ACS
blue0: ACS-STARTED
Am 16.10.2024 um 17:05 schrieb Michael Tremer:
> I believe this is a known bug in the driver. You can fix this by turning the IRQ mode to legacy. It is a setting of the module:
>
> [root(a)fw01 ~]# modinfo ath10k_pci
> filename: /lib/modules/6.6.47-ipfire/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko.xz
> firmware: ath10k/QCA9377/hw1.0/board.bin
> firmware: ath10k/QCA9377/hw1.0/firmware-5.bin
> firmware: ath10k/QCA9377/hw1.0/firmware-6.bin
> firmware: ath10k/QCA6174/hw3.0/board-2.bin
> firmware: ath10k/QCA6174/hw3.0/board.bin
> …
> parm: irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint)
> …
>
> This is most likely because of updating the firmware for your card.
>
> -Michael
>
>> On 16 Oct 2024, at 16:02, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>>
>> 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.
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors for WLAN card since CU189
2024-10-16 16:20 ` Bernhard Bitsch
@ 2024-10-16 19:04 ` Bernhard Bitsch
2024-10-17 9:33 ` Michael Tremer
0 siblings, 1 reply; 8+ messages in thread
From: Bernhard Bitsch @ 2024-10-16 19:04 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 5057 bytes --]
Some light at the end of the tunnel. ;)
wlanap.cgi tries to set $INTF from $cgiparams{'INTERFACE'} in line 64.
But $cgiparams{'INTERFACE'} is not defined or empty.
Setting $INTF to "blue0" brings the channels and the status.
I think there went something wrong with the modification to new look.
The problem with the kernel errors is solved by the interrupt setting.
Regards,
Bernhard
Am 16.10.2024 um 18:20 schrieb Bernhard Bitsch:
> I also cannot set the channel. Only automatic channel select available.
> /etc/init.d/hostapd restart functions at the second restart only.
>
> Messages:
> /etc/init.d/hostapd restart
> Stopping hostapd... [
> Starting hostapd...
> blue0: interface state UNINITIALIZED->COUNTRY_UPDATE
> ACS: Automatic channel selection started, this may take a bit
> blue0: interface state COUNTRY_UPDATE->ACS
> blue0: ACS-STARTED
>
> Am 16.10.2024 um 17:05 schrieb Michael Tremer:
>> I believe this is a known bug in the driver. You can fix this by
>> turning the IRQ mode to legacy. It is a setting of the module:
>>
>> [root(a)fw01 ~]# modinfo ath10k_pci
>> filename: /lib/modules/6.6.47-ipfire/kernel/drivers/net/
>> wireless/ath/ath10k/ath10k_pci.ko.xz
>> firmware: ath10k/QCA9377/hw1.0/board.bin
>> firmware: ath10k/QCA9377/hw1.0/firmware-5.bin
>> firmware: ath10k/QCA9377/hw1.0/firmware-6.bin
>> firmware: ath10k/QCA6174/hw3.0/board-2.bin
>> firmware: ath10k/QCA6174/hw3.0/board.bin
>> …
>> parm: irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint)
>> …
>>
>> This is most likely because of updating the firmware for your card.
>>
>> -Michael
>>
>>> On 16 Oct 2024, at 16:02, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>>>
>>> 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.
>>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors for WLAN card since CU189
2024-10-16 19:04 ` Bernhard Bitsch
@ 2024-10-17 9:33 ` Michael Tremer
2024-10-17 9:43 ` Bernhard Bitsch
0 siblings, 1 reply; 8+ messages in thread
From: Michael Tremer @ 2024-10-17 9:33 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 5137 bytes --]
Could you elaborate a little bit more on this?
We might want to fix this in c189 before other people walk into the same problem…
-Michael
> On 16 Oct 2024, at 20:04, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>
> Some light at the end of the tunnel. ;)
>
> wlanap.cgi tries to set $INTF from $cgiparams{'INTERFACE'} in line 64.
> But $cgiparams{'INTERFACE'} is not defined or empty.
> Setting $INTF to "blue0" brings the channels and the status.
> I think there went something wrong with the modification to new look.
>
> The problem with the kernel errors is solved by the interrupt setting.
>
> Regards,
> Bernhard
>
> Am 16.10.2024 um 18:20 schrieb Bernhard Bitsch:
>> I also cannot set the channel. Only automatic channel select available.
>> /etc/init.d/hostapd restart functions at the second restart only.
>> Messages:
>> /etc/init.d/hostapd restart
>> Stopping hostapd... [
>> Starting hostapd...
>> blue0: interface state UNINITIALIZED->COUNTRY_UPDATE
>> ACS: Automatic channel selection started, this may take a bit
>> blue0: interface state COUNTRY_UPDATE->ACS
>> blue0: ACS-STARTED
>> Am 16.10.2024 um 17:05 schrieb Michael Tremer:
>>> I believe this is a known bug in the driver. You can fix this by turning the IRQ mode to legacy. It is a setting of the module:
>>>
>>> [root(a)fw01 ~]# modinfo ath10k_pci
>>> filename: /lib/modules/6.6.47-ipfire/kernel/drivers/net/ wireless/ath/ath10k/ath10k_pci.ko.xz
>>> firmware: ath10k/QCA9377/hw1.0/board.bin
>>> firmware: ath10k/QCA9377/hw1.0/firmware-5.bin
>>> firmware: ath10k/QCA9377/hw1.0/firmware-6.bin
>>> firmware: ath10k/QCA6174/hw3.0/board-2.bin
>>> firmware: ath10k/QCA6174/hw3.0/board.bin
>>> …
>>> parm: irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint)
>>> …
>>>
>>> This is most likely because of updating the firmware for your card.
>>>
>>> -Michael
>>>
>>>> On 16 Oct 2024, at 16:02, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>>>>
>>>> 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.
>>>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors for WLAN card since CU189
2024-10-17 9:33 ` Michael Tremer
@ 2024-10-17 9:43 ` Bernhard Bitsch
0 siblings, 0 replies; 8+ messages in thread
From: Bernhard Bitsch @ 2024-10-17 9:43 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 5445 bytes --]
I'll try as good as my influenca allows;)
I think, the problems came up with the change from 'select interface' in
hostapd WUI to 'hostapd is on blue'.
BR,
Bernhard
Am 17.10.2024 um 11:33 schrieb Michael Tremer:
> Could you elaborate a little bit more on this?
>
> We might want to fix this in c189 before other people walk into the same problem…
>
> -Michael
>
>> On 16 Oct 2024, at 20:04, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>>
>> Some light at the end of the tunnel. ;)
>>
>> wlanap.cgi tries to set $INTF from $cgiparams{'INTERFACE'} in line 64.
>> But $cgiparams{'INTERFACE'} is not defined or empty.
>> Setting $INTF to "blue0" brings the channels and the status.
>> I think there went something wrong with the modification to new look.
>>
>> The problem with the kernel errors is solved by the interrupt setting.
>>
>> Regards,
>> Bernhard
>>
>> Am 16.10.2024 um 18:20 schrieb Bernhard Bitsch:
>>> I also cannot set the channel. Only automatic channel select available.
>>> /etc/init.d/hostapd restart functions at the second restart only.
>>> Messages:
>>> /etc/init.d/hostapd restart
>>> Stopping hostapd... [
>>> Starting hostapd...
>>> blue0: interface state UNINITIALIZED->COUNTRY_UPDATE
>>> ACS: Automatic channel selection started, this may take a bit
>>> blue0: interface state COUNTRY_UPDATE->ACS
>>> blue0: ACS-STARTED
>>> Am 16.10.2024 um 17:05 schrieb Michael Tremer:
>>>> I believe this is a known bug in the driver. You can fix this by turning the IRQ mode to legacy. It is a setting of the module:
>>>>
>>>> [root(a)fw01 ~]# modinfo ath10k_pci
>>>> filename: /lib/modules/6.6.47-ipfire/kernel/drivers/net/ wireless/ath/ath10k/ath10k_pci.ko.xz
>>>> firmware: ath10k/QCA9377/hw1.0/board.bin
>>>> firmware: ath10k/QCA9377/hw1.0/firmware-5.bin
>>>> firmware: ath10k/QCA9377/hw1.0/firmware-6.bin
>>>> firmware: ath10k/QCA6174/hw3.0/board-2.bin
>>>> firmware: ath10k/QCA6174/hw3.0/board.bin
>>>> …
>>>> parm: irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint)
>>>> …
>>>>
>>>> This is most likely because of updating the firmware for your card.
>>>>
>>>> -Michael
>>>>
>>>>> On 16 Oct 2024, at 16:02, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>>>>>
>>>>> 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.
>>>>
>>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Errors for WLAN card since CU189
[not found] <920bf76e-5baf-4cb5-9a47-26b69a801c81@ipfire.org>
@ 2024-10-16 16:03 ` Michael Tremer
0 siblings, 0 replies; 8+ messages in thread
From: Michael Tremer @ 2024-10-16 16:03 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 4200 bytes --]
You create a new file in /etc/modprobe.d. Let’s call it ath10_pci.conf.
In there you write this line:
options ath10k_pci irq_mode=1
Then save and reboot.
-Michael
P.S. Please make sure you copy the list.
> On 16 Oct 2024, at 16:53, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>
> How can I set that?
>
>
> Am 16.10.2024 um 17:05 schrieb Michael Tremer:
>> I believe this is a known bug in the driver. You can fix this by turning the IRQ mode to legacy. It is a setting of the module:
>> [root(a)fw01 ~]# modinfo ath10k_pci
>> filename: /lib/modules/6.6.47-ipfire/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko.xz
>> firmware: ath10k/QCA9377/hw1.0/board.bin
>> firmware: ath10k/QCA9377/hw1.0/firmware-5.bin
>> firmware: ath10k/QCA9377/hw1.0/firmware-6.bin
>> firmware: ath10k/QCA6174/hw3.0/board-2.bin
>> firmware: ath10k/QCA6174/hw3.0/board.bin
>> …
>> parm: irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint)
>> …
>> This is most likely because of updating the firmware for your card.
>> -Michael
>>> On 16 Oct 2024, at 16:02, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>>>
>>> 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.
>
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2024-10-17 9:43 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-10-16 15:02 Errors for WLAN card since CU189 Bernhard Bitsch
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox