This bug was fixed in the package linux - 3.19.0-20.20
---
linux (3.19.0-20.20) vivid; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1459957
* Revert "SAUCE: Call i915_bpo specific functions from the hda driver"
- LP: #1457369
linux (3.19.0-19.19) vivid;
This bug was fixed in the package linux - 3.19.0-20.20
---
linux (3.19.0-20.20) vivid; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1459957
* Revert "SAUCE: Call i915_bpo specific functions from the hda driver"
- LP: #1457369
linux (3.19.0-19.19) vivid;
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating eit
Thank you for bringing this to our attention, Florian. I will follow up
on this issue (both for vivid update to 3.19.7 and utopic update to
3.16.7-ckt11, bug #1454202). The commit that introduced the issue was
upstream 47d68979cc96 ("md/raid0: fix bug with chunksize not a power of
2.").
Unfortun
This kernel (3.19.7), as well as the SRU-proposed 3.19.8, is also
affected by the ext+raid0+trim "chunksize not a power of 2
patch"-regression that causes severe data loss. So I certainly don't
want this patch to land on my trusty system with -lts-vivid kernel. :)
https://lkml.org/lkml/2015/5/21/1
** Changed in: linux (Ubuntu Vivid)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454699
Title:
Vivid update to 3.19.7 stable release
To manage notifications ab
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
