Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 Sep 2025 21:57:27 +0000 (UTC)
From:      "Bjoern A. Zeeb" <bz@freebsd.org>
To:        Nuno Teixeira <eduardo@freebsd.org>
Cc:        FreeBSD wireless mailing list <wireless@freebsd.org>
Subject:   Re: Please test iwlwifi/rtw88/rtw89 now
Message-ID:  <p76s1254-0930-6q11-819o-2s9s705qnr2p@serrofq.bet>
In-Reply-To: <CAFDf7ULe_ydt7vB_m-x2mc_7w8TEvp-JBWeCcTdz1nBXcBdM-g@mail.gmail.com>
References:  <pp8s28qp-78n8-n9p8-49n0-o99qqpop47q9@SerrOFQ.bet> <CAFDf7U%2B16xjHbX2tgbLwoKhxWFUJu7tzfHCmAhsMQt_CQAQ9cQ@mail.gmail.com> <CAFDf7ULe_ydt7vB_m-x2mc_7w8TEvp-JBWeCcTdz1nBXcBdM-g@mail.gmail.com>

index | next in thread | previous in thread | raw e-mail

On Wed, 3 Sep 2025, Nuno Teixeira wrote:

> (...)
>
> After a few hours:
>
> Sep  3 22:02:06 leg kernel: iwlwifi0: WRT: Collecting data: ini trigger 4
> fired (delay=0ms).
> Sep  3 22:02:06 leg kernel: bad state = 0
> Sep  3 22:02:06 leg kernel: iwlwifi0: HCMD_ACTIVE already clear for command
> SCAN_CFG_CMD
> Sep  3 22:02:15 leg kernel: iwlwifi0: Queue 2 is stuck 109 29
>
> Net have stoped, I needed to restart netif.
> I'm sending messages log.

So this is a scan command send to firmware which never came back.

This wouldn't by any chance coincide with you getting bluetooth working
(I see a few errors in the log minutes before)?

/bz

-- 
Bjoern A. Zeeb                                                     r15:7


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p76s1254-0930-6q11-819o-2s9s705qnr2p>