openSUSE Kernel May 2014

kernel@lists.opensuse.org

24 participants
21 discussions

[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] shmobile support in armv7hl/default kernel
by Jean Delvare 23 Jun '14

23 Jun '14

Hi Guillaume, Andreas and all, I am wondering if our default armv7 kernel is supposed to support the shmobile architecture? I see the following: # CONFIG_ARCH_SHMOBILE_LEGACY is not set CONFIG_ARCH_SHMOBILE=y CONFIG_ARCH_SHMOBILE_MULTI=y CONFIG_SHMOBILE_TIMER_HZ=128 CONFIG_I2C_SH_MOBILE=m # CONFIG_VIDEO_SH_MOBILE_CSI2 is not set # CONFIG_VIDEO_SH_MOBILE_CEU is not set CONFIG_DRM_SHMOBILE=m # CONFIG_FB_SH_MOBILE_LCDC is not set # CONFIG_FB_SH_MOBILE_MERAM is not set # CONFIG_SHMOBILE_IOMMU is not set which gives me the feeling that we half-support it, which is not terribly useful. Can we make a decision and either enable all these drivers or disable shmobile support altogether? I don't care which way we go, but I would enjoy some consistency. Thanks, -- Jean Delvare SUSE L3 Support -- 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] Why is CONFIG_SLAB the default in SUSE kernels ?
by Cristian Rodríguez 12 Jun '14

12 Jun '14

Hi: Just out of curiosity, why SUSE kernels default to CONFIG_SLAB and not CONFIG_SLUB ? I just checked the rest of current distribution world and everyone else takes the kernel default. I am assuming there is a reason for this, that it is intentional and not a oversight where somebody forgot changing the configuration... -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

7 7

[opensuse-kernel] trim or not to trim : luks encrypted ssd
by Bruno Friedmann 05 Jun '14

05 Jun '14

A few months ago, I discovered that in mkinitrd we don't have (take care?) support for the option allow-discards for crypsetup luks drive. Trying fstrim: /: FITRIM ioctl failed: Operation not supported on plain stock 13.1 Even with the argument on boot line cryptdevice=/dev/mapper/cr_sda2:root:allow-discards I've then patched locally boot-luks.sh by adding the hard way the support by modifying the function luksopen() { local name="$1" local ask_pass="$2" eval local dev="\"\${luks_${name}}\"" eval local realname="\"\${luks_${name}_name}\"" if [ "$ask_pass" = no ]; then cryptsetup --tries=1 --allow-discards luksOpen "$dev" "$realname" ret="$?" elif luks_check_ply; then plymouth ask-for-password --prompt="Unlocking ${realname} ($dev)" | cryptsetup --tries=1 --allow-discards luksOpen "$dev" "$realname" ret="$?" else echo -e "${extd}Unlocking ${realname} ($dev)${norm}" splash_off cryptsetup --tries=1 --allow-discards luksOpen "$dev" "$realname" ret="$?" fi return "$ret" } Mostly cause my laptop has this option, part 1 is /boot unencrypted ext4 part 1 the whole rest with vg encrypted. So far so good, the discard option in fstab and manual fstrim function work after a reboot with the new initrd. My first question is : is it a good idea to have discard option for encrypted device ? My main concern is (my 2.5 years 480Gb ssd which totalize a 35000Gb write for 13000 hours powered on) behave strangely last week-end. Some binaries normally ELF became data file. (Was the case of dos2unix) which I don't run from months. rpm -Va show others like this .5.... just the md5sum has changed... Could it be linked to the fact that the ssd has work during 2.5 years without any trim? What your thought on it? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board GPG KEY : D5C9B751C4653227 irc: tigerfoot ~~~Don't take Life too serious. Nobody gets out alive anyway!~~~ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

7 14

[opensuse-kernel] please set CONFIG_FW_LOADER_USER_HELPER=n in kernel HEAD
by Cristian Rodríguez 02 Jun '14

02 Jun '14

