• 1
  • 106
  • 107
  • 108(current)
  • 109
  • 110
  • 342
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
(2015-10-11, 19:15)fritsch Wrote: Use team kodi ppa instead of fernetmenta. Pvr addons are packacked by wsnipex for this howto here, so they actually are compatible.

Ahh. I didn't notice that. I installed Janbars PPA to install the kodi-pvr-mythtv-isengard package. I will try removing it, and testing what is in wsnipex PPA instead

edit

The kodi-pvr-mythtv plugin packaged by wsnipex works beautifully. Thanks for pointing that out.
Livingroom: 65" Panasonic Plasma, Denon AVR-x3300w, Parasound A31, Fronts: RBH SX-6300 Towers, Center: RBH 441-se, Surrounds: RBH 41-se Sub: Dual SVS PC13-Ultra, Source: Custom Kodi Box
Desk: DAC: Schiit Modi Multibit,Headphones: Schiit Jotunheim -> Sennheiser HD650 & Beyerdynamic DT770 Pro, Speakers: Parasound 275v2-> RBH 41-se & SVS SB12-NSD
Reply
(2015-10-11, 11:09)fritsch Wrote: I don't plan to provide patched kernels for ubuntu. As said - this thread is about testing VAAPI features - providing a kernel and keeping it up2date is a lot of maintainance. Those that don't use OpenELEC can do that easily byself - as the kernel patch was pushed on my github:

Code:
git clone https://github.com/fritsch/linux.git
cd linux
git checkout v4.3-rc4-passthrough
cp /boot/config-`uname -r` .config
make oldconfig (Press return until finished)
sudo apt-get install fakeroot kernel-package
make-kpkg --append-to-version "-passthrough" -j4 --initrd linux-headers linux-image
done
In my case make-kpkg needs sudo. Anyway thanks for this - now i've 4.3-rc4 with pass-though :-)
Reply
(2015-10-11, 19:41)BigL-New Wrote:
(2015-10-11, 11:09)fritsch Wrote: I don't plan to provide patched kernels for ubuntu. As said - this thread is about testing VAAPI features - providing a kernel and keeping it up2date is a lot of maintainance. Those that don't use OpenELEC can do that easily byself - as the kernel patch was pushed on my github:

Code:
git clone https://github.com/fritsch/linux.git
cd linux
git checkout v4.3-rc4-passthrough
cp /boot/config-`uname -r` .config
make oldconfig (Press return until finished)
sudo apt-get install fakeroot kernel-package
make-kpkg --append-to-version "-passthrough" -j4 --initrd linux-headers linux-image
done
In my case make-kpkg needs sudo. Anyway thanks for this - now i've 4.3-rc4 with pass-though :-)
Use fakeroot instead of sudo, please. I typed that out of head .... and forgot that.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2015-10-10, 10:47)fritsch Wrote: Limited Range just replaces the shader. It's even less it uses the same shader but with other coefficients.

As you run the old nightmare sandybridge based Celeron 847 which gets hot like hell - check the temperatures, please.

Temperatures seem fine. After a 2hr 1080p movie with ac3 decoded to pcm it runs at 75C. Not cool, but not too hot as well. The debug log I uploaded was right after boot, it runs at 60C then.

Although I said I had it only happen with limited, it happens on full as well. Not sure how I managed to run a couple of days on full without any crash. It happens as easily as on limited now.

It seems the guy fps is related, when running on 24hz it crashes all the time. Even before a frame of video has been displayed.

Do you want another debug log?
My XBMC / Kodi history.
XBMC for XBOX -> XBMC for Windows -> XBMC for Android -> Kodi for Android - > Kodi v16 OE (Amlogic) -> Kodi v17 LE (NUC 2x) -> Kodi v18.5 LE (NUC 2x)
Reply
Jep - and as it crashes I also want the crashlog, please - should be in the home directory. Also dmesg | pastebinit directly after the "crash" would be good.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2015-10-11, 19:45)fritsch Wrote:
(2015-10-11, 19:41)BigL-New Wrote:
(2015-10-11, 11:09)fritsch Wrote: I don't plan to provide patched kernels for ubuntu. As said - this thread is about testing VAAPI features - providing a kernel and keeping it up2date is a lot of maintainance. Those that don't use OpenELEC can do that easily byself - as the kernel patch was pushed on my github:

