Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Apr 2024 00:49:20 +0000
From:      bugzilla-noreply@freebsd.org
To:        wireless@FreeBSD.org
Subject:   [Bug 263632] iwlwifi(4) crashes (freezes) a few seconds after resuming from sleep (suspend/resume not working; workaround known for now)
Message-ID:  <bug-263632-21060-xkoyYSoTxU@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-263632-21060@https.bugs.freebsd.org/bugzilla/>
References:  <bug-263632-21060@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263632

--- Comment #34 from Jonathan Vasquez <jon@xyinn.org> ---
Hey Bjoern,

I wanted to give an update since I recently purchase a new Intel AX210 card
(and swapped out my Atheros chip - which has been working pretty well but
FreeBSD in general has slow performance with basically all of the wireless
chips I've tried) in order to re-test the iwlwifi driver.

These results are on the latest FreeBSD 14-RELEASE (FreeBSD leslie
14.0-RELEASE-p6 FreeBSD 14.0-RELEASE-p6 #0: Tue Mar 26 20:26:20 UTC 2024=20=
=20=20=20
root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
amd64).

The good news is that the basic packet passing is working and I can reach t=
he
internet, my NAS (over NFS), watch videos, and that sort of basic stuff.

The bad news is that if I put the machine to sleep and then resume, even if=
 it
doesn't crash during the first attempt, the connection never automatically
works again. ifconfig mentions that it's still associated, but I can't ping
anything. After putting the machine to sleep/resumed a few more times in a =
row,
I eventually got the machine to crash on the third attempt.

This was connected on 2.4 GHz frequency. Attempting to connect to my 5 GHz
channel never worked. I did see it associated for a few seconds, and then
disconnected (same passphrase and I know both of my frequencies work perfec=
tly
fine with my other devices).

Another thing is that the performance of the chip is just way to slow to be
usable. I tried transferring a 2.1 GB file and after 6 minutes I gave up. I
tried transferring a 684 MB file from my NAS (over NFS) and it took 14 minu=
tes
to complete. I did see the following line in `ifconfig` slowly drop from 54
Mbps to about 6 Mbps over the duration of the 14 minutes, it may have even
dropped lower:

media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263632-21060-xkoyYSoTxU>