jwboyer (jwboyer) wrote,

Fedora 19 Kernel Testing

I have a sekret. I know what kernel version is going to be used for the Fedora 19 release. Want to know? Well, I'll be glad to tell you. Why would I tell you? Because we need your help! (Aside from the fact that Fedora doesn't really have secrets and stuff.)

So looking into the kernel release crystal ball and comparing it with the Fedora 19 schedule, we're pretty much settled on using the 3.9 kernel as the release kernel. Fedora 19 (at the moment) is schedule to ship at the end of June, and we'll still be in the middle of the -rc timeframe for 3.10 kernel at that point. While shipping with a non-released kernel sounds like fun for entirely inappropriate reasons, it's not something we're going to do. Even if F19 slips by a month, we'd be hard pressed to really get another kernel rebase in place in that timeframe. Just doesn't make sense. So we'll ship with whatever is the latest stable 3.9.y kernel at that point.

Now you might be wondering why I'm already saying we need help if we're talking about using a 3.9 kernel three months from now. Basically, we need your help finding the bugs in the 3.9 kernel NOW, not after it's already been released. With 3.9-rc3 being released over the weekend, things are getting fairly stable. However they aren't perfect and, like all -rc releases, the testing base is likely pretty limited in terms of hardware. So we need to get it tested as widely as we can and get as many bugs reported now as possible. The upstream kernel maintainers are much more likely to be able to look into issues reported while the kernel is still fresh in their collective memories.

Convinced? Great! Here's how you can help. Simply run the F19 kernels on your machine and report any and all issues in bugzilla. We don't care if this results in an onslaught of bugs. We want them reported and we can deal with any duplicates, etc as we go. What's another couple hundred when you already have more than 1000 to deal with.

Some of you are going to be running F19 Alpha or are already running the Branched repos now. That's great, and it is really the best way to help the F19 release overall. Others of you aren't quite ready to dive into an adventure like that across the whole package set, and are still running on Fedora 18. That's OK, the great news is that if you want to still help with just the kernel, you can run the F19 kernels on top of Fedora 18 without issue. There are two ways to do this. The first is to grab the F19 kernels from either koji or the Branched repo and install them manually with yum. That will get you the kernels as we build them, including the debug option enabled kernels. The second way to get them is to use the Nodebug kernels that Justin builds. Add that repository and update and you should be good to go without the overhead of the kernel debug options.

We really want Fedora 19 to be as solid as possible for as many people as possible. The Fedora kernel team does testing on the variety of hardware we have at hand, but it is a very small subset of what people run and to be perfectly honest it is rather "boring" hardware. We just don't see a lot of the issues that get reported on the hardware we have. So, come help make Fedora 19 great. We'll really appreciate it if you do.
Tags: fedora

  • Flock Krakow 2016

    The annual Fedora contributor's conference, Flock to Fedora, wrapped up last week. From everything I've seen and heard, it was a smashing success.…

  • Time for an Alternative

    I've been doing kernel development or maintenance for a large portion of my professional career. It started at my previous employer and continued for…

  • When is a kernel bug not a kernel bug?

    Think of this scenario: You're sitting at your shiny Fedora install and notice a kernel update is available. You get all excited, update it through…

  • Post a new comment


    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.