From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernhard Bitsch To: development@lists.ipfire.org Subject: Re: Errors for WLAN card since CU189 Date: Wed, 16 Oct 2024 21:04:17 +0200 Message-ID: In-Reply-To: <9c1b8f05-f4ee-46d6-8f7e-b6bddfba3ae3@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5757258287619921943==" List-Id: --===============5757258287619921943== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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. >=20 > Messages: > /etc/init.d/hostapd restart > Stopping hostapd...=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 [ > 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 >=20 > 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=20 >> turning the IRQ mode to legacy. It is a setting of the module: >> >> [root(a)fw01 ~]# modinfo ath10k_pci >> filename:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 /lib/modules/6.6.47-ipfire/k= ernel/drivers/net/=20 >> wireless/ath/ath10k/ath10k_pci.ko.xz >> firmware:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ath10k/QCA9377/hw1.0/board.b= in >> firmware:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ath10k/QCA9377/hw1.0/firmwar= e-5.bin >> firmware:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ath10k/QCA9377/hw1.0/firmwar= e-6.bin >> firmware:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ath10k/QCA6174/hw3.0/board-2= .bin >> firmware:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ath10k/QCA6174/hw3.0/board.b= in >> =E2=80=A6 >> parm:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 irq_mode= :0: auto, 1: legacy, 2: msi (default: 0) (uint) >> =E2=80=A6 >> >> This is most likely because of updating the firmware for your card. >> >> -Michael >> >>> On 16 Oct 2024, at 16:02, Bernhard Bitsch 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=20 >>> increase tx pending count: -16, dropping >>> Oct 16 16:10:39 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> increase tx pending count: -16, dropping >>> Oct 16 16:11:20 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:13:45 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> increase tx pending count: -16, dropping >>> Oct 16 16:18:47 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:18:52 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:19:13 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:19:28 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:19:33 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:19:38 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:19:43 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:19:48 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:19:54 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:19:59 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:20:04 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:20:09 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:20:24 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:20:40 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:21:10 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:21:16 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:21:41 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:21:46 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> Oct 16 16:21:51 BitschCop kernel: ath10k_pci 0000:01:00.0: failed to=20 >>> flush transmit queue (skip 0 ar-state 1): 0 >>> ............ >>> >>> Regards, >>> Bernhard >>> >>> BTW: I'm missing the status part of the hostapd WUI page. >> >=20 --===============5757258287619921943==--