kernel March 2016

kernel@lists.fedoraproject.org

10 participants
7 discussions

4.5.0 for Fedora 24?
by Chris Murphy 30 Mar '16

30 Mar '16

Hi, There's no Fedora 24 kernel in Bodhi right now. Composes are being created with 4.5.0-0.rc7.git0.2.fc24.x86_64 still, where koji has 4.5.0 for some time. Is this intentional? Thanks, -- Chris Murphy

2 3

Build break: "Upstream fix for stmmac driver regressions (AllWinner Gb NICs) until it lands upstream"
by Josh Boyer 20 Mar '16

20 Mar '16

On Sat, Mar 19, 2016 at 8:03 AM, <notifications(a)fedoraproject.org> wrote: > From bf70cee80d99f5d7adb0e346fba06b006e080062 Mon Sep 17 00:00:00 2001 > From: Peter Robinson <pbrobinson(a)gmail.com> > Date: Sat, 19 Mar 2016 12:01:49 +0000 > Subject: Upstream fix for stmmac driver regressions (AllWinner Gb NICs) until > it lands upstream > > --- > kernel.spec | 7 +- > ...t-stmmac-Fix-eth0-No-PHY-found-regression.patch | 87 ++++++++ > stmmac-fix-MDIO-settings.patch | 235 +++++++++++++++++++++ > 3 files changed, 328 insertions(+), 1 deletion(-) > create mode 100644 revert-stmmac-Fix-eth0-No-PHY-found-regression.patch > create mode 100644 stmmac-fix-MDIO-settings.patch These break the build on rc0.git13.1, which is the networking tree merge. I've commented them out in the kernel spec so they don't get applied but I have not removed them from git. The build error is below: drivers/net/ethernet/stmicro/stmmac/stmmac_main.c: In function 'stmmac_init_phy': drivers/net/ethernet/stmicro/stmmac/stmmac_main.c:869:16: error: 'struct plat_stmmacenet_data' has no member named 'phy_bus_name'; did you mean 'phy_node'? if (priv->plat->phy_bus_name) ^~ drivers/net/ethernet/stmicro/stmmac/stmmac_main.c:870:25: error: 'struct plat_stmmacenet_data' has no member named 'phy_bus_name'; did you mean 'phy_node'? if (!strcmp(priv->plat->phy_bus_name, "fixed")) ^~ scripts/Makefile.build:258: recipe for target 'drivers/net/ethernet/stmicro/stmmac/stmmac_main.o' failed make[5]: *** [drivers/net/ethernet/stmicro/stmmac/stmmac_main.o] Error 1 josh

2 2

Kernel plans for Fedora 24
by Justin Forbes 16 Mar '16

16 Mar '16

With the 4.5 kernel out and the merge window for 4.6 opened up, we had to make a decision on what the release kernel for F24 would be. The decision has been made to ship F24 with the 4.5 kernel with 4.6 available as an update once it is ready. Timing wise, 4.6 *should* release just before the final freeze for F24, but that is cutting it insanely close. Should Fedora move on as scheduled, and 4.6 have some delay due to a bug that impacts users, that would be unfortunate. This means we have a good bit of time to make sure that everything is working as intended with 4.5 in Fedora. It also means that any installer critical fixes will need to be backported to 4.5. Thanks, Justin

1 0

where are patches?
by Chris Murphy 13 Mar '16

13 Mar '16

I'm running kernel-4.5.0-0.rc7.git0.1.fc24.x86_64 and running into seemingly cosmetic warning bug with a Btrfs mount option. Upstream is asking me to build a mainline kernel myself and I'm being resistant because Fedora carries so few patches in its mainline builds. I go here: http://koji.fedoraproject.org/koji/rpminfo?rpmID=7476227 There's a list of patches, but if I click on any of them, it's something of a dead end because it doesn't actually show me the patch contents. Do I really have to download the RPM and unpack it just to see the patch contents? It's like the trail of breadcrumbs is crossing a river... Thanks, -- Chris Murphy

2 1

Consider Merging: sign kernel modules on all archs in Fedora
by Thorsten Leemhuis 08 Mar '16

08 Mar '16

