(2018-11-08, 04:45)jmerrilljr Wrote: Whew!!!!

(2018-11-08, 12:00)Milhouse Wrote:

(2018-11-08, 04:45)jmerrilljr Wrote: Whew!!!!

Can you try a different swtich, maybe a Gig-ethernet capable switch? From your log, and your LE8.2.5 iperf results, you're connecting at 100Mbp/s. I wonder if you still have problems with 4.19 when using a different switch? 

(2018-11-08, 15:39)jmerrilljr Wrote:

(2018-11-08, 12:00)Milhouse Wrote:

(2018-11-08, 04:45)jmerrilljr Wrote: Whew!!!!

Can you try a different swtich, maybe a Gig-ethernet capable switch? From your log, and your LE8.2.5 iperf results, you're connecting at 100Mbp/s. I wonder if you still have problems with 4.19 when using a different switch? 

That is a gig-ethernet switch. I guess the first thing is to get a new cable. Any other suggestions?

(2018-11-08, 15:39)jmerrilljr Wrote:

(2018-11-08, 12:00)Milhouse Wrote:

(2018-11-08, 04:45)jmerrilljr Wrote: Whew!!!!

Can you try a different swtich, maybe a Gig-ethernet capable switch? From your log, and your LE8.2.5 iperf results, you're connecting at 100Mbp/s. I wonder if you still have problems with 4.19 when using a different switch?    

That is a gig-ethernet switch. I guess the first thing is to get a new cable. Any other suggestions?   

(2018-11-08, 19:03)Milhouse Wrote:

(2018-11-08, 15:39)jmerrilljr Wrote:

(2018-11-08, 12:00)Milhouse Wrote: Can you try a different swtich, maybe a Gig-ethernet capable switch? From your log, and your LE8.2.5 iperf results, you're connecting at 100Mbp/s. I wonder if you still have problems with 4.19 when using a different switch? 

That is a gig-ethernet switch. I guess the first thing is to get a new cable. Any other suggestions?  

Nope, just a decent CAT5e cable to start with. If you still have problems with a new cable then we'll need the #1016/#1016x kernel logs to take things forward. If the new cable resolves the issue then it might still be worth having the logs - my plan is to ping them to a kernel developer familiar with the r8169, based on the assumption that the 4.19-rc1 kernel introduces some sort of regressive behaviour.  

(2018-11-08, 23:03)jmerrilljr Wrote: I then installed 1016 followed by 1016x and got this:

#10016
http://ix.io/1rla
#10016x
http://ix.io/1rlc

Just to make things interesting I ran #1107 which works fine, now. I'm going to try to figure out the problem with the switch. I have a Time Warner modem that connects via ethernet to an Apple base station. The ethernet runs from the Apple basestation as does the wireless. I will refigure that setup.

text:
# uname -a

Linux NUC 4.19.1 #1 SMP Thu Nov 8 21:04:25 GMT 2018 x86_64 GNU/Linux



# lsb_release

LibreELEC (Milhouse): devel-20181108210234-#1108-ge8e2816 [Build #1108]



# Kodi version

(18.0-RC1 Git:c674db0). Platform: Linux x86 64-bit

• Includes latest kodi-platform master (e8574b8)
  
• Includes latest libcec master (d57d3ac, ahead +7)
  
• Includes latest libnfs master (6dfc87d, ahead +10)
  
• Includes latest p8-platform master (1eb12b1, ahead +1)
  
