[PATCH] add a link to the 7.5 errata

2024-04-29 Thread Piotr Durlej
---
 security.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/security.html b/security.html
index 38b427bb9..eb7f9e0e4 100644
--- a/security.html
+++ b/security.html
@@ -83,7 +83,8 @@ For security advisories for specific releases, click below:
 7.1,
 7.2,
 7.3,
-7.4.
+7.4,
+7.5.
 
 
 
-- 
2.44.0



Re: iwm regression in 7.5 amd64

2024-04-29 Thread Stefan Sperling
On Mon, Apr 29, 2024 at 10:26:15PM +0200, Stefan Sperling wrote:
> Then send me the pcap file off-list.
> 

Received, off-list, thanks!

The config looks fine.
Channel 48, HT secondary channel below at 44, 80 MHz VHT center channel 42.
This is a valid config that will pass the tests we added to avoid firmware
errors. So this cannot be the source of the problem.

Not sure what is going on, sorry.
If you could bisect the regression to a specific commit or at least a
reasonably narrow date-range within the 7.4->7.5 release cycle then
perhaps we'll find a clue.



Re: iwm regression in 7.5 amd64

2024-04-29 Thread Stefan Sperling
On Mon, Apr 29, 2024 at 08:05:31PM +0200, Mizsei Zoltán wrote:
> Yes, it is a general speed regression. Reboot didn1t help. Firmware is 
> up-to-date, and AFAIK nothing else changed. The bottleneck is there in cli 
> aswell, not just in Firefox.
> 
> -- ext

The only possibility I can think of is that the changes to avoid
firmware panics on APs that announce invalid 11ac channel
configurations are implicated.

To know whether this is the case I need to see the beacon channel
configuration info.

While associated, run this for a short while:

tcpdump -n -i iwm0 -y IEEE802_11_RADIO -s4096 -w /tmp/iwm0.pcap type mgt 
subtype beacon

Ctrl-C out of it and check whether tcpdump -r /tmp/iwm0.pcap contains
lines that begin with a timestamp and then "802.11: beacon" and show
your APs SSID.

Then send me the pcap file off-list.



Re: sysupgrade boot.bin apply m1 boot failure

2024-04-29 Thread Klemens Nanni
On Mon, Apr 29, 2024 at 12:58:25PM GMT, bo...@plexuscomp.com wrote:
> >Synopsis:sysupgrade to latest snap results in bootloop, had to replace 
> >boot.bin
> >Category:system aarch64
> >Environment:
>   System  : OpenBSD 7.5
>   Details : OpenBSD 7.5-current (GENERIC.MP) #19: Sun Apr 28 13:44:22 
> MDT 2024
>
> dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
> 
>   Architecture: OpenBSD.arm64
>   Machine : arm64
> >Description:
>   Upgraded my m1 macbook air to the latest snapshot.
> After the installation, reboot, I see the mac logo, asahi logo, no 
> OpenBSD logo, then it reboots and repeats.
> I copied /m1n1/boot.bin from another asahi efi partition to the 
> OpenBSD m1n1 partition and it boots again. 
> >How-To-Repeat:
>   Install a snapshot on a mac?

For the archives:  Installing is not enough, apple-boot's m1n1/boot.bin is
put there by installboot(8) which is run before fw_update(8) fetched it.

So far, it takes an upgrade or manual installboot to boot our firmware
(and thus see the OpenBSD logo).

> >Fix:
Use a boot.bin from asahi



Re: sysupgrade boot.bin apply m1 boot failure

