openSUSE Kernel May 2012

kernel@lists.opensuse.org

21 participants
17 discussions

[opensuse-kernel] [CONFIG] Disabled options
by Jeff Mahoney 13 Jun '12

13 Jun '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - Just a quick heads up that I've disabled a bunch of options on the HEAD kernel. I've disabled DECNet and ARCnet. I've disabled LocalTalk drivers on i386-default. I've disabled many drivers that can only be used on embedded hardware. While I don't doubt that there are users out there playing with Linux on embedded hardware - I do doubt that they're using an openSUSE-built kernel RPM. The disabled modules include voltage regulators, multifunction devices that are typically found on SoCs, IIO sensor drivers, SPI drivers, and drivers only used on Intel Medfield or Moorestown. I'd like to try to clear out as many of the drivers we're building that are inappropriate for desktop, server, or notebook systems. That includes drivers that are only used for embedded devices and hardware that is so ancient that nobody is likely to be using it anymore. The former is pretty easy but the latter gets tricky. The goal is to save on users' disk space, download bandwidth, and build resources. DECNet and ARCnet were rare already in my former life as a sysadmin. That was over 10 years ago. Here's the full list of disabled options: CONFIG_ARCNET CONFIG_ARCNET_1051 CONFIG_ARCNET_1201 CONFIG_ARCNET_CAP CONFIG_ARCNET_COM20020_CS CONFIG_ARCNET_COM20020 CONFIG_ARCNET_COM20020_PCI CONFIG_ARCNET_COM90xxIO CONFIG_ARCNET_COM90xx CONFIG_ARCNET_RAW CONFIG_ARCNET_RIM_I CONFIG_DECNET CONFIG_DECNET_NF_GRABULATOR CONFIG_COPS CONFIG_LTPC CONFIG_AD2S1200, CONFIG_AD2S1210, CONFIG_AD2S90, CONFIG_AD5064, CONFIG_AD5360, CONFIG_AD5380, CONFIG_AD5421, CONFIG_AD5446, CONFIG_AD5504, CONFIG_AD5624R_SPI, CONFIG_AD5686, CONFIG_AD5764, CONFIG_AD5791, CONFIG_AD5930, CONFIG_AD5933, CONFIG_AD7150, CONFIG_AD7152, CONFIG_AD7192, CONFIG_AD7280, CONFIG_AD7291, CONFIG_AD7298, CONFIG_AD7476, CONFIG_AD7606_IFACE_PARALLEL, CONFIG_AD7606_IFACE_SPI, CONFIG_AD7606, CONFIG_AD7746, CONFIG_AD7780, CONFIG_AD7793, CONFIG_AD7816, CONFIG_AD7887, CONFIG_AD799X, CONFIG_AD799X_RING_BUFFER, CONFIG_AD9832, CONFIG_AD9834, CONFIG_AD9850, CONFIG_AD9852, CONFIG_AD9910, CONFIG_AD9951, CONFIG_ADE7753, CONFIG_ADE7754, CONFIG_ADE7758, CONFIG_ADE7759, CONFIG_ADE7854_I2C, CONFIG_ADE7854, CONFIG_ADE7854_SPI, CONFIG_ADIS16060, CONFIG_ADIS16080, CONFIG_ADIS16130, CONFIG_ADIS16201, CONFIG_ADIS16203, CONFIG_ADIS16204, CONFIG_ADIS16209, CONFIG_ADIS16220, CONFIG_ADIS16240, CONFIG_ADIS16260, CONFIG_ADIS16400, CONFIG_ADT7310, CONFIG_ADT7316_I2C, CONFIG_ADT7316, CONFIG_ADT7316_SPI, CONFIG_ADT7410, CONFIG_ADXRS450, CONFIG_BACKLIGHT_WM831X, CONFIG_CAN_JANZ_ICAN3, CONFIG_FB_SM501, CONFIG_GPIO_JANZ_TTL, CONFIG_GPIO_RDC321X, CONFIG_GPIO_STMPE, CONFIG_GPIO_TIMBERDALE, CONFIG_GPIO_WM831X, CONFIG_IIO_BUFFER, CONFIG_IIO_CONSUMERS_PER_TRIGGER=2, CONFIG_IIO_GPIO_TRIGGER, CONFIG_IIO_KFIFO_BUF, CONFIG_IIO, CONFIG_IIO_PERIODIC_RTC_TRIGGER, CONFIG_IIO_SIMPLE_DUMMY, CONFIG_IIO_ST_HWMON, CONFIG_IIO_SW_RING, CONFIG_IIO_SYSFS_TRIGGER, CONFIG_IIO_TRIGGER, CONFIG_INPUT_MC13783_PWRBUTTON, CONFIG_INPUT_WM831X_ON, CONFIG_KEYBOARD_STMPE, CONFIG_KXSD9, CONFIG_LEDS_MC13783, CONFIG_LEDS_REGULATOR, CONFIG_LEDS_WM831X_STATUS, CONFIG_LIS3L02DQ_BUF_KFIFO, CONFIG_LIS3L02DQ, CONFIG_MAX1363, CONFIG_MAX1363_RING_BUFFER, CONFIG_MAX517, CONFIG_MFD_CORE, CONFIG_MFD_JANZ_CMODIO, CONFIG_MFD_MC13783, CONFIG_MFD_MC13XXX, CONFIG_MFD_RDC321X, CONFIG_MFD_SM501_GPIO, CONFIG_MFD_SM501, CONFIG_MFD_STMPE, CONFIG_MFD_TIMBERDALE, CONFIG_MFD_TPS65217, CONFIG_MFD_WM831X_SPI, CONFIG_MFD_WM831X, CONFIG_MFD_WM8400, CONFIG_RADIO_TIMBERDALE, CONFIG_REGMAP_I2C, CONFIG_REGMAP_SPI, CONFIG_REGMAP, CONFIG_REGULATOR_AD5398, CONFIG_REGULATOR_DA903X, CONFIG_REGULATOR_DEBUG, CONFIG_REGULATOR_DUMMY, CONFIG_REGULATOR_FIXED_VOLTAGE, CONFIG_REGULATOR_GPIO, CONFIG_REGULATOR_ISL6271A, CONFIG_REGULATOR_LP3971, CONFIG_REGULATOR_LP3972, CONFIG_REGULATOR_MAX1586, CONFIG_REGULATOR_MAX8649, CONFIG_REGULATOR_MAX8660, CONFIG_REGULATOR_MAX8952, CONFIG_REGULATOR_MC13783, CONFIG_REGULATOR_MC13892, CONFIG_REGULATOR_MC13XXX_CORE, CONFIG_REGULATOR_PCAP, CONFIG_REGULATOR_TPS6105X, CONFIG_REGULATOR_TPS62360, CONFIG_REGULATOR_TPS65023, CONFIG_REGULATOR_TPS6507X, CONFIG_REGULATOR_TPS65217, CONFIG_REGULATOR_TPS6524X, CONFIG_REGULATOR_USERSPACE_CONSUMER, CONFIG_REGULATOR_VIRTUAL_CONSUMER, CONFIG_REGULATOR_WM831X, CONFIG_REGULATOR_WM8400, CONFIG_REGULATOR, CONFIG_RFKILL_REGULATOR, CONFIG_RTC_DRV_MC13XXX, CONFIG_RTC_DRV_WM831X, CONFIG_SCA3000, CONFIG_SENSORS_AK8975, CONFIG_SENSORS_HMC5843, CONFIG_SENSORS_ISL29018, CONFIG_SENSORS_MC13783_ADC, CONFIG_SENSORS_TSL2563, CONFIG_SENSORS_WM831X, CONFIG_SERIAL_MFD_HSU, CONFIG_SERIAL_UARTLITE, CONFIG_STMPE_I2C, CONFIG_STMPE_SPI, CONFIG_TOUCHSCREEN_MC13783, CONFIG_TOUCHSCREEN_STMPE, CONFIG_TOUCHSCREEN_WM831X, CONFIG_TPS6105X, CONFIG_TSL2583, CONFIG_WM831X_BACKUP, CONFIG_WM831X_POWER, CONFIG_WM831X_WATCHDOG - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPmYT7AAoJEB57S2MheeWyrW0P/i+Obf4QMQIr0xTD7YoNbczI LLYc92bYZ5vPPLq+Cl+V8Mv0DkMw6n9OziJ6KpB2xklgNHgmEqM0Hk7A6UdV8Ms9 BfnoZiEVOrj5TpgeTNL6j39/cMKaA0bXeU5ZotPJLxUlakxfhtJkwEzkhhThtZLV ewIzOSIXV4IoEhUgKCEhd/F3TRpvotAe/rTybiujxrvFUj8fq/+GRThklNtSmvqf 2+IvS2bfiDqdx88nMq5QIHwjOnfDrFLgsf2dDt46710SaUlaPogZPo6k3bBaaNLi rC0wzTRPTtrmFiEq/XI1jncbFBNb4ne1ys77dsaM//mkRDLKntNyOBMnxV0tlw+j RQA6WB1tp9qwMPrtXYMtJoEKgj7sXwBlPLql5aaF3cIpW4hsIzq3Cpnfn02ddnjf aUHgFtZZTEHCUg7iaMKNqMNDCED5z/6DwYXArgQewZP2SQJYIVpSMFwu7U48Jakr VDaUf9QTcIMxD/j8Ng3cXj3a1UbiVtjl8uM4rHUThTZjI+99ieN92J239qXPjfVH eC5ewwm2eXOmOTtSYUnoAs7pbUUZDVxYCPc68PoPzaG63HZjqje0+kIuxlEWqi0+ JrywGOZfBJYp4dbCzyc8iMMMjWwbHAbMT5SPWxrgG6QRiPH2vGoR5742kHh4eX73 9Y/MR9Yyc9B/O+Qh5wBO =2CJZ -----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