• Includes latest addons: inputstream.adaptive (d1bb1eb, +3), inputstream.rtmp (ce7f559), peripheral.joystick (2008fdc, +1), peripheral.xarcade (f09a0e7, +1), pvr.argustv (609a2e7, +2), pvr.demo (964686d), pvr.dvblink (47cbff0, +2), pvr.dvbviewer (a9b204e, +8), pvr.filmon (f736ab4, +2), pvr.hdhomerun (a9d7309, +1), pvr.hts (f4ea60f, +2), pvr.iptvsimple (90a8d6f, +1), pvr.mediaportal.tvserver (e4a9dae, +2), pvr.mythtv (db3e73b, +4), pvr.nextpvr (7e36106, +2), pvr.njoy (4467cac, +1), pvr.octonet (203f800), pvr.pctv (e28a90f, +2), pvr.stalker (a99ad5e, +2), pvr.teleboy (484db31), pvr.vbox (6ed2f63, +2), pvr.vdr.vnsi (6bbdb78), pvr.vuplus (d77458b, +2), pvr.wmc (e00c895, +2), pvr.zattoo (41268ee), vfs.libarchive (6d39012), vfs.sftp (6749200)
  
• Include [env] compare (perma): TESTING: increase timeout to ensure OS is able to create core dump/crash log
  
• Include [env] patch: RPi/RPi2: enable Broadcom WiFi debugging (see details)
  
• Include [env] patch: kodi: use upstream repo for Milhouse RPi builds
  
• Include [env] patch: kodi: remove annoying, excessively repetitive addon logging
  
• Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.* and os.*
  
• Include [env] patch: rev hack for kodi
  
• Include [env] patch: Bump included addon versions to prevent online updates
  
• Include [env] patch: Add experimental splash video for RPi
  
• Include [env] patch: Add kodi binary addons (pvr, adsp, inputstream, vfs, peripheral.joystick/xarcade, other)
  
• Include [env] PR:3077 (perma): kodi: use project specific cputemp scripts for all projects
  
• Include [env] PR:3084 (perma): linux (RPi/Generic): update to linux-4.19.1
  
• Include [env] PR:3089 (perma): iptables: update to iptables-1.8.1
  
• Include [env] PR:3092 (perma): samba: update to samba-4.9.2
  

1. samba: update to samba-4.9.2
   
2. libcec 4.0.3
   
3. [Settings] Implement FindIntInList in CSettingList
   

1. LibreELEC.tv:
   • lcdd: build with optimization (PR:3094, 1 commit, 2 files changed)
     
2. XBMC:
   • windowing/gbm: fallback to non-alpha visual id (PR:14785, 3 commits, 7 files changed)
     
   • [Settings] Implement FindIntInList in CSettingList (PR:14815, 1 commit, 3 files changed)
     
   • [macos] [filemanager] Removable storage fixes/improvements (PR:14818, 2 commits, 6 files changed)
     
   • [osx/windowing] - fix "blank other displays" (PR:14822, 1 commit, 1 file changed)
     
   • [macos] CDarwinStorageProvider::Eject: Fix crash due to double release of DADiskRef instance. (PR:14827, 2 commits, 1 file changed)
     
3. libcec:
   • changed/fixed: install cec-client by default. correct vs redist (6c76f5f)
     
   • changed: build with vs 2015 (d8bd948)
     
   • bump to 4.0.3 (d57d3ac)
     
4. pvr.mythtv:
   • default settings (4cf000a)
     
   • bump version 5.8.15 (db3e73b)
     
5. Additional commits/pull requests/changes not yet merged upstream:
   • Added: [env] PR:3092 (perma): samba: update to samba-4.9.2
     

(2018-11-09, 03:44)Milhouse Wrote:

(2018-11-08, 23:03)jmerrilljr Wrote: I then installed 1016 followed by 1016x and got this:

#10016
http://ix.io/1rla
#10016x
http://ix.io/1rlc

Just to make things interesting I ran #1107 which works fine, now. I'm going to try to figure out the problem with the switch. I have a Time Warner modem that connects via ethernet to an Apple base station. The ethernet runs from the Apple basestation as does the wireless. I will refigure that setup.

Yes, I'm not seeing any errors in your #1016x kernel log when connecting at 1Gbps, so this may be an issue triggered when connecting at 100Mbps.

@jwegman It's most likely the same issue, you can confirm by testing #1016 and #1016x, but without kernel logs from #1016/#1016x it's not possible to determine what you have in common with @jmerrilljr. For instance, do you also have an r8169, are you connecting at 100Mbps etc.? 

