Kodi Community Forum

Full Version: [SOLVED?] Intel UHD 630 lag during "kodi.bin [fileCache]"
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
[UPDATE:  07/21/2019]
Working on manually installing Nightly in Debian see ( This ) post . Also trying to get VA hardware rendering working. Along with disabling swap and seeing if I can force fileCache to use RAM only ..

Looks like it 'helped' still not using the 3GIG HW rendering ( I think the 3gigs is ram not sure how these onboard videocards work but from what I understand this board can handel 4K so WTF...by setting memorysize high and readfactor  low it does not cache much at all so I dont have the issue. not sure what even cacheing the entire video does ... I see little to no difference between the two ... tested fine with 32x playback for en entire 1 1/2hr movie and no lag .. I got nothing ...problem sloved ?? I still would like to get GPU playback working so the CPU does not have to work as hard but seeing SW in playback info menu and the VA errors and highish CPU I assume its not using GPU playback.

cat /home/plex/.kodi/userdata/advancedsettings.xml
<advancedsettings>
  <cache>
    <buffermode>1</buffermode>
    <memorysize>5368709120</memorysize>
    <readfactor>4</readfactor>
  </cache>
</advancedsettings>


Reference:
https://wiki.archlinux.org/index.php/Har...celeration ( give you an idea about video support for *nix )
https://forums.plex.tv/t/i5-9600k-intel-...ing/394742
https://github.com/intel/media-driver


Screenshot

https://drive.google.com/file/d/1-ATm-iL...sp=sharing

Added Kodi log 

https://drive.google.com/file/d/1v_Z9YFW...sp=sharing

---------------

* seems to be fine at first on a reboot ...still lags in the UI but player works fine ( 07/21/2019) 
Seems to freze the entire system even over SSH ...
VLC software rendering works fine but GPU or CPU in Kodi laggs 
Video starts just fine but after about a minute or 5 I get the lag and sometimes with larger files it lags out Kodi for 5-10 min and/or crashes 
CPU is almost 0%
GPU is at 13-17% even when paused and fully (bufferd)
"kodi.bin [fileCache]" is running when I have these issues
searching for "lag" or anything of the such returns a bunch of BS about garbage streamin plugins online for Kodi ...
complied and installed libva from git same issue



Reference:
https://serverfault.com/questions/659164...disk-write
https://erikugel.wordpress.com/tag/tune2fs/
ERROR: VAAPI::CheckSuccess error: unknown libva error


-----------------

GRUB_CMDLINE_LINUX="spectre_v2=off nopti pti=off acpi=off apm=off"



------------------

100% IO DISK USAGE ? 
jbd2/sda1-8
kworker/u24:1+flush-8:0

------

at /sys/kernel/debug/tracing/trace_pipe 
     jbd2/sda1-8-294   [008] ....  1312.036884: jbd2_run_stats: dev 8,1 tid 79826293 wait 0 request_delay 0 running 3244 locked 336 flushing 0 logging 4816 handle_count 18723 blocks 22 blocks_logged 23
     jbd2/sdb1-8-557   [002] ....  1320.919783: jbd2_run_stats: dev 8,17 tid 49649 wait 0 request_delay 0 running 5016 locked 0 flushing 0 logging 20 handle_count 14 blocks 1 blocks_logged 2
     jbd2/sda1-8-294   [008] ....  1323.190885: jbd2_run_stats: dev 8,1 tid 79826294 wait 0 request_delay 0 running 4816 locked 0 flushing 0 logging 11156 handle_count 28200 blocks 26 blocks_logged 27
     jbd2/sda1-8-294   [003] ....  1324.531622: jbd2_run_stats: dev 8,1 tid 79826295 wait 0 request_delay 10420 running 11148 locked 0 flushing 0 logging 1340 handle_count 60376 blocks 26 blocks_logged 27



---------------
I enabled the following on media drives ( not boot/OS ) in fstab

# reference https://erikugel.wordpress.com/tag/tune2fs/ http://dcjtech.info/topic/etcfstab-options/
noatime,nodiratime,data=writeback,barrier=0,noblock_validity,nodelalloc,nouser_xattr,noacl

  
tune2fs -o journal_data_writeback /dev/sdb1
tune2fs -O ^has_journal /dev/sdb1

tune2fs -o journal_data_writeback /dev/sdc1
tune2fs -O ^has_journal /dev/sdc1

 
tune2fs -o journal_data_writeback /dev/sdd1
tune2fs -O ^has_journal /dev/sdd1


tune2fs -O ^has_journal /dev/sdd1



--------------------
lshw -c video
  *-display                 
       description: VGA compatible controller
       product: UHD Graphics 630 (Desktop)
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:126 memory:a0000000-a0ffffff memory:90000000-9fffffff ioport:4000(size=64) memory:c0000-dffff



------------------------
vainfo 
error: XDG_RUNTIME_DIR not set in the environment.
error: can't connect to X server!
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit


------------------------
phoronix-test-suite system-info 

  PROCESSOR:          Intel Core i7-8700 @ 4.60GHz
    Core Count:       6                                        
    Thread Count:     12                                       
    Extensions:       SSE 4.2 + AVX2 + AVX + RDRAND + FSGSBASE 
    Cache Size:       12288 KB                                 
    Microcode:        0xb4                                     
    Scaling Driver:   intel_pstate powersave                   

  GRAPHICS:           Intel UHD 630
    Frequency:        1200MHz            
    Display Driver:   modesetting 1.19.2 
    Monitor:          AV Receiver        
    Screen:           1280x720           

  MOTHERBOARD:        ASRock H310M-HDV
    BIOS Version:     P4.10                     
    Chipset:          Intel Cannon Lake PCH     
    Audio:            Realtek ALC887-VD         
    Network:          Realtek RTL8111/8168/8411 

  MEMORY:             2 x 8192 MB DDR4-2667MHz CMK16GX4M2Z3466C16

  DISK:               128GB SAMSUNG MZ7TE128
                      + 10001GB Western Digital WD100EMAZ-00
                      + 4001GB Western Digital WD4003FZEX-0
                      + 5001GB Expansion Desk
    File-System:      ext4                          
    Mount Options:    errors=remount-ro relatime rw 
    Disk Scheduler:   MQ-DEADLINE                   

  OPERATING SYSTEM:   Debian 9.9
    Kernel:           4.19.0-0.bpo.5-amd64 (x86_64)                                                                                                                                                                                                
    Desktop:          Xfce                                                                                                                                                                                                                         
    Display Server:   X Server 1.19.2                                                                                                                                                                                                              
    Compiler:         GCC 4.9.2
To receive meaningful assistance you will need to provide a full debug log.

The instructions are here... debug log (wiki)

If you are using the Basic Method, then ensure the following is applied...
1.Enable debugging in Settings>System Settings>Logging,
2.Restart Kodi
3.Replicate the problem.
4.Upload the log to Kodi Paste Site manually or use the Kodi Logfile Uploader. (wiki) With either method post the link to the log back here.

If you are using the Advanced Method ensure you have correctly created and applied the advancedsettings.xml file (wiki)

In both instances, you should see the word DEBUG throughout the log.

Note: Full logs only. No partial or redacted logs
Do NOT post your logs directly into the forum. Use the Kodi Paste Site. Post the link to your pasted log in the forum
Screenshot

https://drive.google.com/file/d/1-ATm-iL...sp=sharing

Added Kodi log 

https://drive.google.com/file/d/1v_Z9YFW...sp=sharing

Not much in the kodi log besides the VA warning as far as I can tell .. it feels more like a IO issue as the entire system is completely unresponsive when it triggers. I assume by the screenshot that (SW) is software rendering I think I had it working before I messed with it using HW rendering or the CPU load was SUPER low during SW playback...
On a google share, in a zipped tar file...?! It's okay to simply post the log file on Kodi's own paste site. It'll be gone in some 60 days. Smile
Also, always enable debugging when having Kodi problems. It will give a more detailed output right from the start.

Code:
03:02:31.227 T:140121503595328 NOTICE: Starting Kodi (17.6 Git:Unknown). Platform: Linux x86 64-bit
03:02:31.227 T:140121503595328 NOTICE: Using Release Kodi x64 build
03:02:31.227 T:140121503595328 NOTICE: Kodi compiled Apr 6 2018 by GCC 6.3.0 for Linux x86 64-bit version 4.9.82 (264530)
03:02:31.227 T:140121503595328 NOTICE: Running on Debian GNU/Linux 9 (stretch), kernel: Linux x86 64-bit version 4.19.0-0.bpo.5-amd64
03:02:31.228 T:140121503595328 NOTICE: FFmpeg version/source: 3.3.9

Debian... has its own insights on how to package the Kodi application. Team Kodi itself prefers to use Ubuntu, and has its own PPA for it.
As to why the Intel UHD 630 isn't doing hw acceleration, that is above my paygrade. Others will have to dive into that.
thanks know the plug and said I only could upload to Meg's Max .. the problem it takes two minutes of debug logging just for it to start scrap out that's why I sent it up and put it on Google.

thanks for taking a look I'll update this post if I figure something out.... I got to get hardware acceleration working again
you might want to update kodi to the current version, 17.6 is old
(2019-07-30, 22:09)wsnipex Wrote: [ -> ]you might want to update kodi to the current version, 17.6 is old

i can't.... I'm running Debian none of guides work for some reason ... I even tried compiling from source that was straight up ridiculous...guess I'll keep this unsolved till i can manage to update. not likely anything in 18 will solve my GPU issues...I gotta get vainfo working first I think....
Then I can only suggest to open a bug with Debian