2024-04-29 Thread Mark Kettenis
> Date: Mon, 29 Apr 2024 12:58:25 -0600 (MDT)
> From: bo...@plexuscomp.com
> 
> >Synopsis:sysupgrade to latest snap results in bootloop, had to replace 
> >boot.bin
> >Category:system aarch64
> >Environment:
>   System  : OpenBSD 7.5
>   Details : OpenBSD 7.5-current (GENERIC.MP) #19: Sun Apr 28 13:44:22 
> MDT 2024
>
> dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
> 
>   Architecture: OpenBSD.arm64
>   Machine : arm64
> >Description:
>   Upgraded my m1 macbook air to the latest snapshot.
> After the installation, reboot, I see the mac logo, asahi logo, no 
> OpenBSD logo, then it reboots and repeats.
> I copied /m1n1/boot.bin from another asahi efi partition to the 
> OpenBSD m1n1 partition and it boots again. 
> >How-To-Repeat:
>   Install a snapshot on a mac?
> >Fix:
>   Use a boot.bin from asahi
> 
> 
> dmesg:
> OpenBSD 7.5-current (GENERIC.MP) #19: Sun Apr 28 13:44:22 MDT 2024
> dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
> real mem  = 16379801600 (15620MB)
> avail mem = 15738245120 (15009MB)
> random: good seed from bootblocks
> mainbus0 at root: Apple MacBook Air (M1, 2020)
> efi0 at mainbus0: UEFI 2.10
> efi0: Das U-Boot rev 0x20230700
> cpu0 at mainbus0 mpidr 0: Apple Icestorm r1p1
> cpu0: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
> cpu0: 4096KB 128b/line 16-way L2 cache
> cpu0: 
> TLBIOS+IRANGE,TS+AXFLAG,FHM,DP,SHA3,RDM,Atomic,CRC32,SHA2+SHA512,SHA1,AES+PMULL,SPECRES,SB,FRINTTS,GPI,LRCPC+LDAPUR,FCMA,JSCVT,API+PAC,DPB,SpecSEI,PAN+ATS1E1,LO,HPDS,VH,CSV3,CSV2,DIT,SSBS+MSR
> cpu1 at mainbus0 mpidr 1: Apple Icestorm r1p1
> cpu1: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
> cpu1: 4096KB 128b/line 16-way L2 cache
> cpu2 at mainbus0 mpidr 2: Apple Icestorm r1p1
> cpu2: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
> cpu2: 4096KB 128b/line 16-way L2 cache
> cpu3 at mainbus0 mpidr 3: Apple Icestorm r1p1
> cpu3: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
> cpu3: 4096KB 128b/line 16-way L2 cache
> cpu4 at mainbus0 mpidr 10100: Apple Firestorm r1p1
> cpu4: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
> cpu4: 12288KB 128b/line 12-way L2 cache
> cpu5 at mainbus0 mpidr 10101: Apple Firestorm r1p1
> cpu5: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
> cpu5: 12288KB 128b/line 12-way L2 cache
> cpu6 at mainbus0 mpidr 10102: Apple Firestorm r1p1
> cpu6: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
> cpu6: 12288KB 128b/line 12-way L2 cache
> cpu7 at mainbus0 mpidr 10103: Apple Firestorm r1p1
> cpu7: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
> cpu7: 12288KB 128b/line 12-way L2 cache
> "asc-firmware" at mainbus0 not configured
> "asc-firmware" at mainbus0 not configured
> "framebuffer" at mainbus0 not configured
> "region95" at mainbus0 not configured
> "region94" at mainbus0 not configured
> "region57" at mainbus0 not configured
> "dcp_data" at mainbus0 not configured
> "uat-handoff" at mainbus0 not configured
> "uat-pagetables" at mainbus0 not configured
> "uat-ttbs" at mainbus0 not configured
> "isp-heap" at mainbus0 not configured
> apm0 at mainbus0
> "opp-table-0" at mainbus0 not configured
> "opp-table-1" at mainbus0 not configured
> "opp-table-gpu" at mainbus0 not configured
> agtimer0 at mainbus0: 24000 kHz
> "pmu-e" at mainbus0 not configured
> "pmu-p" at mainbus0 not configured
> "clock-ref" at mainbus0 not configured
> "clock-120m" at mainbus0 not configured
> "clock-200m" at mainbus0 not configured
> "clock-disp0" at mainbus0 not configured
> "clock-dispext0" at mainbus0 not configured
> "clock-ref-nco" at mainbus0 not configured
> simplebus0 at mainbus0: "soc"
> aplpmgr0 at simplebus0
> aplpmgr1 at simplebus0
> aplmbox0 at simplebus0
> apldart0 at simplebus0: 32 bits
> apldart1 at simplebus0: 32 bits, locked
> apldart2 at simplebus0: 32 bits, locked
> aplmbox1 at simplebus0
> apldart3 at simplebus0: 32 bits, bypass
> apldart4 at simplebus0: 32 bits
> apldart5 at simplebus0: 32 bits
> apldart6 at simplebus0: 32 bits, bypass
> aplintc0 at simplebus0 nirq 896 ndie 1
> aplpinctrl0 at simplebus0
> aplpinctrl1 at simplebus0
> apldog0 at simplebus0
> aplmbox2 at simplebus0
> aplpinctrl2 at simplebus0
> aplpinctrl3 at simplebus0
> aplmbox3 at simplebus0
> aplefuse0 at simplebus0
> apldart7 at simplebus0: 32 bits, bypass
> apldart8 at simplebus0: 32 bits, bypass
> apldart9 at simplebus0: 32 bits, bypass
> apldart10 at simplebus0: 32 bits, bypass
> apldart11 at simplebus0: 32 bits
> "gpu" at simplebus0 not configured
> aplcpu0 at simplebus0
> aplcpu1 at simplebus0
> apldcp0 at simplebus0
> apldrm0 at simplebus0
> drm0 at apldrm0
> "isp" at simplebus0 not configured
> apliic0 at simplebus0
> iic0 at apliic0
> tipd0 at iic0 addr 0x38
> tipd1 at iic0 addr 0x3f
> apliic1 at simpleb

