December 2015 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] Use pvops-enabled kernel for Xen (fate#315712)
by Michal Marek 20 Jan '16

20 Jan '16

Hi, you have probably noticed that the SUSE virtualization developers have been working on porting features from the kernel-source patches.xen series to the upstream Xen implementation. This mostly works nowadays, so at the SUSE Labs Conference last month, we agreed to finally get rid of kernel-xen in Factory and instead use kernel-default with CONFIG_XEN (the mainline option) enabled. I prepared a branch on github https://github.com/michal42/kernel-source stable-noxen which does exactly this. Test packages are building here: https://build.opensuse.org/project/show/home:michal-m:kernel-stable-noxen The kernel boots and works on my machine, both on bare metal and under the hypervisor (*), but there is some integration work to be done before it can be submitted to Factory: - The installer needs to cope with kernel-xen not available and choose kernel-default. Something like the attached patch should fix it (untested). - perl-Bootloader: Right now, it creates a Xen multiboot entry if the kernel is named -xen, otherwise it creates a regular linux entry. Create both entries if the Xen hypervisor is installed? - kernel-xen needs to be dropped from the patterns, but that's trivial - We have been building a kernel-obs-build-xen package for the OBS workers, which now disappears. Of course, there is lot more work to be done in making the xen -> pvops transition seamless in all corner cases. But that should not be a barrier to pushing the kernel to factory. (*) With the -default kernel, I do not see the kernel messages on the serial console with kernel /boot/xen.gz com1=115200 console=com1,vga module /boot/vmlinuz-4.2.2-0.g980fcdb-default ... console=tty0 console=ttyS0,115200 while I see them with kernel-xen. Michal

6 16

[opensuse-kernel] Please raise disk size constraints for kernel builds
by Stefan Bruens 11 Jan '16

11 Jan '16

Hi, builds of kernel packages occasionally fail due to unsufficient disk space. Happens for kernel-default,-vanilla,-... on 64bit archs. Used resources on for Kernel:stable/Kernel:HEAD (MBytes) Kernel:stable standard x86_64 kernel-vanilla Disk: 16273, Memory: 728, Time: 20519 Kernel:HEAD standard x86_64 kernel-debug Disk: 16279, Memory: 758, Time: 24744 Kernel:HEAD standard x86_64 kernel-default Disk: 16232, Memory: 1260, Time: 5804 Kernel:HEAD standard x86_64 kernel-pv Disk: 16366, Memory: 1263, Time: 4837 Kernel:HEAD standard x86_64 kernel-vanilla Disk: 16860, Memory: 751, Time: 17809 Kernel:HEAD PPC ppc64 kernel-vanilla Disk: 15142, Memory: 1117, Time: 6345 Kernel:HEAD ARM aarch64 kernel-vanilla Disk: 15214, Memory: 746, Time: 10565 Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 work: +49 2405 49936-424 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 6

[opensuse-kernel] [KOTD] 4.4.0-rc4-1.g923c13b-vanilla and WARNING: CPU: 0 PID: 2126 at ../kernel/module.c:1124 module_put+0xac/0xc0()
by Sebastian Herbszt 14 Dec '15

14 Dec '15

Hello, I am getting the following warning on 4.4.0-rc4-1.g923c13b-vanilla while loading a simple kernel module: [ 499.783288] init_module() [ 499.783301] ------------[ cut here ]------------ [ 499.783322] WARNING: CPU: 0 PID: 2126 at ../kernel/module.c:1124 module_put+0xac/0xc0() [ 499.783324] Modules linked in: h(O) xfs libcrc32c dm_mod sr_mod cdrom irda ata_generic floppy e1000 ppdev vmw_balloon fjes joydev i2c_piix4 8250_fintek crc_ccitt vmw_vmci ata_piix parport_pc parport shpchp mptctl pcspkr acpi_cpufreq battery tpm_tis tpm button ac sg mptspi mptscsih mptbase scsi_transport_spi vmwgfx ttm drm_kms_helper drm fb_sys_fops sysimgblt sysfillrect syscopyarea scsi_dh_alua scsi_dh_emc scsi_dh_rdac scsi_dh_hp_sw [ 499.783377] CPU: 0 PID: 2126 Comm: insmod Tainted: G O 4.4.0-rc4-1.g923c13b-vanilla #1 [ 499.783381] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/02/2012 [ 499.783384] ffffffff81a5cee9 ffff88000019fcc8 ffffffff8137ada9 0000000000000000 [ 499.783390] ffff88000019fd00 ffffffff8107c1f2 ffffffffa01db000 ffffffffa01db000 [ 499.783394] ffff880037c55600 0000000000000001 ffffffffa01db000 ffff88000019fd10 [ 499.783398] Call Trace: [ 499.783459] [<ffffffff8137ada9>] dump_stack+0x4b/0x72 [ 499.783476] [<ffffffff8107c1f2>] warn_slowpath_common+0x82/0xc0 [ 499.783484] [<ffffffff8107c2ea>] warn_slowpath_null+0x1a/0x20 [ 499.783488] [<ffffffff810fd52c>] module_put+0xac/0xc0 [ 499.783502] [<ffffffff811810d7>] do_init_module+0xd5/0x1e5 [ 499.783508] [<ffffffff81101f99>] load_module+0x15d9/0x1b30 [ 499.783513] [<ffffffff810fe190>] ? __symbol_put+0x50/0x50 [ 499.783522] [<ffffffff81102615>] SyS_init_module+0x125/0x160 [ 499.783534] [<ffffffff816a4db6>] entry_SYSCALL_64_fastpath+0x16/0x75 [ 499.783538] ---[ end trace 57f0d89c0b9a5063 ]--- This warning does not appear on 4.4.0-rc4-1.g923c13b-default. The module source is: #include <linux/module.h> #include <linux/kernel.h> int init_module(void) { printk(KERN_INFO "init_module()\n"); return 0; } void cleanup_module(void) { printk(KERN_INFO "cleanup_module()\n"); } MODULE_LICENSE("GPL"); Sebastian -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

4 6

[opensuse-kernel] prev-stable repo
by Olaf Hering 04 Dec '15

04 Dec '15

Should there be some prev-stable repo to make it easier to verify if a certain bug is a regression (bnc#957848)? As of today it would mean master is at 4.4, stable at 4.3.x and prev-stable at 4.2.x. Olaf -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 4

[opensuse-kernel] master build breakage for aarch64 - make all
by Andreas Färber 02 Dec '15

02 Dec '15

Hello, The Kernel:HEAD kernel is currently failing to build for aarch64. While this may or may not be due to a patch in our patch queue according to Matthias, I confirmed that it is building "make all" [1]. For aarch64 this unnecessarily builds not only "Image" and "modules" but also "dtbs", which are built separately in Base:System dtb-source. The failure here is due to an error building a .dtb file. Can this be changed to only build what's necessary per architecture? There is already an $image variable and @IMAGE@ placeholder elsewhere to handle image file differences (although x86 overrides that from bzImage to vmlinuz). Or would you rather want to patch the Makefile for vanilla and default to not include dtbs as a dependency of all? While aarch64 is doing okay in terms of build time currently, armv7l and armv6l will be affected by the same build duplication, wasting precious build time. Thanks, Andreas [1] https://build.opensuse.org/package/view_file/Kernel:HEAD/kernel-default/ker… -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] revert to 4K pagesize for ppc64
by Olaf Hering 02 Dec '15

02 Dec '15

Neither firewire nor nouveau seem to support 64K pagesize. Any objection to revert to 4K pages for ppc64/default? ppc64le can remain 64K. Olaf -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

6 17

[opensuse-kernel] Re: [LOG] kernel-source branch users/ohering/master/for-next created. ceec9f0
by Jeff Mahoney 01 Dec '15

01 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/1/15 9:24 AM, Olaf Hering wrote: > The branch users/ohering/master/for-next has been created at > ceec9f0a394b865d7a4ab0b0dd264805f7ede727 (commit) > > - Log > ----------------------------------------------------------------- > > commit ceec9f0a394b865d7a4ab0b0dd264805f7ede727 Author: Olaf > Hering <ohering(a)suse.de> Date: Tue Dec 1 15:22:12 2015 +0100 > > ppc64: Revert from 64K to 4K PAGE_SIZE to fix firewire and nouveau > on G5 > > ---------------------------------------------------------------------- - - > > > This seems like a pretty big change just to fix two drivers. Isn't the correct solution to fix the drivers? In SLE12, we only support ppc64le, but in openSUSE, are we certain that there aren't ppc64 big-endian users out there and that this change to fix drivers they might not even use is acceptable? - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJWXa4aAAoJEB57S2MheeWyi7YQAKHtW4Bq8Aiv4ohouHl+GZKf S5vWSavRuDYYCgREgXMkuKnBTzRgoTjepNdrb8gffkOWl2/pH5sOn71KNyl5Ies6 6nNzJlJB+JFGG073H7ZLuHPOa3yiAP1/wsBDPPYBbofc2X3JtUNnq5ppPWhTKDcw cuEqEz6ePsUjjgeB8HhnRxdjtZ9SS5qUeGEIKULSuuBbgoDpSXRhEXNdc36Mvi84 NMl8wzTw/gAhFMy/41K4HBWLp32Z4L6rqcoXhYGnMpVeP4u6bDQelfuhUGYYTeVG 0OQbi6KUgDeZ88UnLu5z+1ZJddsjsOIGXJzb8eNmeM/2dL6HLE793DJovX29X73T PCVKn+rbUG+du6dQuoeBLTwsLatsJPZliiO7QxKu2TSTBm1+VdD0gLly1VVCwT1i JLi7qovvp2v67RsJc0bmKvVj8FGRwu5uMhKL8ggqfBWRfXRHCSMdN06lb9Wwqf7R R4AFv9xYqB4kW8/sl3WKzO+qmAXhzbLCdE+qUKxoF0u+RUbHBJbaMJCu+V6Q+ye8 +35VoHMoDqYdz71c0WYambF8NNeqlX1YbzZJ4DURF/FdrY5/QaMaXPjC3o3HaVbn d5l86cUM7fjasQ9xIRxJK7EvSmMrY4CfpIbML2QMaXfngwBX81gKIMFd9CP82W58 9OesJ3bil1vh8LsrQ7Yi =/FUP -----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

2 4