Rebase to 4.15.3
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2018-8739091f47Please log in to add feedback.
| 0 | 0 | Test Case kernel regression |
This update has been submitted for testing by labbott.
Both default and performance kernel regression tests passed on Intel i7-4770K, 32Gig, MSI Z97M Gaming MB, using integrated graphics.
This update has been pushed to testing.
My music server (VM) works with this kernel.
How come there is a test day announced for 4.15 rebase, when kernel is pushed to stable a week before test day (F27)? Even for F26 this kernel will hit stable before the test event.
What's the purpose of a test day if every Fedora user will receive the new kernel before looking at test results/bugs...? Is the test event canceled?
Working fine
works
Mmh, I'm getting this new error message at early bootup stage (no present in 4.14.18), but without problems/errors following up:
kernel: smp: Bringing up secondary CPUs ...
kernel: x86: Booting SMP configuration:
kernel: .... node #0, CPUs: #1
kernel: do_IRQ: 1.55 No irq handler for vector <<< ERROR
kernel: smp: Brought up 1 node, 2 CPUs
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.
This update has been submitted for batched by labbott.
This update has been submitted for stable by labbott.
Tested on 4 Intel platforms: C2D 6300, i5-6600, i7-3770, and i7-6700. Regression tests "default" and "performance" pass w/o problems. Basic system operation seems normal on all platforms.
@augenauf Typically test days do happen before a rebase. In this instance due to travel schedules and the like, it did not. There is still a lot of value in the test day, as it will hopefully allow us to find bugs which might be lingering, or close out some older bugs that were fixed in 4.15. There was no reason to with hold existing fixes from users while we waited for the updated test day.
This update has been pushed to stable.
@labbott and @jforbes, thanks for the explanation!