sysupgrade boot.bin apply m1 boot failure

2024-04-29 Thread bobby
>Synopsis:  sysupgrade to latest snap results in bootloop, had to replace 
>boot.bin
>Category:  system aarch64
>Environment:
System  : OpenBSD 7.5
Details : OpenBSD 7.5-current (GENERIC.MP) #19: Sun Apr 28 13:44:22 
MDT 2024
 
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP

Architecture: OpenBSD.arm64
Machine : arm64
>Description:
Upgraded my m1 macbook air to the latest snapshot.
After the installation, reboot, I see the mac logo, asahi logo, no 
OpenBSD logo, then it reboots and repeats.
I copied /m1n1/boot.bin from another asahi efi partition to the OpenBSD 
m1n1 partition and it boots again. 
>How-To-Repeat:
Install a snapshot on a mac?
>Fix:
Use a boot.bin from asahi


dmesg:
OpenBSD 7.5-current (GENERIC.MP) #19: Sun Apr 28 13:44:22 MDT 2024
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
real mem  = 16379801600 (15620MB)
avail mem = 15738245120 (15009MB)
random: good seed from bootblocks
mainbus0 at root: Apple MacBook Air (M1, 2020)
efi0 at mainbus0: UEFI 2.10
efi0: Das U-Boot rev 0x20230700
cpu0 at mainbus0 mpidr 0: Apple Icestorm r1p1
cpu0: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu0: 4096KB 128b/line 16-way L2 cache
cpu0: 
TLBIOS+IRANGE,TS+AXFLAG,FHM,DP,SHA3,RDM,Atomic,CRC32,SHA2+SHA512,SHA1,AES+PMULL,SPECRES,SB,FRINTTS,GPI,LRCPC+LDAPUR,FCMA,JSCVT,API+PAC,DPB,SpecSEI,PAN+ATS1E1,LO,HPDS,VH,CSV3,CSV2,DIT,SSBS+MSR
cpu1 at mainbus0 mpidr 1: Apple Icestorm r1p1
cpu1: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu1: 4096KB 128b/line 16-way L2 cache
cpu2 at mainbus0 mpidr 2: Apple Icestorm r1p1
cpu2: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu2: 4096KB 128b/line 16-way L2 cache
cpu3 at mainbus0 mpidr 3: Apple Icestorm r1p1
cpu3: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu3: 4096KB 128b/line 16-way L2 cache
cpu4 at mainbus0 mpidr 10100: Apple Firestorm r1p1
cpu4: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu4: 12288KB 128b/line 12-way L2 cache
cpu5 at mainbus0 mpidr 10101: Apple Firestorm r1p1
cpu5: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu5: 12288KB 128b/line 12-way L2 cache
cpu6 at mainbus0 mpidr 10102: Apple Firestorm r1p1
cpu6: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu6: 12288KB 128b/line 12-way L2 cache
cpu7 at mainbus0 mpidr 10103: Apple Firestorm r1p1
cpu7: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu7: 12288KB 128b/line 12-way L2 cache
"asc-firmware" at mainbus0 not configured
"asc-firmware" at mainbus0 not configured
"framebuffer" at mainbus0 not configured
"region95" at mainbus0 not configured
"region94" at mainbus0 not configured
"region57" at mainbus0 not configured
"dcp_data" at mainbus0 not configured
"uat-handoff" at mainbus0 not configured
"uat-pagetables" at mainbus0 not configured
"uat-ttbs" at mainbus0 not configured
"isp-heap" at mainbus0 not configured
apm0 at mainbus0
"opp-table-0" at mainbus0 not configured
"opp-table-1" at mainbus0 not configured
"opp-table-gpu" at mainbus0 not configured
agtimer0 at mainbus0: 24000 kHz
"pmu-e" at mainbus0 not configured
"pmu-p" at mainbus0 not configured
"clock-ref" at mainbus0 not configured
"clock-120m" at mainbus0 not configured
"clock-200m" at mainbus0 not configured
"clock-disp0" at mainbus0 not configured
"clock-dispext0" at mainbus0 not configured
"clock-ref-nco" at mainbus0 not configured
simplebus0 at mainbus0: "soc"
aplpmgr0 at simplebus0
aplpmgr1 at simplebus0
aplmbox0 at simplebus0
apldart0 at simplebus0: 32 bits
apldart1 at simplebus0: 32 bits, locked
apldart2 at simplebus0: 32 bits, locked
aplmbox1 at simplebus0
apldart3 at simplebus0: 32 bits, bypass
apldart4 at simplebus0: 32 bits
apldart5 at simplebus0: 32 bits
apldart6 at simplebus0: 32 bits, bypass
aplintc0 at simplebus0 nirq 896 ndie 1
aplpinctrl0 at simplebus0
aplpinctrl1 at simplebus0
apldog0 at simplebus0
aplmbox2 at simplebus0
aplpinctrl2 at simplebus0
aplpinctrl3 at simplebus0
aplmbox3 at simplebus0
aplefuse0 at simplebus0
apldart7 at simplebus0: 32 bits, bypass
apldart8 at simplebus0: 32 bits, bypass
apldart9 at simplebus0: 32 bits, bypass
apldart10 at simplebus0: 32 bits, bypass
apldart11 at simplebus0: 32 bits
"gpu" at simplebus0 not configured
aplcpu0 at simplebus0
aplcpu1 at simplebus0
apldcp0 at simplebus0
apldrm0 at simplebus0
drm0 at apldrm0
"isp" at simplebus0 not configured
apliic0 at simplebus0
iic0 at apliic0
tipd0 at iic0 addr 0x38
tipd1 at iic0 addr 0x3f
apliic1 at simplebus0
iic1 at apliic1
tascodec0 at iic1 addr 0x31
apliic2 at simplebus0
iic2 at apliic2
tascodec1 at iic2 addr 0x34
"cirrus,cs42l83" at iic2 addr 0x48 not configured
aplpwm0 at simplebus0
aplspi0 at simplebus0
aplspi1 at simplebus0
aplhidev0 at aplspi1
aplkbd0 at aplhidev0: 8 variable keys, 6 key code

