On Sun, Apr 21, 2024 at 06:31:39PM +0200, Kirill A. Korinsky wrote:
> Greeting,
>
> finally I've catch something. I not sure is it the same error or not, but it
> seems right to share anyway.
>
> It was get from snapshot which was installed about 3 days ago.
>
> Apr 21 10:59:40 matebook /bsd:
Greeting,
finally I've catch something. I not sure is it the same error or not, but it
seems right to share anyway.
It was get from snapshot which was installed about 3 days ago.
Apr 21 10:59:40 matebook /bsd: iwx0: dumping device error log
Apr 21 10:59:40 matebook /bsd: iwx0: Start Error
On Wed, Mar 13, 2024 at 12:05:59AM +0100, Kirill A. Korinsky wrote:
> On Tue, 27 Feb 2024 08:45:44 +0100,
> Stefan Sperling wrote:
> >
> > > Anyway, I'll keep debug enabled for the case if frimeware error happens.
> >
> > Yes, that would still be interesting, thanks.
>
> Here it is:
>
>
On Tue, 27 Feb 2024 08:45:44 +0100,
Stefan Sperling wrote:
>
> > Anyway, I'll keep debug enabled for the case if frimeware error happens.
>
> Yes, that would still be interesting, thanks.
Here it is:
iwx0: unhandled firmware response 0x3ff/0x2008 rx ring 95[17]
iwx0: fatal firmware
On Tue, 27 Feb 2024 08:45:44 +0100,
Stefan Sperling wrote:
>
> On Mon, Feb 26, 2024 at 10:17:20PM +0100, Kirill A. Korinsky wrote:
>
> > Anyway, I'll keep debug enabled for the case if frimeware error happens.
>
> Yes, that would still be interesting, thanks.
It's happening not each boot. I've
On Mon, Feb 26, 2024 at 10:17:20PM +0100, Kirill A. Korinsky wrote:
> On Mon, 26 Feb 2024 12:39:12 +0100,
> Stefan Sperling wrote:
> >
> > On Mon, Feb 26, 2024 at 11:40:35AM +0100, Kirill A. Korinsky wrote:
> > > all of this seems like a strong indicator that the issue is inside iwx
> >
> > I
On Mon, 26 Feb 2024 12:39:12 +0100,
Stefan Sperling wrote:
>
> On Mon, Feb 26, 2024 at 11:40:35AM +0100, Kirill A. Korinsky wrote:
> > all of this seems like a strong indicator that the issue is inside iwx
>
> I have no idea what causes the latency spikes you are seeing, and
> none of the info
On Mon, 26 Feb 2024 12:39:12 +0100,
Stefan Sperling wrote:
>
> On Mon, Feb 26, 2024 at 11:40:35AM +0100, Kirill A. Korinsky wrote:
> > all of this seems like a strong indicator that the issue is inside iwx
>
> You don't need to try hard to convince me that there could be
> a bug in iwx. Yes,
On Mon, Feb 26, 2024 at 11:40:35AM +0100, Kirill A. Korinsky wrote:
> all of this seems like a strong indicator that the issue is inside iwx
You don't need to try hard to convince me that there could be
a bug in iwx. Yes, there will always be bugs in iwx. Many have
been fixed already but there
I'd like to add an example of ping and iperf to some host in my network
which shows how wired network is:
~ $ ping 172.31.3.10
PING 172.31.3.10 (172.31.3.10): 56 data bytes
64 bytes from 172.31.3.10: icmp_seq=0 ttl=63 time=209.458 ms
64 bytes from 172.31.3.10: icmp_seq=1 ttl=63
On Sun, 25 Feb 2024 23:03:31 +0100,
Stefan Sperling wrote:
>
> To get more information about this error please run with 'ifconfig iwx0
> debug'.
> Just adding the line 'debug' in /etc/hostname.iwx0 is enough to activate
> at boot. It will be a bit more noise in dmesg and once this firmware error
On Sun, Feb 25, 2024 at 10:17:37PM +0100, Kirill A. Korinsky wrote:
> On Sun, 25 Feb 2024 17:32:46 +0100,
> Stefan Sperling wrote:
> >
> > I have less than 2ms ping latency to my 5 GHz AP over iwx.
> > So this is probably not an issue in iwx but something else.
>
> I wan't near machine for
On Sun, 25 Feb 2024 17:32:46 +0100,
Stefan Sperling wrote:
>
> I have less than 2ms ping latency to my 5 GHz AP over iwx.
> So this is probably not an issue in iwx but something else.
I wan't near machine for couple of hours, but it stay up and connected to
the wifinetwork.
When I'll back
On Sun, Feb 25, 2024 at 05:19:33PM +0100, Kirill A. Korinsky wrote:
> Well,
>
> I just rebooted to a new snapshot, and WiFi has been future degradated.
>
> I do run a MPD sync in background which downloads some files via HTTP,
> but I may run before, and it never creates an issue.
>
> Meanwhile
Well,
I just rebooted to a new snapshot, and WiFi has been future degradated.
I do run a MPD sync in background which downloads some files via HTTP,
but I may run before, and it never creates an issue.
Meanwhile the ping to GW from latop seems like:
~ $ ping 172.31.2.1
PING 172.31.2.1
On Fri, 16 Feb 2024 12:13:32 +0100,
Stefan Sperling wrote:
>
> I might have found the root cause of your problem in iwx.
> Can you try this diff please?
>
> diff /usr/src
> commit - 5f5902b3789b6f994566004963a31af6304d3a70
> path + /usr/src
> blob - 4b945edf2c73c6e2582819b283277baff81a6586
>
On Fri, Feb 16, 2024 at 11:25:51AM +, Stuart Henderson wrote:
> Also: regardless of whether it really makes sense for a given network,
> sometimes a network operator will do this anyway and as a user you have
> no control over it - and based on Kirill's description this seems a
> regression
On 2024/02/16 10:13, Stefan Sperling wrote:
> Tne driver uses the lowest basic rate anncounced by the AP:
>
> const struct iwx_rate *
> iwx_tx_fill_cmd(struct iwx_softc *sc, struct iwx_node *in,
> struct ieee80211_frame *wh, uint16_t *flags, uint32_t *rate_n_flags)
> {
> [...]
>
On Fri, Feb 16, 2024 at 11:45:30AM +0100, Kirill A. Korinsky wrote:
> Stefan,
>
> On Fri, 16 Feb 2024 10:13:50 +0100,
> Stefan Sperling wrote:
> >
> > If your AP still announces 6M even while you've disabled this rate in
> > settings,
> > then the AP is broken and there is nothing to fix for us,
Stefan,
On Fri, 16 Feb 2024 10:13:50 +0100,
Stefan Sperling wrote:
>
> If your AP still announces 6M even while you've disabled this rate in
> settings,
> then the AP is broken and there is nothing to fix for us, you could only try
> asking the vendor for an AP firmware fix. Otherwise, there
On Fri, Feb 16, 2024 at 03:22:07AM +0100, Kirill A. Korinsky wrote:
> Thus, disabling 5Ghz does help. that lead me to dig an issue on network
> settings
> side. After poking around I've discovered that settings which triggers an
> issue
> is "Minimum Data Rate Control" inside Unifi UI. It has
ifconfig iwx0 debug, reconnect:
Feb 16 03:00:17 matebook /bsd: iwx0: using firmware iwx-QuZ-a0-hr-b0-77
Feb 16 03:00:17 matebook /bsd: iwx0: begin active scan
Feb 16 03:00:17 matebook /bsd: iwx0: INIT -> SCAN
Feb 16 03:00:21 matebook /bsd: iwx0: end active scan
Feb 16 03:00:21
>Synopsis: iwx obtains IP via DHCP but no traffic
>Category: network, drivers
>Environment:
System : OpenBSD 7.4
Details : OpenBSD 7.4-current (GENERIC.MP) #1688: Thu Feb 15
10:48:34 MST 2024
dera...@amd64.openbsd.org:/usr/src
23 matches
Mail list logo
