Rebase to 4.15.3
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?
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!
Comment fields support Fedora-Flavored Markdown.
Text fields in Bodhi2 support an
version of markdown.
This is a cheat sheet for your reference.
You can do headers by underlining or by prefixing with the # character:
This is an H1
This is an H2
# This is another H1
## This is another H2
You can do blockquotes using email-style prefixes with the > character:
> This is a quotation
> over many lines
> > and it can be nested(!)
Lists work like you'd expect, by prefixing with any of the *, +, or - characters:
Check out this list:
* a list..
You need a blank line between a paragraph and the start of a list for the renderer to pick up on it.
Emphasis can be added like this:
You can save your code references from being misinterpreted as emphasis by surrounding them with backtick characters (`):
Use `the_best_function()` and _not_ that crummy one.
Links look like this:
..but we also support bare links if you just provide a URL.
You can create code blocks by indenting
every line of the block by at least 4 spaces or 1 tab.
Here is a code block:
for i in range(4):
You can reference bug reports by simply writing something of the form tracker#ticketid.
This fixes PHP#1234 and Python#2345
... we will automatically generate links to the tickets in the appropriate trackers in place.
The supported bug tracker prefixes are: (these are all case-insensitive)
And you can refer to other users by prefixing their username with the @ symbol.
This will generate a link to their profile, but it won't necessarily send them a notification unless they have a special FMN rule set up to catch it.
Lastly, you can embed inline images with syntax like this:
Is the update generally functional? (karma)
You need to be logged in to add karma!
Copyright © 2007-2018 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.