July 2017 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] v4.13-rc1 module linking issue
by Andreas Färber 09 Sep '17

09 Sep '17

Hi, I'm facing an error trying to locally build a custom kernel module: make -C /lib/modules/`uname -r`/build M=$PWD make[1]: Entering directory '/usr/src/linux-4.13.0-rc1-2.g9c198f2-obj/arm64/default' AR /home/andreas/lora/built-in.o CC [M] /home/andreas/lora/af_lora.o LD [M] /home/andreas/lora/lora.o CC [M] /home/andreas/lora/dev.o LD [M] /home/andreas/lora/lora-dev.o CC [M] /home/andreas/lora/sx1276.o CC [M] /home/andreas/lora/rn2483.o Building modules, stage 2. MODPOST 4 modules CC /home/andreas/lora/lora-dev.mod.o LD [M] /home/andreas/lora/lora-dev.ko ld: cannot find ./arch/arm64/kernel/ftrace-mod.o: No such file or directory make[4]: *** [/usr/src/linux-4.13.0-rc1-2.g9c198f2/scripts/Makefile.modpost:132: /home/andreas/lora/lora-dev.ko] Error 1 make[3]: *** [/usr/src/linux-4.13.0-rc1-2.g9c198f2/Makefile:1525: modules] Error 2 make[2]: *** [Makefile:145: sub-make] Error 2 make[1]: *** [Makefile:24: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-4.13.0-rc1-2.g9c198f2-obj/arm64/default' make: *** [Makefile:8: all] Error 2 If I pass KDIR=/lib/modules/4.12.*/build it builds okay. To reproduce: git clone https://github.com/afaerber/lora-modules.git cd lora-modules make It's not specific to that module of mine: make -C /lib/modules/`uname -r`/build M=$PWD make[1]: Entering directory '/usr/src/linux-4.13.0-rc1-2.g9c198f2-obj/arm64/default' AR /home/andreas/netx-module/built-in.o CC [M] /home/andreas/netx-module/netx.o Building modules, stage 2. MODPOST 1 modules CC /home/andreas/netx-module/netx.mod.o LD [M] /home/andreas/netx-module/netx.ko ld: cannot find ./arch/arm64/kernel/ftrace-mod.o: No such file or directory make[4]: *** [/usr/src/linux-4.13.0-rc1-2.g9c198f2/scripts/Makefile.modpost:132: /home/andreas/netx-module/netx.ko] Error 1 make[3]: *** [/usr/src/linux-4.13.0-rc1-2.g9c198f2/Makefile:1525: modules] Error 2 make[2]: *** [Makefile:145: sub-make] Error 2 make[1]: *** [Makefile:24: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-4.13.0-rc1-2.g9c198f2-obj/arm64/default' make: *** [Makefile:8: all] Error 2 git clone https://github.com/afaerber/netx-module.git cd netx-module make On x86_64 (Leap host) lora-modules.git builds okay. armv7hl 4.13-rc1 packages haven't finished building yet for comparison. Any ideas what's going wrong here? Our config/arm64/default Kconfig? Our kernel[-default]-devel packaging? Something in the upstream kernel? Thanks, Andreas -- 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

3 4

[opensuse-kernel] Frequency of Leap kernel updates
by Takashi Iwai 07 Sep '17

07 Sep '17

Hi, as we're closing to the release of Leap 42.3, I'd like to ask your opinions about the frequency of update kernel releases. For Leap 42.1 and 42.2, I've tried to pick up the update regularly, roughly once per month. For example, below is the list of kernels that have been released for Leap 42.2: 4.4.27-1 20161027 4.4.36-5 * 20161208 4.4.36-8 20161209 4.4.46-11 20170204 4.4.49-16 * 20170219 4.4.57-18.3 * 20170330 4.4.62-18.6 20170421 4.4.70-18.9 20170531 4.4.72-18.12 * 20170619 4.4.73-18.17 20170623 4.4.74-18.20 20170630 The kernels with asterisk are for security updates. My question here is whether this rhythm is ideal for users and from maintenance burden POV. Should the update be triggered more often, a la rolling release like each stable 4.4.x kernel update? Or twice per month? Or better to be less frequently? Release more often would allow catching a regression more quickly, and this would make bug hunting easier. More frequent update is no problem from my kernel branch maintainer side, too, but it'll certainly increase the load for QA. Comments? thanks, Takashi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 19

