openSUSE Kernel September 2014

kernel@lists.opensuse.org

20 participants
14 discussions

[opensuse-kernel] RichACL patches in Factory
by Jan Kara 11 Oct '14

11 Oct '14

Hello, one openSUSE user has found out (bug 892834) RichACL kernel patches present in Factory aren't working. Since these patches are out of tree, support only ext4, are effectively disabled (due to a bug) since 13.1, and it's uncertain when / if ever they get upstream I (and Jeff Mahoney) want to drop these patches from Factory kernel. I'm sending this as a heads up and a chance for someone to convince us he really needs those... Honza -- Jan Kara <jack(a)suse.cz> SUSE Labs, CR -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 3

[opensuse-kernel] [PATCH] config: armv7hl/default: Compile KGDB serial console into kernel
by Matwey V. Kornilov 02 Oct '14

02 Oct '14

From: "Matwey V. Kornilov" <matwey.kornilov(a)gmail.com> A serial console is the major communication for ARM devices. Having CONFIG_KGDB_SERIAL_CONSOLE=m makes it impossible to debug the kernel at early boot stages. Signed-off-by: Matwey V. Kornilov <matwey.kornilov(a)gmail.com> --- config/armv7hl/default | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/armv7hl/default b/config/armv7hl/default index 3aa6e82..fffe803 100644 --- a/config/armv7hl/default +++ b/config/armv7hl/default @@ -7091,7 +7091,7 @@ CONFIG_BUILD_DOCSRC=y # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y CONFIG_KGDB=y -CONFIG_KGDB_SERIAL_CONSOLE=m +CONFIG_KGDB_SERIAL_CONSOLE=y # CONFIG_KGDB_TESTS is not set CONFIG_KGDB_KDB=y CONFIG_KDB_KEYBOARD=y -- 1.8.1.4 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 3

[opensuse-kernel] first attempt at Evergreen 13.1 kernel
by Michal Kubecek 26 Sep '14

26 Sep '14

Hello, 13.1 is still going to be supported for quite some time before it goes into the Evergreen phase but I believe the kernel switch deserves some time for testing. Thus I prepared a (SLE12 based) 3.12 kernel for Evergreen in a similar way to the (SLE11-SP2 based) 3.0 kernel used in Evergreen 11.4. So far it's almost untested except that it builds and booted and has been running on one machine for 11 hours. Everyone adventurous enough is welcome to help with testing. The packages are available in home:mkubecek:evergreen-13.1 OBS project, repository URL (for zypper) is http://download.opensuse.org/repositories/home:/mkubecek:/evergreen-13.1/op… The project and its repository also contain other packages providing kernel modules. The only exception is i586 build of xen package as the kernel doesn't provide 32-bit hypervisor; hopefully it's not going to be a big problem. Diff of the configurations is attached (left column is standard 13.1 kernel, right column the evergreen one). Except the missing i586 hypervisor code, the only potential problem is the change of CONFIG_XEN_INTERFACE_VERSION, I'm going to look more into that. I still have to check the full list of available modules. Michal Kubeček

4 9

[opensuse-kernel] Announce: bugzilla.opensuse.org
by Jeff Mahoney 22 Sep '14

22 Sep '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - Over the weekend, the shared Attachmate Group Bugzilla instance got a substantial upgrade from v3.3 to v4.4. Apart from a completely new look and an expanded interface, the updated instance now has multiple skins. So, https://bugzilla.opensuse.org/ now exists! (So does https://bugzilla.suse.com) Previous users of our Bugzilla will want to read the Bugzilla update slide deck[1] because some user visible interfaces have changed, especially surrounding the use of NEEDINFO (now a flag) and the lifecycle of a bug report. - -Jeff [1] http://bugzilla.opensuse.org/docs/Bugzilla3x-to-4x-UpgradeTransition.pdf - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) iQIcBAEBAgAGBQJUIFbiAAoJEB57S2MheeWytZkQAK1ahkpUMsdZu8Ngp8Pr40PG xp80uYKNIcqDZ4L1toOais3gVto9/Bm+OmGEvVJx86gFrLX1lVk8X5UfyQFvgqDx awDBDumeLDDoFJR8EJrL+qmXDrDCj42h8exNxEt83nYjA8lz37kt7+Lfun8pjPKS TfbJpo3arJe79rKdfwH+XSZyiUgCcbjoauTPE7i6HFP0LIPXx2hSYP43xfFgmMfA vVugzuZf/zh4q4D78hlV5RKgtU3Mp6hc4WXw4FanTaGUcWbuveiEEq5f2nxU7t25 DeWWUC+wybXmvX4oZNbufH2weueSqRKUMw8ZoEzOtFV/UpbUl5GzyvsWgMXpmYRW muUXPpZnXmLCPm5MvB76XLC96NSK0u/JN8P5DoaRe96S68aDjT4Io4gDCvJjbWhV anpbrMMCUYrrkr9DdggFnwVL09b/mLD/T7Snd40co5uOLz/Wqa9fYmXWZCOPSin8 CchSqg/R8X+IXvkRv/2ONOAUb8+a3nJ2BZJcbz4J2ezcX5Ue8fUg3kC+P6b/TNAD syXMTjBv11ZaMxwVKiSDHdAz5w4vaoBuJVN8pTxNHV198CCNbeEWU6MqCM2I7PiT Eo/m5T5+OfkLJuBgBw8Y5nYd8niF/zgjNZT+bAxpw+NvJGynRBgxA/qdLAL4rugJ kI8NWH/rWil3Y1KagASL =gC8J -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0