5 20

[opensuse-kernel] kernel-default-debuginfo-3.4.0-25.2-x86_64 in Tumbleweed. No debugging data available
by Jon Arne Jørgensen 31 May '12

31 May '12

Hi, I'm developing a Linux driver, and have been using "gnu crash" with kdump/kexec to debug kernel crashes during development. Today "gnu crash" failed with: --- crash: /var/tmp/vmlinux-3.4.0-25-default.gz_keG5g9: no debugging data available crash: vmlinux-3.4.0-25-default.debug: debuginfo file not found crash: either install the appropriate kernel debuginfo package, or copy vmlinux-3.4.0-25-default.debug to this machine --- Where should the "vmlinux-3.4.0-25-default.debug" file that "gnu crash" is looking for be located? I've been googeling like a madman the whole day, and installing/removing the different debug kernels, with no luck. I don't know if the culprit is "gnu crash" or if this has something to do with Tumbleweed. The next option I can think of is to compile the kernel my self, then I would know if it was compiled with debug-symbols, but I tought I should ask here before starting a big compile :) Any help, or directions for where to look next would be appreciated. Some info: --- $ uname -a Linux linux-l0ba.site 3.4.0-25-default #1 SMP Mon May 21 15:20:43 UTC 2012 (6966f52) x86_64 x86_64 x86_64 GNU/Linux $zypper se -i -s "kernel" Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | --+----------------------------+---------+-----------------+--------+------------------------ i | kernel-debug | package | 3.4.0-25.2 | x86_64 | i | kernel-debug-devel | package | 3.4.0-25.2 | x86_64 | i | kernel-default | package | 3.4.0-25.2 | x86_64 | i | kernel-default-debuginfo | package | 3.4.0-25.2 | x86_64 | i | kernel-default-debugsource | package | 3.4.0-25.2 | x86_64 | i | kernel-default-devel | package | 3.4.0-25.2 | x86_64 | i | kernel-devel | package | 3.4.0-25.1 | noarch | i | kernel-docs | package | 3.4.0-25.1 | noarch | i | kernel-firmware | package | 20111025git-5.1 | noarch | -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