[opensuse-kernel] [PATCH] arm64: Enable RTC and SPI on Allwinner A64/H5
by Stefan Brüns 11 Aug '17

11 Aug '17

A64 and H5 share the RTC and SPI functional blocks with older SoCs, enable the corresponding drivers. Signed-off-by: Stefan Brüns <stefan.bruens(a)rwth-aachen.de> --- config/arm64/default | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) Based on master branch, commit 40a86960d573 diff --git a/config/arm64/default b/config/arm64/default index 286b93b710..c9107abca1 100644 --- a/config/arm64/default +++ b/config/arm64/default @@ -3931,7 +3931,7 @@ CONFIG_SPI_QUP=m CONFIG_SPI_S3C64XX=m CONFIG_SPI_SC18IS602=m CONFIG_SPI_SUN4I=m -# CONFIG_SPI_SUN6I is not set +CONFIG_SPI_SUN6I=m CONFIG_SPI_TEGRA20_SFLASH=m CONFIG_SPI_THUNDERX=m CONFIG_SPI_XCOMM=m @@ -6820,7 +6820,7 @@ CONFIG_HAVE_S3C_RTC=y CONFIG_RTC_DRV_S3C=m CONFIG_RTC_DRV_PL030=y CONFIG_RTC_DRV_PL031=y -# CONFIG_RTC_DRV_SUN6I is not set +CONFIG_RTC_DRV_SUN6I=y CONFIG_RTC_DRV_MV=y # CONFIG_RTC_DRV_ARMADA38X is not set CONFIG_RTC_DRV_FTRTC010=m -- 2.13.2 -- 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] XFS metadata I/O error since Leap 42.3 kernel
by Stefan Priebe - Profihost AG 31 Jul '17

31 Jul '17

Hello, while testing the opensuse 42.3 kernel (commit cacedb76a59dcf452aaab40b9307bd7604ed5c28) i'm getting XFS crashes under high load. The device is a bcache device. dmesg output: XFS (bcache1): metadata I/O error: block 0x575b6d70 ("xfs_trans_read_buf_map") error 4 numblks 16 XFS (bcache1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -4. XFS (bcache1): xfs_do_force_shutdown(0x8) called from line 3519 of file fs/xfs/xfs_inode.c. Return address = 0xffffffff993441ff XFS (bcache1): Corruption of in-memory data detected. Shutting down filesystem XFS (bcache1): Please umount the filesystem and rectify the problem(s) XFS (bcache1): xfs_log_force: error -5 returned. XFS (bcache1): xfs_log_force: error -5 returned. XFS (bcache1): xfs_log_force: error -5 returned. I'm not sure whether this is a bug in bcache or in xfs. Greets, Stefan -- 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] How csn I build a kernel with a specific patch which is applied to it, [obs]
by doiggl＠velocitynet.com.au 31 Jul '17

31 Jul '17