[opensuse-kernel] Fwd: [PATCH] patches for fixing various master issues
by Dirk Müller 22 Sep '14

22 Sep '14

Hi, please apply to master... TIA, Dirk

1 0

[opensuse-kernel] [PATCH] config: armv7hl/default: Disable CONFIG_USB_MUSB_TUSB6010
by matwey.kornilov＠gmail.com 19 Sep '14

19 Sep '14

From: "Matwey V. Kornilov" <matwey.kornilov(a)gmail.com> TUSB6010 is not used by any of our JeOSes*, but introduces issues with USB at BeagleBone. The way to resolve the issues is currently unknown, so we temporarily disable it. See for details: http://marc.info/?l=linux-usb&m=141088564307331&w=2 Cc: Guillaume Gardet <guillaume.gardet(a)free.fr> Signed-off-by: Matwey V. Kornilov <matwey.kornilov(a)gmail.com> --- * If you know JeOS which uses tusb6010 module, please inform config/armv7hl/default | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/armv7hl/default b/config/armv7hl/default index 379bcde..a957a9f 100644 --- a/config/armv7hl/default +++ b/config/armv7hl/default @@ -5509,7 +5509,7 @@ CONFIG_USB_MUSB_HDRC=m # CONFIG_USB_MUSB_HOST is not set # CONFIG_USB_MUSB_GADGET is not set CONFIG_USB_MUSB_DUAL_ROLE=y -CONFIG_USB_MUSB_TUSB6010=m +# CONFIG_USB_MUSB_TUSB6010 is not set CONFIG_USB_MUSB_OMAP2PLUS=m CONFIG_USB_MUSB_AM35X=m CONFIG_USB_MUSB_DSPS=m -- 1.8.1.4 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0

[opensuse-kernel] Re: [PATCH] patches for fixing various master issues
by Dirk Müller 17 Sep '14

17 Sep '14

2014-09-06 10:45 GMT+02:00 Dirk Müller <dirk(a)dmllr.de>: > Hi, > > please apply to master... Hi, ping......... > > TIA, > Dirk > > > -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 2

[opensuse-kernel] Keep 3.11.y kernel for openSUSE 13.1 updates?
by Takashi Iwai 12 Sep '14

12 Sep '14

Hi, Since 3.11.y maintenance was discontinued by Greg, Ubuntu took over it. It made me wonder: are we willing to continue 3.11.y for openSUSE 13.1 updates, just relying on Ubuntu? Or, can we just move on 3.12.y? Takashi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

27 80

[opensuse-kernel] Factory -> Rolling releases: What does it mean for the kernel package?
by Jeff Mahoney 11 Sep '14

