Bug 231716

Summary: scp stalls on (slightly) big files over wifi
Product: Base System Reporter: Jørn Gabrielsen <jorntg>
Component: wirelessAssignee: freebsd-wireless (Nobody) <wireless>
Status: Closed Feedback Timeout    
Severity: Affects Only Me CC: bz
Priority: ---    
Version: CURRENT   
Hardware: Any   
OS: Any   
Bug Depends on:    
Bug Blocks: 278175    
Attachments:
Description Flags
Output of scp -v on FreeBSD and GNU/Linux none

Description Jørn Gabrielsen 2018-09-25 13:50:35 UTC
Created attachment 197487 [details]
Output of scp -v on FreeBSD and GNU/Linux

When I use scp to copy a big (100Mb) file from, or to, the laptop running FreeBSD, it allways stalls, usually at 24Mb, sometimes a bit more, but never at 100Mb

This only occurs over wifi. When using wired network, everything is fine.

I have allso tried the same with GNU/Linux installed on the laptop and everything works fine.

When the scp stalls, I am still able to, for instance, browse the web or using an other ssh session, so it is not the network going down.

The laptop is a Lenovo W500 with Intel wifi: 
iwn0@pci0:3:0:0:	class=0x028000 card=0x10118086 chip=0x42368086 rev=0x00 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'Ultimate N WiFi Link 5300'
    class      = network
    cap 01[c8] = powerspec 3  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
    cap 10[e0] = PCI-Express 1 endpoint max data 128(128) FLR RO NS
                 link x1(x1) speed 2.5(2.5) ASPM L0s/L1(L0s/L1)
    ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected
    ecap 0003[140] = Serial 1 0016eaffffc17714

Attached output from FreeBSD and GNU/Linux (100Mb is a remote file on a Linux server)
Comment 1 Bjoern A. Zeeb freebsd_committer freebsd_triage 2024-03-05 21:22:59 UTC
I know it's late but I'll give it a shot anyway;  did this ever get resolved,  can you still reproduce it so we could debug?
Comment 2 Bjoern A. Zeeb freebsd_committer freebsd_triage 2024-06-08 01:21:26 UTC
Hi,

I am sorry no one did help timely.  If the issue still exists please re-open the PR and we can see.