Hello. Happy New Year everyone. :)
I have a doubt: I started testing these kernels and one of'em has the following message in dmesg (shell command was 'dmesg | grep -i i915'): [ 11.547334] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) I understand that this isn't a bug (it seems that snd_hda_intel was bound to the audio component of i915 and that's it), but since I'm not 100% sure about what this message actually means it doesn't hurt to ask. Any consideration to be taken into account here? Anyway, so far I've tested the following kernels and got the following outputs from 'dmesg |grep -i i915': 1) v4.1.6-unstable: [ 1.195451] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0 [ 2.311613] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 2.311614] i915 0000:00:02.0: registered panic notifier [ 8.605191] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Because I am assuming that "snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])" isn't a bug, I considered that the bug reported in this ticket is fixed in kernel version "v4.1.6-unstable", hence I decided to test a previous (older) kernel version: v4.0.6-wily. 2) v4.0.6-wily: [ 1.243539] [drm] Initialized i915 1.6.0 20150130 for 0000:00:02.0 on minor 0 [ 2.316114] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 2.316115] i915 0000:00:02.0: registered panic notifier [ 7.558016] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 34.302400] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun I considered that FIFO underrun a bug, hence I then decided to test a newer kernel version: v4.1-rc7-unstable. 3) v4.1-rc7-unstable: [ 1.194191] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0 [ 2.324857] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 2.324858] i915 0000:00:02.0: registered panic notifier [ 5.989937] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 26.618897] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Same FIFO underrun issue, thus I then tested a newer kernel version: v4.1.2-unstable. 4) v4.1.2-unstable: [ 1.188288] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0 [ 2.296468] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 2.296469] i915 0000:00:02.0: registered panic notifier [ 7.502745] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Assuming that "snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])" isn't a bug, I considered the bug fixed in kernel version v4.1.2-unstable, and thus decided to test a previous (older) kernel version: v4.1-wily. 5) v4.1-wily: [ 1.176185] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0 [ 2.292596] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 2.292597] i915 0000:00:02.0: registered panic notifier [ 11.547334] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Again, since I'm assuming that "snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])" isn't a bug, I'm considering that the vug is fixed in kernel version v4.1-wily. Is it ok so far? If it is, I am very close to finding out in which kernel version the bug fix was commited. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520040 Title: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