Code:
git clone https://github.com/fritsch/linux.git
cd linux
git checkout v4.3-rc4-passthrough
cp /boot/config-`uname -r` .config
make oldconfig (Press return until finished)
sudo apt-get install fakeroot kernel-package
make-kpkg --append-to-version "-passthrough" -j4 --initrd linux-headers linux-image
done
In my case make-kpkg needs sudo. Anyway thanks for this - now i've 4.3-rc4 with pass-though :-)
Use fakeroot instead of sudo, please. I typed that out of head .... and forgot that.

I updated the howto for rc5. If you already have build, do:
git fetch origin
git clean -xfd
git checkout -b v4.3-rc5-passthrough origin/v4.3-rc5-passthrough

And then continue with
cp /boot/config-`uname -r` .config
make oldconfig (Press return until finished)
sudo apt-get install fakeroot kernel-package
make-kpkg --append-to-version "-passthrough" -j4 --initrd linux-headers linux-image
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2015-10-11, 22:00)fritsch Wrote:
(2015-10-11, 19:45)fritsch Wrote:
(2015-10-11, 19:41)BigL-New Wrote: In my case make-kpkg needs sudo. Anyway thanks for this - now i've 4.3-rc4 with pass-though :-)
Use fakeroot instead of sudo, please. I typed that out of head .... and forgot that.

I updated the howto for rc5. If you already have build, do:
git fetch origin
git clean -xfd
git checkout -b v4.3-rc5-passthrough origin/v4.3-rc5-passthrough

And then continue with
cp /boot/config-`uname -r` .config
make oldconfig (Press return until finished)
sudo apt-get install fakeroot kernel-package
make-kpkg --append-to-version "-passthrough" -j4 --initrd linux-headers linux-image

I have completed the above commands successfully, but when I run uname –r I get the following :
root@htpc:~/linux# uname -r
4.3.0-040300rc4-generic
Reply
(2015-10-12, 15:11)jteeuw Wrote:
(2015-10-11, 22:00)fritsch Wrote:
(2015-10-11, 19:45)fritsch Wrote: Use fakeroot instead of sudo, please. I typed that out of head .... and forgot that.

I updated the howto for rc5. If you already have build, do:
git fetch origin
git clean -xfd
git checkout -b v4.3-rc5-passthrough origin/v4.3-rc5-passthrough

And then continue with
cp /boot/config-`uname -r` .config
make oldconfig (Press return until finished)
sudo apt-get install fakeroot kernel-package
make-kpkg --append-to-version "-passthrough" -j4 --initrd linux-headers linux-image

I have completed the above commands successfully, but when I run uname –r I get the following :
root@htpc:~/linux# uname -r
4.3.0-040300rc4-generic
After compiling you need to install the resulting .deb files from ../ with sudo dpkg -i
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2015-10-12, 15:15)fritsch Wrote:
(2015-10-12, 15:11)jteeuw Wrote:
(2015-10-11, 22:00)fritsch Wrote: I updated the howto for rc5. If you already have build, do:
git fetch origin
git clean -xfd
git checkout -b v4.3-rc5-passthrough origin/v4.3-rc5-passthrough

And then continue with
cp /boot/config-`uname -r` .config
make oldconfig (Press return until finished)
sudo apt-get install fakeroot kernel-package
make-kpkg --append-to-version "-passthrough" -j4 --initrd linux-headers linux-image

I have completed the above commands successfully, but when I run uname –r I get the following :
root@htpc:~/linux# uname -r
4.3.0-040300rc4-generic
After compiling you need to install the resulting .deb files from ../ with sudo dpkg -i

Thanks!
Reply
@fritsch as you wished.