Hi: The userspace firmware loader in udev should not be called anymore, I just submitted a new udev package that disables the code but would be much better if this functionality is disabled in the kernel so it does not creeps back ever again. -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- 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] Installing USB3 card in Opensuse 13.1 with Opensuse kernel cases boot fail & CallTrace. Filed a bug; told to go elsewhere?
by grantksupport＠operamail.com 27 May '14

27 May '14

I run Opensuse 13.1 + the Opensuse kernel from Kernel:/stable/standard, 3.14.4-1.gbebeb6f-desktop. When I install a new USB3 card, the system refuses to boot. I filed this bug about it Bug 878489 - Opensuse 13.1 throws CALL TRACE and fails to boot when USB3 (xhci_hcd) card is added. https://bugzilla.novell.com/show_bug.cgi?id=878489 @ the bug, I was told to go 'upstream' to #kernel I've spoken at some length at upstream, and they say 'no way', and that it's an Opensuse kernel that should be reported to Novell/*Suse. I'm an Opensuse user, using an Opensuse-specific kernel. Can somebody clear up who we're supposed to report this to to get this fixed for Opensuse? Grant -- 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] CONFIG_RTC_DRV_MOXART=m in openSUSE arm configs
by Jean Delvare 27 May '14

27 May '14

Hi Alexander, In: commit 2503bec93926d88267b7f4e4f45175b93fb511cd Author: Alexander Graf <agraf(a)suse.de> Date: Wed Sep 25 16:01:31 2013 +0200 - config.conf: - Update config files for ARM on 3.12. you set CONFIG_RTC_DRV_MOXART=m in all arm config files. Was it on purpose? As far as I can see this driver is only needed for the Moxa Art which is an ARM9 32-bit processor [1]. At least the arm64/default kernel doesn't seem suitable at all for such systems. In fact I don't think any of the openSUSE kernels would benefit from that option as they are all missing the rest of the Moxa Art support. So may I disable CONFIG_RTC_DRV_MOXART from all out kernels? I suppose RTC_DRV_MOXART should depend on ARCH_MOXART as other Moxa Art drivers do. [1] http://www.moxa.com/product/UC-7112_UC-7110.htm Thanks, -- Jean Delvare SUSE L3 Support -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 4

Re: [opensuse-kernel] trim or not to trim : luks encrypted ssd
by Bruno Friedmann 27 May '14

27 May '14

> Hi all, > > To Bruno, in cca 2 yrs you own the drive, have you ever done secure erase? > Not through live/installation media but actual command to fw to perform > zeroing. Yeap 1.5 year ago, just before I install 12.3 I've secure erased the ssd. Now I've do it again, and restore the data afterward from good backup. I would recommand to anyone to do this, at least once 1.5 years (if like me) it is running 24h/24h with lot of read/write ( database, files, osc build etc) > > To Greg, sorry, been busy. Will adapt the page soon. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board GPG KEY : D5C9B751C4653227 irc: tigerfoot ~~~Don't take Life too serious. Nobody gets out alive anyway!~~~ -- 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] Kernel 3.15rc5 much too large
by Stephan Kulow 26 May '14

26 May '14

Hi, I accepted 3.15rc5 after openqa tested it OK, but it won't be published in factory unless the size issue is fixed. 6,1M 13. Apr 13:12 vmlinux-3.14.0-2-desktop.gz 67M 23. Mai 16:46 vmlinux-3.15.0-rc5-1-desktop.gz So the kernel image grew 1098% - please someone have a look at it. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 2

[opensuse-kernel] missing vhba-kmp rpm for kernel 3.11.10-11.1
by Giacomo Comes 21 May '14

21 May '14

Yesterday there was a kernel update for openSUSE 13.1 Together were updated also the rpm with out-of-tree kernel modules: ipset-kmp, iscsitarget-kmp, ndiswrapper-kmp etc. One rpm is missing though: vhba-kmp. Can this be fixed? This missing rpm causes the installation of kernel-<flavor>-base with mkinitrd issues. See my previous post on the subject: http://lists.opensuse.org/opensuse-kernel/2014-02/msg00020.html Giacomo -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 3

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openSUSE Kernel May 2014