[gentoo-dev] Re: [gentoo-kernel] Dropping stable USE flags for 4.14

2017-12-30 Thread Greg KH
On Sat, Dec 30, 2017 at 03:14:45PM +0100, Greg KH wrote:
> On Fri, Dec 29, 2017 at 10:58:28PM +0900, Alice Ferrazzi wrote:
> > 
> > - Unbootable system with CONFIG_MCORE2 [6]

This turns out to be a gentoo-specific bug, not much upstream can do
about a broken compiler that some profiles are using :(

greg k-h



[gentoo-dev] Re: [gentoo-kernel] Dropping stable USE flags for 4.14

2017-12-30 Thread Greg KH
On Fri, Dec 29, 2017 at 10:58:28PM +0900, Alice Ferrazzi wrote:
> Hello,
> 
> We have recently started the stabilization of gentoo-sources-4.14.8.
> 
> Very soon we received reports regarding broken e1000e driver [1] and moved
> to gentoo-sources-4.14.8-r1.
> 
> Since then we keep receiving new problems related to 4.14.x kernel:
> 
> - IPSec is broken [2]
> 
> - Change in 4.14.9 broke nVIDIA driver [3]
> 
> - Colors on console are broken with some Radeon HD cards [4]
> 
> - BUG report on boot [5]
> 
> - Unbootable system with CONFIG_MCORE2 [6]
> 
> - ...more bugs [7]
> 
> While not all issues are present in gentoo-sources-4.14.8-r1 we are
> concerned about the current stability/quality of the 4.14.x branch in
> general and don't feel comfortable recommending 4.14.x branch for general
> use at the moment. But that's what a stable USE flag means for most
> Gentoo users.
> 
> So, for now, we have decided to drop gentoo-sources-4.14.x stable keywords.
> We will keep watching 4.14 branch and once the stability/quality matches
> our requirements we will restart stabilization.

Be careful, you don't want to drop back to older kernels with known
security issues that are already fixed in the latest 4.14.y release.

Most of the above issues have resolutions already, and yes, 4.14 is
being a bit more "temperamental", sorry, it will pay off in the end...

thanks,

greg k-h