Re: iwm regression in 7.5 amd64

2024-04-29 Thread Mizsei Zoltán
Yes, it is a general speed regression. Reboot didn1t help. Firmware is 
up-to-date, and AFAIK nothing else changed. The bottleneck is there in cli 
aswell, not just in Firefox.

-- ext

Mikhail Pchelin írta 2024. ápr.. 29, H-n 18:13 órakor:
> On Mon, Apr 29, 2024 at 09:19:49AM +0200, Mizsei Zoltán wrote:
>> Hi,
>> 
>> thanks for the input! I sadly don't have any other OBSD machine on this lan, 
>> so i can't do any tcpbench test right now :(
>> 
>> I hovewer did a test with fast.com (same LAN, same router, same computer):
>> - OpenBSD did 4Mbps down, 20 up
>> - Debian 12.5 did 300Mbps down and 20 up. 
>> 
>> Something is really fishy.
>> 
>> I would greatly appreciate any help and advice.
>
> Have you tried different AP in different place? - same speed issue
> there?

-- 
--Z--



Re: iwm regression in 7.5 amd64

2024-04-29 Thread Mikhail Pchelin
On Mon, Apr 29, 2024 at 09:19:49AM +0200, Mizsei Zoltán wrote:
> Hi,
> 
> thanks for the input! I sadly don't have any other OBSD machine on this lan, 
> so i can't do any tcpbench test right now :(
> 
> I hovewer did a test with fast.com (same LAN, same router, same computer):
> - OpenBSD did 4Mbps down, 20 up
> - Debian 12.5 did 300Mbps down and 20 up. 
> 
> Something is really fishy.
> 
> I would greatly appreciate any help and advice.