(2018-11-09, 04:21)jmerrilljr Wrote:

(2018-11-09, 03:44)Milhouse Wrote:

(2018-11-08, 23:03)jmerrilljr Wrote: I then installed 1016 followed by 1016x and got this:

#10016
http://ix.io/1rla
#10016x
http://ix.io/1rlc

Just to make things interesting I ran #1107 which works fine, now. I'm going to try to figure out the problem with the switch. I have a Time Warner modem that connects via ethernet to an Apple base station. The ethernet runs from the Apple basestation as does the wireless. I will refigure that setup.

Yes, I'm not seeing any errors in your #1016x kernel log when connecting at 1Gbps, so this may be an issue triggered when connecting at 100Mbps.

@jwegman It's most likely the same issue, you can confirm by testing #1016 and #1016x, but without kernel logs from #1016/#1016x it's not possible to determine what you have in common with @jmerrilljr. For instance, do you also have an r8169, are you connecting at 100Mbps etc.?  

I went back to my original networking setup because Libreelec does not play nice with the non-switched setup. Lots of ip address changes, etc. so I'm back to the slow connection. However, #1107 still plays well. Go figure? I think I need to contact Time Warner/Spectrum and get some info re: their modem. 

(2018-11-09, 04:37)jmerrilljr Wrote:

(2018-11-09, 04:21)jmerrilljr Wrote:

(2018-11-09, 03:44)Milhouse Wrote: Yes, I'm not seeing any errors in your #1016x kernel log when connecting at 1Gbps, so this may be an issue triggered when connecting at 100Mbps.

@jwegman It's most likely the same issue, you can confirm by testing #1016 and #1016x, but without kernel logs from #1016/#1016x it's not possible to determine what you have in common with @jmerrilljr. For instance, do you also have an r8169, are you connecting at 100Mbps etc.?  

I went back to my original networking setup because Libreelec does not play nice with the non-switched setup. Lots of ip address changes, etc. so I'm back to the slow connection. However, #1107 still plays well. Go figure? I think I need to contact Time Warner/Spectrum and get some info re: their modem.  

 I will retest #1016 and #1016x tomorrow at 100Mbps  and will get kernel logs for you. 

(2018-11-08, 19:10)jwegman Wrote:

(2018-11-08, 15:39)jmerrilljr Wrote:

(2018-11-08, 12:00)Milhouse Wrote: Can you try a different swtich, maybe a Gig-ethernet capable switch? From your log, and your LE8.2.5 iperf results, you're connecting at 100Mbp/s. I wonder if you still have problems with 4.19 when using a different switch?    

That is a gig-ethernet switch. I guess the first thing is to get a new cable. Any other suggestions?     

FYI; I'm also having the same issue in the recent builds, on a Asus Chromebox CN60, so the issue isn't isolate to @jmerrilljr or his network switch.  The following keeps repeating: 

(2018-11-09, 17:14)supergroover Wrote:

(2018-11-08, 19:10)jwegman Wrote:

(2018-11-08, 15:39)jmerrilljr Wrote: That is a gig-ethernet switch. I guess the first thing is to get a new cable. Any other suggestions?     

FYI; I'm also having the same issue in the recent builds, on a Asus Chromebox CN60, so the issue isn't isolate to @jmerrilljr or his network switch.  The following keeps repeating: 

I have the same "buffering" problems with a Asus Chromebox M004U with the latest builds.

(2018-11-09, 17:16)Milhouse Wrote:

(2018-11-09, 17:14)supergroover Wrote:

(2018-11-08, 19:10)jwegman Wrote: FYI; I'm also having the same issue in the recent builds, on a Asus Chromebox CN60, so the issue isn't isolate to @jmerrilljr or his network switch.  The following keeps repeating: 

I have the same "buffering" problems with a Asus Chromebox M004U with the latest builds.

No log no problem. In this case I'll need a kernel log. Compare #1016/#1016x. Logs from both please.