5 12

[opensuse-kernel] Will kernel version linux-3.4 be used in Opensuse 12.2 as this kernel is released
by doiggl＠velocitynet.com.au 24 May '12

24 May '12

Hello Will kernel version linux-3.4 be used in Opensuse 12.2 as this kernel is released ? Thanks Glenn [1]http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.4.tar.bz2 -- 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] How is build kernel-firmware [related to bnc 760857]
by Bruno Friedmann 18 May '12

18 May '12

In bnc bug 760857 An end user using Centrino Wireless-N 2230 wifi adapter find that the corresponding firmware iwlwifi-2030-5.ucode didn't load. I was thinking about a missing kernel-firmware package, but even installed the 2030 is not here. A missing somewhere ? Look like we didn't have all presented firmware here http://intellinuxwireless.org/?n=Downloads Can someone have a look to it? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- 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] 3.4rc6: ACPI change/regression ?
by Cristian Rodríguez 14 May '12

14 May '12

Hi: Since 3.4rc6 I am not able to "turn off" unused Nvidia "optimus" card, either with 3rd party modules or vga_switchero. In rc5 it worked fine, now I get: a) with third party bbswitch module. bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0 bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP bbswitch: detected an Optimus _DSM function bbswitch: disabling discrete graphics bbswitch: Result of Optimus _DSM call: 11000059 pci 0000:01:00.0: Refused to change power state, currently in D0 ACPI: Device does not support D3 bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on Ok, third party module may be buggy and I don't expect anyone here to support it, so I went to try kernel vga_switchero.. VGA switcheroo: switched nouveau off [drm] nouveau 0000:01:00.0: Disabling display... [drm] nouveau 0000:01:00.0: Disabling fbcon... [drm] nouveau 0000:01:00.0: Unpinning framebuffer(s)... [drm] nouveau 0000:01:00.0: Evicting buffers... [drm] nouveau 0000:01:00.0: Idling channels... [drm] nouveau 0000:01:00.0: Suspending GPU objects... [drm] nouveau 0000:01:00.0: And we're gone! ACPI: Device does not support D3 But device DOES support D3 states or at least it did in rc5.. The ill effec of this change is that now the video card fan is running almost all the time. Is this a side effect of http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=1cc… ? -- 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] [Fwd: [fedora-arm] Fwd: [PATCH 1/2] ARM: audit: fix treatment of saved ip register during syscall tracing]
by Andrew Wafaa 09 May '12