Have you tried different AP in different place? - same speed issue
there?



Re: problem with qwx on thinkpad arm

2024-04-29 Thread BESSOT Jean-Michel



On 28/04/2024 17:59, Stefan Sperling wrote:

On Sun, Apr 28, 2024 at 01:46:22PM +0200, BESSOT Jean-Michel wrote:

Hello

Hello

qwx does not work after the last snapshot.

There is an error message in dmesg that I send.

If you need more information feel free to ask.

bye
qwx0: could not allocate DP SRNG DMA memory

Does this error persist or is it only happening occasionally?


I only got it one time and I could restart the netstart script it didn't

work.

  
Does it persist after rebooting?oot (autoconf)

no

and keep it around to avoid such errors in case the system ru


It looks like your machine ran out of sufficient non-fragmented
memory below 4GB, which was evidently still available while the
system was booting since the firmware version was displayed,
meaning the affected code path ran successfully at least once.

The qwx driver is doing a lot of DMA allocations during 'ifconfig qwx0 up'
because the code inherited from Linux behaves this way and I didn't have
the guts to change that during the initial porting effort as it would have
made things even more complicated during this early phase of development.

Generally, OpenBSD drivers reserve DMA memory during early boot (autoconf)
and keep it around to avoid such errors in case the system runs out of
sufficient usable fresh DMA memory later.
So this issue could probably be avoided by refactoring things such that
DMA memory is only allocated once and not freed when the interface goes
down.

The rest of the error messages are most likely just fallout from the
above allocation error.


qwx_dp_pdev_reo_setup: failed to setup reo_dst_ring
qwx_core_start: failed to initialize reo destination rings: 12
qwx0: failed to start core: 12
qwx0: tx credits timeout
qwx0: failed to send WMI_PDEV_SET_PARAM cmd
qwx0: failed to enable dynamic bw for pdev 0: 35


Thank you

Bye




security(8) spams "Device not configured" daily

2024-04-29 Thread Alexander Klimov

Hello everyone!

To reproduce the following, a laptop and two USB sticks are enough.

1) Plug them in and create a RAID 1C or crypto.
One stick is the key, the other contains the array partition(s).

2) Run bioctl softraid0. Ensure everything is as expected.

3) Detach the key stick.

4) Run bioctl softraid0. The key stick is still listed!

5) Run /usr/libexec/security as often as you want.
Every time it will say: "disklabel: /dev/rXdYc: Device not configured"

I thought about making a patch for security(8) to ignore key disks, but
I know you OpenBSD devs want things to work properly (or not at all).

So I've digged through the softraid code. But it seems not to contain
hotplug handling for key disks (neither even bioctl -O handling).
And I have no idea where to even start fixing.

Best,
A/K



Re: iwm regression in 7.5 amd64