11 Sep '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks - The openSUSE team recently announced[1] that openSUSE Factory is moving to a rolling development model, similar to how Tumbleweed has functioned for some time. I think this will do wonders for the stability of Factory and hopefully make it interesting again for those of us who used to sync nightly and zypper dup first thing every morning. It does bring a few questions with it, though. How do we handle the kernel with a rolling release? Having multiple outstanding versions isn't an issue unique to the kernel, but few other projects are as large and have as much churn between releases. The folks trying to support the kernel as best we can are short on time as it is, so I'm concerned about establishing parameters for which bug reports will be considered valid[2]. I'd like to define what those are so that anyone going through bug reports (even someone not actively involved in kernel development or maintenance) and see which ones can be closed or, at least, put on hold until they've been reproduced with the latest version. 1) How do we handle releases of the Factory kernel? 2) What releases will be considered "supported" simultaneously? For 1), I propose we make it official that Kernel:stable is now the external repository for openSUSE Factory. Even though Factory has already been pulling from Kernel:stable, making it an official thing means that security fixes and other backports are actively added to it rather than it being Jiri's side project. Factory would only contain point releases moving forward and release candidates would be confined to Kernel:HEAD. As a result of the change, I'd start adding -rc1 updates to Kernel:HEAD rather than waiting until -rc2 as I have in the past. It also means that there would no longer be a delay for things like Xen and ARM in Factory. As for 2), I'd like to hear suggestions. With only so much time to devote to supporting the Factory kernel, we'll need to find a balance between convenience for users and bugs actually getting fixed. We have options between supporting every release (which I would actively fight) and dropping support for any previous kernel as soon as a new one is added to the repository. I've added some interested parties to the CC list, but I'd like to hear from anyone with an opinion. Related to 2, I'd like to put more effort into trimming down the number of patches we carry in the openSUSE kernel. Over the years, we've done a pretty good job of that (compare the number of patches in a SLES release vs openSUSE), but we can do more. SUSE has already hired several engineers to work on getting our divergent Xen implementation into something that is mergeable upstream. Once that happens, the openSUSE kernel patchset should only contain security/stability backports. - -Jeff [1] https://news.opensuse.org/2014/07/29/factory-rolling-release/#more-18251 [2] I'll be the first to admit we're open to criticism in how fast openSUSE bugs are handled already - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) iQIcBAEBAgAGBQJT2lNmAAoJEB57S2MheeWyBw0P/iwhsLnc9IECJ3dGc6DylTEN M3DCvT5LsWajXZ1PrKpByww4ZeMKCiYKf7Y4Jo6Jd864ipZ5mFGviCkm5x9Q7sI+ 5qX9izy742kdlgQyFM3v+AYqtz+CVlzKwcHa1GTjLq5nOycxr6G6UWw6StD3FVoy r/a1wQUzRj0Y/ypwqtF0F4Mifbt+JATHutDJsfSmbyJlhB8nF+nYCTQKrmDV9zVZ Qekm5zzns4OwG3cL82vp5x1Mj8gr86/TwiO/DY3D7U/Dcv8m7izRLSSpRHkkuKtL VutxMXgbrZ5ga2c8ocatTj1e2Ntw1c8sLCzKJ6ubuXXCBQJ4z3eXQayliHiXExBJ yfThxnK49rD7CNEL6LhKdAaiJFEwudopmy2gEClOQV9xrFhrCBUuM5Ml7VBD2xTD d8k73OgxzpXA3UCwc7omR4DS1I1QfyxQaPRfXFi8kdywWe6gNmkmITst7gAdyjmi XjOM0O9jqBgi6TcXsxF+RiS2vxtR330aZty7VrlCu4+n4jzD4fk0FXL7u7pNmW2D n9/m33yq9cyxUeS3+ERq5hCojztTaqrs9sky1+BwdHeonCBAkpwvCKyoO8FhnM4k fZpF7eVNYBL8TZfhJ4YBXw/TRvWjqataI7RfzLdpiYxuBiluhuRBFJxs5d0t9Na1 vJpQbJP6jRTsuJnA7Zk1 =+cb1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

11 30

[opensuse-kernel] [PATCH] config: armv7hl/default: Disable DMA for MUSB
by Matwey V. Kornilov 10 Sep '14

10 Sep '14

From: "Matwey V. Kornilov" <matwey.kornilov(a)gmail.com> Hi, this is both for stable and master. An issue is the following. We can not have multiple DMA modes in the same kernel due to current musb design. So, it will work only for specific hardware (OMAP DMA). Current configuration leads to OOPS at BeaglBone Black (CPI41 DMA which is disabled), because it tries to use wrong DMA functions (from OMAP DMA). The fairest way to fix it is to disable DMA for all hardware until fix in upstream. Signed-off-by: Matwey V. Kornilov <matwey.kornilov(a)gmail.com> --- config/armv7hl/default | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config/armv7hl/default b/config/armv7hl/default index 71ae044..423b2cb 100644 --- a/config/armv7hl/default +++ b/config/armv7hl/default @@ -5534,8 +5534,8 @@ CONFIG_USB_MUSB_AM335X_CHILD=m # CONFIG_USB_UX500_DMA is not set # CONFIG_USB_INVENTRA_DMA is not set # CONFIG_USB_TI_CPPI41_DMA is not set -CONFIG_USB_TUSB_OMAP_DMA=y -# CONFIG_MUSB_PIO_ONLY is not set +# CONFIG_USB_TUSB_OMAP_DMA is not set +CONFIG_MUSB_PIO_ONLY=y CONFIG_USB_DWC3=m # CONFIG_USB_DWC3_HOST is not set # CONFIG_USB_DWC3_GADGET is not set -- 1.8.1.4 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 2

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openSUSE Kernel September 2014