This update has been unpushed.

We do kernel builds frequently enough it's not worth rebuilding.

This update has been unpushed.

This update has been unpushed.

@whisebuddha based on your comments on IRC, your error was from building the kernel yourself. Please do not leave karma for kernels that are self built.

This update has been unpushed.

The patches to fix module signing are not in this build but the rest of the update with CVE fixes and an NFS fix seems to be okay so I'd rather push this since it's not actually a new regression. The module signing fixes will be in the 5.0.10 update which should be out Friday.

The dracut crash is interesting because based on it's not an issue with the 5.0.x kernel itself but just installing it. This is the 4.x -> 5.x bump so I don't know if there's something there or it's just an underlying dracut issue that's being exposed now.

Please file a bugzilla with the full kernel crash

This update has been unpushed.

It's really not necessary to comment on each update when the next stable version is released

Rebases are always tricky. We ran into a major blocking issue with random number generation and the updates were delayed because of figuring out how to approach that. That should be fixed now so updates should be coming at a regular cadence.

4.15.12 is out today so I'm going to push that as an update and obsolete this update. If you are having booting problems please file a bugzilla with system information. "It doesn't boot" with no information makes it difficult to narrow down the problem when many people do seem to be able to boot successfully.

Can those who are having problems file a bugzilla with system details? Please also confirm if warm vs. cold boot makes a difference (It works for me but I also did a cold boot).

Yeah 4.15.9 failed for F26 due to a build hiccup and I decided not to rebuilt because I knew 4.15.9 was coming out. Since this update does have the karma I'm going to go ahead and push it.

can you file a bug for the not-booting or link me to it if you already filed it? There weren't that many changes so bisection is going to be your best bet.

There's never a perfect time to push updates. The longer we wait to rebase, the more bugs we're likely to find that are actually solved by "just update to 4.15". The test day is still valuable for finding and reporting bugs.

@nucleo can you file a bugzilla with logs?

perf and other userspace packages were split out into a separate repository. An update has been filed for that as well (see