I really don't understand what's going on here. It's been another 6 days now. There has been another (broken) kernel update for xenial (4.4.0-43) which did not include this fix, and which also did not go through -proposed. Instead xenial-proposed is still at at 4.4.0-41, which is broken as well.
Two "stable" kernel updates with a known regression and a simple fix.
How is this possible?
And how does this fit with xenial being an LTS-Release?
This really ain't funny any more!
For now I have build the packages with the fix applied for amd64 and I'll try to keep up with new broken kernels. In case anybody else needs them:
I really don't understand what's going on here. It's been another 6 days now. There has been another (broken) kernel update for xenial (4.4.0-43) which did not include this fix, and which also did not go through -proposed. Instead xenial-proposed is still at at 4.4.0-41, which is broken as well.
Two "stable" kernel updates with a known regression and a simple fix.
How is this possible?
And how does this fit with xenial being an LTS-Release?
This really ain't funny any more!
For now I have build the packages with the fix applied for amd64 and I'll try to keep up with new broken kernels. In case anybody else needs them:
sudo apt-key adv --keyserver keyserver. ubuntu. com --recv-keys 89C9B5AE ubuntu. repo.uni- hannover. de/ubuntu xenial pub' ubuntu. repo.uni- hannover. de/ubuntu/ luh-deb- repo.gpg. key
sudo apt-add-repository -u 'http://
Or get the key from here: http://
Regards, Robert