dmesg: http://sprunge.us/ihRV
debug log: http://sprunge.us/DVQY
va-info: http://sprunge.us/JBTU
My XBMC / Kodi history.
XBMC for XBOX -> XBMC for Windows -> XBMC for Android -> Kodi for Android - > Kodi v16 OE (Amlogic) -> Kodi v17 LE (NUC 2x) -> Kodi v18.5 LE (NUC 2x)
Reply
Quote:[ 67.327004] [drm] GPU HANG: ecode 6:0:0x00c2c0c6, in Vaapi-Output [600], reason: Ring hung, action: reset
[ 67.327008] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 67.327011] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 67.327013] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 67.327016] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 67.327019] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 67.329119] drm/i915: Resetting chip after gpu hang
[ 93.322796] [drm] stuck on render ring
[ 93.323790] [drm] GPU HANG: ecode 6:0:0x00000ecc, in Vaapi-Output [600], reason: Ring hung, action: reset
[ 93.325902] drm/i915: Resetting chip after gpu hang
[ 105.334637] [drm] stuck on render ring
[ 105.335660] [drm] GPU HANG: ecode 6:0:0x00c2c0c6, in Vaapi-Output [617], reason: Ring hung, action: reset
[ 105.338163] drm/i915: Resetting chip after gpu hang
[ 141.330191] [drm] stuck on render ring
[ 141.331208] [drm] GPU HANG: ecode 6:0:0xfeffffff, in kodi.bin [460], reason: Ring hung, action: reset
[ 141.333386] drm/i915: Resetting chip after gpu hang
[ 163.314164] [drm] stuck on blitter ring
[ 163.316819] [drm] GPU HANG: ecode 6:2:0x00ccccc6, in Xorg [293], reason: Ring hung, action: reset
[ 163.822502] drm/i915: Resetting chip after gpu hang
[ 163.822519] [drm:i915_reset] *ERROR* Failed to reset chip: -110
-> bugs.freedesktop.org and file a new bug under DRM/Intel
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2015-10-12, 20:07)fritsch Wrote:
Quote:[ 67.327004] [drm] GPU HANG: ecode 6:0:0x00c2c0c6, in Vaapi-Output [600], reason: Ring hung, action: reset
[ 67.327008] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 67.327011] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 67.327013] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 67.327016] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 67.327019] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 67.329119] drm/i915: Resetting chip after gpu hang
[ 93.322796] [drm] stuck on render ring
[ 93.323790] [drm] GPU HANG: ecode 6:0:0x00000ecc, in Vaapi-Output [600], reason: Ring hung, action: reset
[ 93.325902] drm/i915: Resetting chip after gpu hang
[ 105.334637] [drm] stuck on render ring
[ 105.335660] [drm] GPU HANG: ecode 6:0:0x00c2c0c6, in Vaapi-Output [617], reason: Ring hung, action: reset
[ 105.338163] drm/i915: Resetting chip after gpu hang
[ 141.330191] [drm] stuck on render ring
[ 141.331208] [drm] GPU HANG: ecode 6:0:0xfeffffff, in kodi.bin [460], reason: Ring hung, action: reset
[ 141.333386] drm/i915: Resetting chip after gpu hang
[ 163.314164] [drm] stuck on blitter ring
[ 163.316819] [drm] GPU HANG: ecode 6:2:0x00ccccc6, in Xorg [293], reason: Ring hung, action: reset
[ 163.822502] drm/i915: Resetting chip after gpu hang
[ 163.822519] [drm:i915_reset] *ERROR* Failed to reset chip: -110
-> bugs.freedesktop.org and file a new bug under DRM/Intel

Any specific info I need to tell them? The GPU crash dump is 0kb, anything I can do about that?
My XBMC / Kodi history.
XBMC for XBOX -> XBMC for Windows -> XBMC for Android -> Kodi for Android - > Kodi v16 OE (Amlogic) -> Kodi v17 LE (NUC 2x) -> Kodi v18.5 LE (NUC 2x)
Reply
[ 67.327019] [drm] GPU crash dump saved to /sys/class/drm/card0/error <- bzip this error and upload it to the bugreport, also include dmesg > mydmesg.txt
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
But a 0kb gpu crash file won't be of use would it? (sorry edited my previous post, after you replied without hitting F5)
My XBMC / Kodi history.
XBMC for XBOX -> XBMC for Windows -> XBMC for Android -> Kodi for Android - > Kodi v16 OE (Amlogic) -> Kodi v17 LE (NUC 2x) -> Kodi v18.5 LE (NUC 2x)
Reply
cat /sys/class/drm/card0/error > ~/mypersonalgpuhang.txt
bzip2 ~/mypersonalgpuhang.txt
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
  • 1
  • 106
  • 107
  • 108(current)
  • 109
  • 110
  • 342

Logout Mark Read Team Forum Stats Members Help
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server18