2024-04-29 Thread Stuart Henderson
On 2024/04/29 09:19, Mizsei Zoltán wrote:
> Hi,
> 
> thanks for the input! I sadly don't have any other OBSD machine on this lan, 
> so i can't do any tcpbench test right now :(

How about iperf? (iperf2 usually preferred over iperf3).

> I hovewer did a test with fast.com (same LAN, same router, same computer):
> - OpenBSD did 4Mbps down, 20 up
> - Debian 12.5 did 300Mbps down and 20 up. 
> 
> Something is really fishy.
> 
> I would greatly appreciate any help and advice.
> 
> Regards,
> --ext
> 
> 
> Stefan Sperling írta 2024. ápr.. 28, V-n 22:02 órakor:
> > On Sun, Apr 28, 2024 at 09:45:42PM +0200, Mizsei Zoltán wrote:
> >> >Synopsis: iwm regression in 7.5 amd64
> >> >Category: amd64
> >> >Environment:
> >>System  : OpenBSD 7.5
> >>Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024
> >> 
> >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> >> 
> >>Architecture: OpenBSD.amd64
> >>Machine : amd64
> >> >Description:
> >>I've noticed radically reduced networking speed since the 7.5 update. 
> >> On 500Mbit net I experience 3-5 Mbit upload and 20 Mbit download speeds. 
> >> Nothing else changed, as far as i know. 
> >> >How-To-Repeat:
> >>Do a speedtest on 7.5 amd64 GENERIC system using an iwm card and with 
> >> up-to-date firefox.
> >> >Fix:
> >>No idea
> >
> > Please test with tcpbench to a host on LAN behind your AP. Running
> > a speed test to the internet is pointless if the goal is to measure
> > wifi throughput.
> >
> > With tcpbench I am seeing about 290Mbps Tx and Rx with iwm0.
> >
> > Generic internet speed test fast.com shows 210Mbps down, 86Mbps up.
> > That's less than the wifi is capable of.
> >
> >> iwm0 at pci4 dev 0 function 0 "Intel Dual Band Wireless-AC 8265" rev 0x78, 
> >> msi
> >
> > I was also testing with 8265.
> 
> -- 
> --Z--
> 



Re: iwm regression in 7.5 amd64

2024-04-29 Thread Mizsei Zoltán
Hi,

thanks for the input! I sadly don't have any other OBSD machine on this lan, so 
i can't do any tcpbench test right now :(

I hovewer did a test with fast.com (same LAN, same router, same computer):
- OpenBSD did 4Mbps down, 20 up
- Debian 12.5 did 300Mbps down and 20 up. 

Something is really fishy.

I would greatly appreciate any help and advice.

Regards,
--ext


Stefan Sperling írta 2024. ápr.. 28, V-n 22:02 órakor:
> On Sun, Apr 28, 2024 at 09:45:42PM +0200, Mizsei Zoltán wrote:
>> >Synopsis:   iwm regression in 7.5 amd64
>> >Category:   amd64
>> >Environment:
>>  System  : OpenBSD 7.5
>>  Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024
>>   
>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>> 
>>  Architecture: OpenBSD.amd64
>>  Machine : amd64
>> >Description:
>>  I've noticed radically reduced networking speed since the 7.5 update. 
>> On 500Mbit net I experience 3-5 Mbit upload and 20 Mbit download speeds. 
>> Nothing else changed, as far as i know. 
>> >How-To-Repeat:
>>  Do a speedtest on 7.5 amd64 GENERIC system using an iwm card and with 
>> up-to-date firefox.
>> >Fix:
>>  No idea
>
> Please test with tcpbench to a host on LAN behind your AP. Running
> a speed test to the internet is pointless if the goal is to measure
> wifi throughput.
>
> With tcpbench I am seeing about 290Mbps Tx and Rx with iwm0.
>
> Generic internet speed test fast.com shows 210Mbps down, 86Mbps up.
> That's less than the wifi is capable of.
>
>> iwm0 at pci4 dev 0 function 0 "Intel Dual Band Wireless-AC 8265" rev 0x78, 
>> msi
>
> I was also testing with 8265.

-- 
--Z--