Hello, >From build log [1] what change to spec [2] fixes following error. The reiser4-for-4.11.0.patch applies to kernel ok[3]. Help appreciated for build steps. Thanks --Glenn full log: [1]https://build.opensuse.org/package/live_build_log/home:doiggl/kernel-vani… [ 46s] + /bin/cat [ 46s] + echo '##try 1' [ 46s] ##try 1 [ 46s] + /usr/bin/make oldconfig --output-sync -j6 [ 46s] make: *** No rule to make target 'oldconfig'. Stop. [ 46s] error: Bad exit status from /var/tmp/rpm-tmp.15koql (%prep) [ 46s] [ 46s] [ 46s] RPM build errors: [ 46s] Bad exit status from /var/tmp/rpm-tmp.15koql (%prep) [ 46s] [ 46s] lamb77 failed "build kernel-vanilla.spec" at Sun Jul 30 05:56:08 UTC 2017. [ 46s] [ 46s] ### VM INTERACTION START ### [ 49s] [ 36.557432] sysrq: SysRq : Power Off [ 49s] [ 36.562105] reboot: Power down [ 50s] ### VM INTERACTION END ### [ 50s] [ 50s] lamb77 failed "build kernel-vanilla.spec" at Sun Jul 30 05:56:13 UTC 2017. [ 50s] [2] https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ser… series.conf ######################################################## # latest standard kernel patches # DO NOT MODIFY THEM! # Send separate patches upstream if you find a problem... ######################################################## patches.kernel.org/patch-4.12.1 patches.kernel.org/patch-4.12.1-2 patches.kernel.org/patch-4.12.2-3 patches.kernel.org/patch-4.12.3-4 ######################################################## # Reiser4 patch ######################################################## patches.rpmify/reiser4-for-4.11.0.patch [1]build log: https://build.opensuse.org/build/home:doiggl/openSUSE_Factory/x86_64/kernel… [ 45s] + /home/abuild/rpmbuild/SOURCES/apply-patches --vanilla /home/abuild/rpmbuild/SOURCES/series.conf .. [ 45s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-4.12.1 [ 45s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-4.12.1-2 [ 45s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-4.12.2-3 [ 45s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-4.12.3-4 [ 45s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.rpmify/reiser4-for-4.11.0.patch [ 45s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.rpmify/firmware-path [ 45s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.rpmify/cloneconfig.diff [ 45s] + cd /home/abuild/rpmbuild/BUILD/kernel-vanilla-4.12.4/linux-4.12/linux-obj [2] spec https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ker… https://build.opensuse.org/package/show/home:doiggl/kernel-vanilla [3]series.conf https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ser… reiser4-for-4.11.0.patch applies ok -- 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] Can anyone help with query I have.
by doiggl＠velocitynet.com.au 31 Jul '17

31 Jul '17

Hello, Can anyone help with query I have. [see links below] https://bugzilla.novell.com/show_bug.cgi?id=1051384 https://lists.opensuse.org/opensuse-kernel/2017-07/msg00050.html Thanks for your Expertise. Thanks --Glenn -- 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] EOL kernel 4.11.8 in TW
by Felix Miata 25 Jul '17

25 Jul '17

Just out of curiosity, has the reason why TW hasn't yet moved to 4.12.x been discussed publicly and I just didn't recognize it? Maybe so many resources devoted to getting 42.3 released tomorrow? www.kernel.org says 4.11.12 went EOL last week, and 4.12.3 is current. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

4 3

[opensuse-kernel] Kernel:stable flavor for 42.3
by Giacomo Comes 12 Jul '17

12 Jul '17

Back in January there was a talk on this mailing list about adding a new kernel flavor to follow upstream (https://lists.opensuse.org/opensuse-kernel/2017-01/msg00040.html) A quick look at the upcoming release packages, shows me that such kernel is not there. I personally would appreciate such kernel very much because I have 4 different kind of devices for which kernel 4.4 has problems but newer kernel fixed the issue. Is there still some hope to see such kernel flavor in 42.3? Giacomo -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 3

[opensuse-kernel] Leap 42.3, kernel > 4.4.72 : AMD-Vi kernel freeze
by Bruno Friedmann 12 Jul '17

12 Jul '17

Testing openSUSE Leap 42.3 on one of my system, I've seen a hard lockup of the kernel happening for all of them superior to 4.4.72 version. Before filling up a bugzilla entry, I would like to confirm the symptom. Motherboard is a ASUS CROSSHAIR V FORMULA-Z, BIOS 2201 03/23/2015 (latest available) The CPU is an AMD FX(tm)-8350 Eight-Core Processor With 4.4.72 everything was working (since years the hardware was used before with 13.1 and 42.1). Since kernel 4.4.74 with iommu enabled in bios, I got freeze, like one of the trace I finally found in journal. (Attached) Today I retry with 4.4.75 and get immediately after the system is online a AMD-Vi buffer timeout error. I since then disabled iommu in the bios and the computer doesn't show bugs. I know there was a kernel-firmware and ucode-amd update between the 4.4.72 and now. Could you drive me to find the right culprit or confirm the problem ? So I can build a nice and complete bugzilla report. Thanks for your help and advise. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot

2 2

[opensuse-kernel] Linux 4.12 & BFQ
by Dmitriy A. Perlow 10 Jul '17

10 Jul '17

Hello. Is BFQ enabled for kernel builds? I tried elevator=bfq with 4.12.rc7 and got all partitions unmountable. -- Best regards, Dmitriy Perlow -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

5 13