Hi Justin! Please consider merging the two patches I'll send as reply to this mail. They are basically a rebase of the patches I send two months ago: http://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org… To quote myself: > On 10.12.2015 20:59, Josh Boyer wrote(¹): >> > […] >> > Thinking about it some, there isn't really a reason CONFIG_MODULE_SIG >> > couldn't be enabled on other architectures. Signed modules are >> > independent of UEFI secure boot support. If we did that, we might >> > want to come up with something that maps arches which have it enabled >> > to a single RPM macro. >> > >> > Anyway, that's likely future work. > > Find attached two patches to go down that route. > > The first creates a new macro in the spec file to make "signing modules" > and "signing kernels for UEFI secure boot" independent from each other. > This is pretty straightforward and could be applied as is, as afterwards > it if more obvious what happens. I fired a scratch build to verify > mod-sign and pesign are still called just like before on %{ix86} x86_64. > Results can be found via > http://koji.fedoraproject.org/koji/taskinfo?taskID=12376294 The arm > build log shows that mod-sign and pesign are still not called. > > The second patch enables module signing for all archs. Scratch builds > for primary archs: > http://koji.fedoraproject.org/koji/taskinfo?taskID=12376883 > Scratch build for ppc: > http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=3033583 > I for now didn't run any of those kernels to verify if things still work > as I'm unsure what we want to do (hence the RFC in the Subject): On > which archs do we want to enable module signing? Are there any reasons > to not enable it on some archs? Is the overhead considered to big for > armv7? Does it work everywhere? Peter on IRC said the overhead for armv7 is no problem from is point of view and Josh seems to be fine with the whole idea as well. Here is a fresh scratch build to show that the stuff still builds on x86-32, x86-64 and armv7: http://koji.fedoraproject.org/koji/taskinfo?taskID=13251682 CU, knurd

2 3

Disabling early microcode, because kernel does not support it. CONFIG_MICROCODE_[AMD|INTEL]_EARLY!=y
by Reindl Harald 07 Mar '16

07 Mar '16

"Disabling early microcode, because kernel does not support it. CONFIG_MICROCODE_[AMD|INTEL]_EARLY!=y" seems to be back with all 4.4 kernels, i remember that message due update was fixed in the past

5 7

[PATCH] Enable VIDEO_GO7007 as module
by Nicolas Chauvet 02 Mar '16

02 Mar '16

This driver can be used in some usb encoder devices. http://www.linuxtv.org/wiki/index.php/Go7007 The related firmware files are in linux-firmware for some time. The driver has left staging since few release, but I'm fine if this is enabled in linux kernel 4.5 and later. --- config-generic | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/config-generic b/config-generic index 9eef876..1cfcfab 100644 --- a/config-generic +++ b/config-generic @@ -3410,6 +3410,10 @@ CONFIG_VIDEO_CX231XX=m CONFIG_VIDEO_CX231XX_ALSA=m CONFIG_VIDEO_CX231XX_DVB=m CONFIG_VIDEO_CX231XX_RC=y +CONFIG_VIDEO_GO7007=m +CONFIG_VIDEO_GO7007_USB=m +CONFIG_VIDEO_GO7007_LOADER=m +CONFIG_VIDEO_GO7007_USB_S2250_BOARD=m CONFIG_VIDEO_HEXIUM_ORION=m CONFIG_VIDEO_HEXIUM_GEMINI=m CONFIG_VIDEO_IVTV=m @@ -3422,6 +3426,7 @@ CONFIG_VIDEO_SAA6588=m CONFIG_VIDEO_SAA7134=m CONFIG_VIDEO_SAA7134_ALSA=m CONFIG_VIDEO_SAA7134_DVB=m +CONFIG_VIDEO_SAA7134_GO7007=m CONFIG_VIDEO_SAA7134_RC=y CONFIG_VIDEO_SOLO6X10=m CONFIG_VIDEO_USBVISION=m @@ -5560,7 +5565,6 @@ CONFIG_STAGING_MEDIA=y # CONFIG_VIDEO_DT3155 is not set # CONFIG_TI_ST is not set # CONFIG_FB_XGI is not set -# CONFIG_VIDEO_GO7007 is not set # CONFIG_I2C_BCM2048 is not set # CONFIG_DT3155 is not set # CONFIG_PRISM2_USB is not set -- 1.7.2.1

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel March 2016