[Bug 99737] [PATCH] Fix_stuck_on_bsd_ring for Clarkdale/Ironlake and kernel 4.4.x

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=99737

--- Comment #4 from Jani Nikula <jani.nikula at intel.com> ---
This bugzilla is about bugs that are unresolved in our current upstream kernel
tree. I'll take your word for how long it took to fix the bug, it certainly
seems it took too long, but as I understand it, it's fixed now.

The stable kernels (with the three level version numbers x.y.z) are based on
released upstream kernels (x.y) with backports of fixes from later kernels. How
big the .z is merely the number of times a batch of fixes has been backported
to the stable kernel. It's not a measure of quality or how much development
effort has been put to it.

The fixes to be backported to stable kernels must adhere to a pretty strict set
of rules [1]. For example, the fix must exist in a later upstream kernel, and
it cannot be bigger than 100 lines, with context. Your proposed fix is 500+
lines, and as such won't be considered. (And we don't maintain the stable
kernels or backports.)

The kernel is a fast moving target, and from upstream perspective v4.4 is old.
Just in drm/i915 the diffstat since then is 211 files changed, 103334
insertions(+), 48260 deletions(-). It's not trivial to assess the validity of a
backport across such a diff.

I can only recommend to consider upgrading to a more recent kernel release (and
that does not mean a more recent stable .z release of an old kernel).

[1] https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170403/144b313d/attachment.html>