09 May '12

Could we also get this applied to our kernels, please? -------- Forwarded Message -------- From: Jon Masters <jonathan(a)jonmasters.org> To: arm <arm(a)lists.fedoraproject.org>, kernel(a)lists.fedoraproject.org Subject: [fedora-arm] Fwd: [PATCH 1/2] ARM: audit: fix treatment of saved ip register during syscall tracing Date: Fri, 04 May 2012 13:24:04 -0400 Please apply to our Fedora kernels. -------- Original Message -------- Subject: [PATCH 1/2] ARM: audit: fix treatment of saved ip register during syscall tracing Date: Fri, 4 May 2012 17:52:02 +0100 From: Will Deacon <will.deacon(a)arm.com> To: patches(a)arm.linux.org.uk CC: stable(a)vger.kernel.org The ARM audit code incorrectly uses the saved application ip register value to infer syscall entry or exit. Additionally, the saved value will be clobbered if the current task is not being traced, which can lead to libc corruption if ip is live (apparently glibc uses it for the TLS pointer). This patch fixes the syscall tracing code so that the why parameter is used to infer the syscall direction and the saved ip is only updated if we know that we will be signalling a ptrace trap. Cc: stable(a)vger.kernel.org Cc: Eric Paris <eparis(a)redhat.com> Reported-and-tested-by: Jon Masters <jcm(a)jonmasters.org> Signed-off-by: Will Deacon <will.deacon(a)arm.com> KernelVersion: 3.4-rc5 --- arch/arm/kernel/ptrace.c | 16 ++++++++-------- 1 files changed, 8 insertions(+), 8 deletions(-) diff --git a/arch/arm/kernel/ptrace.c b/arch/arm/kernel/ptrace.c index 80abafb..d8dbe9c 100644 --- a/arch/arm/kernel/ptrace.c +++ b/arch/arm/kernel/ptrace.c @@ -916,14 +916,7 @@ asmlinkage int syscall_trace(int why, struct pt_regs *regs, int scno) { unsigned long ip; - /* - * Save IP. IP is used to denote syscall entry/exit: - * IP = 0 -> entry, = 1 -> exit - */ - ip = regs->ARM_ip; - regs->ARM_ip = why; - - if (!ip) + if (why) audit_syscall_exit(regs); else audit_syscall_entry(AUDIT_ARCH_NR, scno, regs->ARM_r0, @@ -936,6 +929,13 @@ asmlinkage int syscall_trace(int why, struct pt_regs *regs, int scno) current_thread_info()->syscall = scno; + /* + * IP is used to denote syscall entry/exit: + * IP = 0 -> entry, =1 -> exit + */ + ip = regs->ARM_ip; + regs->ARM_ip = why; + /* the 0x80 provides a way for the tracing parent to distinguish between a syscall stop and SIGTRAP delivery */ ptrace_notify(SIGTRAP | ((current->ptrace & PT_TRACESYSGOOD) -- 1.7.4.1 -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html _______________________________________________ arm mailing list arm(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F

2 2

[opensuse-kernel] ARM config update
by Guillaume Gardet 09 May '12

09 May '12

Hi, please find in attachment the ARM configs update from 3.4.0-rc5 to 3.4.0-rc6. Signed-off-by: Guillaume GARDET <guillaume.gardet(a)opensuse.org>

1 0

[opensuse-kernel] Server frozen after 84 days with strange i2c errors
by Jaromír Červenka 09 May '12

09 May '12

Hello, today, one of my servers frozen out of nowhere. After hard reset, I found this in /var/log/messages http://paste.opensuse.org/83089371 Configuration: openSUSE 12.1 Linux onca 3.1.9-1.4-default #1 SMP Fri Jan 27 08:55:10 UTC 2012 (efb5ff4) x86_64 x86_64 x86_64 GNU/Linux Could it be a bug of kernel module or HW error? Thank you for any advice or idea, Jaromír Červenka Membership officials team Web: http://www.cervajz.com/ Jabber: cervajz(a)cervajz.com MSN: jara.cervenka(a)seznam.cz Tel.: +420 607 592 687 -- 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] Correct USB quirk for this device ?
by Cristian Rodríguez 09 May '12

09 May '12

Hi: I have one device called "entropy key" http://www.entropykey.co.uk/ 9: USB 00.0: 10200 Modem [Created at usb.122] Unique ID: hhw5.xbUS5LcXf33 Parent ID: FZIx.RTX9xWW_uz4 SysFS ID: /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0 SysFS BusID: 8-1:1.0 Hardware Class: modem Model: "Simtec Electronics Entropy Key" Hotplug: USB Vendor: usb 0x20df "Simtec Electronics" Device: usb 0x0001 "Entropy Key" Revision: "2.00" Serial ID: "M/9uBjBLNzE3QSFD" Driver: "cdc_acm" Driver Modules: "cdc_acm" Device File: /dev/ttyACM0 Device Files: /dev/ttyACM0, /dev/serial/by-id/usb-Simtec_Electronics_Entropy_Key_M_9uBjBLNzE3QSFD-if00, /dev/serial/by-path/pci-0000:00:1d.2-usb-0:1:1.0 Speed: 12 Mbps Module Alias: "usb:v20DFp0001d0200dc02dsc00dp00ic02isc02ip01" Driver Info #0: Driver Status: cdc_acm is active Driver Activation Cmd: "modprobe cdc_acm" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #18 (Hub) which works just fine most of the time, except that it has never-ever recovered after suspend/resume, the only way to make it "live again" is plug/unplug the device after resume, or with an pm script #!/bin/bash . /usr/lib/pm-utils/functions case "$1" in hibernate|suspend) stopservice ekeyd modunload cdc-acm ;; thaw|resume) modreload cdc-acm restartservice ekeyd ;; *) ;; esac exit 0 and well, that's really *really* ugly. Looking at the USB quirks list, looks like this device needs USB_QUIRK_RESET_RESUME, I am not a kernel developer so Im not sure about if this is correct. will be cool if someone can add the quirk if it is the correct one or point me to the right approach. ;) -- 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_FRONTSWAP ..
by Cristian Rodríguez 07 May '12

07 May '12

Hi: Is there a chance to get kernels with CONFIG_FRONTSWAP set to yes ? Thanks ! -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openSUSE Kernel May 2012