Upgrading to wily has fixed this for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1507994
Title:
Broadwell vaapi video decode broken by i915_bpo migration
To manage notifications about this
I haven't been able to reproduce this behaviour with mpv.
I've tried all combinations of --vo=opengl / --vo=vaapi and
--hwdev=vaapi and they all display correctly.
mpv 0.8.0 (C) 2000-2015 mpv/MPlayer/mplayer2 projects
built on 2015-02-19T17:03:21
libav library versions:
libavutil
The offending upstream commit appears to be:
http://kernel.ubuntu.com/git/virgin/linux.git/commit/?id=dc9fb09cae5b1355c1a9d8102e40b97b34332f31
I still need to test this with mpv, and there's been some new mainline &
intel-drm-nightly kernels released since by last attempt.
--
You received this
Bug report posted to linux-gfx
http://lists.freedesktop.org/archives/intel-
gfx/2015-October/078660.html
I'll get started on bisecting the mainline kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Shall do.
One question: should I be using the latest mainline kernel, or the
latest drm-intel-nightly for the Kernel.org bug report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1507994
Title:
Tested http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
nightly/2015-10-17-unstable/linux-
image-4.3.0-994-generic_4.3.0-994.201510162200_amd64.deb
This kernel does not resolve the problem.
(there's two newer directories, but these only contain i386 builds)
--
You received this bug
Tested http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc6-unstable
/linux-
image-4.3.0-040300rc6-generic_4.3.0-040300rc6.201510182030_amd64.deb
Problem remains, although the first playback seems to work about half
the time, then subsequent ones fail.
I run kodi standalone with xinit, so when
vlc works with vaapi
vlc reports:
libva info: VA-API version 0.37.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_37
libva info: va_openDriver() returns 0
[7fc474c0ae78]
Public bug reported:
Since upgrading from linux-image-3.19.0-28-generic to linux-
image-3.19.0-30-generic, vaapi-accelerated video playback on Kodi 15.2
(and 15.1) is now all black.
On-screen display items (eg. elapsed time) and audio still work, but the
decoded video content is now all black.
I've previously reported this behaviour here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/comments/25
I'm reporting this as a separate bug as I now suspect the "master
control interrupt lied" message is unrelated.
--
You received this bug notification because you are a member
I'll give vlc a try when I get home tonight.
Does that mean you've been able to reproduce the kodi behaviour?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1507994
Title:
Broadwell vaapi video
I've just started getting this after updating to linux-
image-3.19.0-30-generic from linux-image-3.19.0-28-generic.
NUC 5i3RYH connected via the mini-hdmi port to a 720p tv.
100% repeatable for me using Kodi 15.1. If I play a video I get audio,
but the video is all black. If I activate the
You can boot to the previous kernel as a workaround.
As root, edit: /etc/default/grub
You should have this line in there:
GRUB_DEFAULT=0
Comment that out, and replace it with:
GRUB_DEFAULT=Advanced options for UbuntuUbuntu, with Linux
3.19.0-16-generic
The part before the '' is what you
Thanks Xiong, that fix works for me!
(Tested against 3.19.0-19.19)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Title:
kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel
To manage
Bisecting points to this commit as the culprit:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
vivid.git/commit/?id=5d81c285e3eb28c80b6cd1c2902afb1bdb9180bb
UBUNTU: SAUCE: Call i915_bpo specific functions from the hda driver
BugLink: http://bugs.launchpad.net/bugs/1449464
Make sure to
3.19.0-18.18 with git revert 5d81c285e3eb28c80b6cd1c2902afb1bdb9180bb
* patch applies cleanly
* audio works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Title:
kernel 3.19.0-18 breaks
3.19.0-19.19 still exhibits the no-audio bug.
Reverting 5d81c285e3eb28c80b6cd1c2902afb1bdb9180bb on top of
3.19.0-19.19 restores the audio.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Still plugging away on the bisect. It's taking a little longer than I
expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Title:
kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel
To
If it's any help, I'm in the process of bisecting this between tags
Ubuntu-3.19.0-16.16 and Ubuntu-3.19.0-18.18 in this repo
git://kernel.ubuntu.com/ubuntu/ubuntu-vivid.git
I'll report back any findings.
I have an i3 NUC (NUC5i3RYH) with the same issue.
--
You received this bug notification
I'll second that - thanks Alan for the great detective work.
And Joseph, thanks for building all those kernels, and most importantly,
for acting on this bug report in the first place.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks again Joseph.
Alan - I'm quite certain your patch fixes the problem for me.
I've now tried at least ten first-after-reboot recordings, and every
single one has worked. I've also tried plenty of other combinations,
including multiple simultaneous recordings, and no failures there
either.
Thanks for that Joseph, but unfortunately that kernel's been built for
amd64, and I'm on i386.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088733
Title:
Regression in dib0700 dvb-t driver
To
No recording failures so far, but see the next comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088733
Title:
Regression in dib0700 dvb-t driver
To manage notifications about this bug go
Joseph, could you please build me a kernel *without* Alan's patches?
I've been getting sporadic kernel panics during startup, and I want to
make sure these aren't related to these patches.
I'm pretty sure they're not, as I've been getting them with all the 3.8
kernels, and have always assumed
Early indications are good!
I've installed this kernel and have done a few manual tests. Three
reboots, and multiple recordings done, no failures as yet.
I'll now schedule a few days worth of wakeup-record-shutdown cycles and
see what we get.
--
You received this bug notification because you
Thanks for taking the time to look into this Alan, and for all your help
Joseph.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088733
Title:
Regression in dib0700 dvb-t driver
To manage
Here's another set of captures, using the kernel from comment #23.
There's only failed recording captures here.
Alan, let me know if you'd like me to try capturing a successful
recording.
** Attachment added: USB tracedata using kernel from comment #23
Not a problem Joseph.
With any luck I'll be able to give that a run later today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088733
Title:
Regression in dib0700 dvb-t driver
To manage
Sorry for the delay.
Attached is new tracedata with Alan's second patch.
Two failed recording runs were captured, as well as one successful run included
for comparison.
All of these runs were the first recording after a reboot.
Notably, with this diagnostic patch, approximately 50% of the
Thanks for the kernel Joseph - that's a big help.
Attached is another set of usbmon captures, as well as the dmesg output
for each session.
Unlike last time, I was not able to get a recording to work the first
time through. I'll keep trying though, and post the results if I get one
to happen.
These are the results of making recordings with mythtv, capturing the
output from /sys/kernel/debug/usb/usbmon/1u.
It is looking likely from this testing that usually only the first
recording after boot fails. Subsequent recordings succeed.
Captures of both working and failed recordings are
Happy to collect that data, but I'm on vacation right now and won't be
back until the first week of February.
Shall gather some usb tracedata when I return.
Thanks again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problem still occurs in the v3.8-rc2 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088733
Title:
Regression in dib0700 dvb-t driver
To manage notifications about this bug go to:
I can confirm that this kernel fixes the bug.
I can also confirm that the bug is present in the stock 3.2.0-35 kernel.
Thanks for looking into this Joseph!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Problem also appears in this kernel: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.7-raring/
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088733
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088733
Title:
Regression in dib0700 dvb-t driver
To manage notifications about
Public bug reported:
I have two dib0700-based dvb-t usb tuners. A Sony PlayTV dual tuner, and
an Asus U3100+ single tuner. Since the 3.2.0-32 kernel, both these
tuners have been failing to record.
The problem first appeared with the 3.2.0-32 kernel. Every kernel up to
3.2.0-31 has worked, and
37 matches
Mail list logo
