openSUSE Kernel March 2012

kernel@lists.opensuse.org

25 participants
13 discussions

[opensuse-kernel] [PATCH] LKDB: Fix usability issues with 'enter'.

by Andrei Warkentin

This fixes the following problems: 1) Typematic-repeat of 'enter' gives warning message. 2) Use of 'keypad enter' gives warning message. 3) Lag on the order of seconds between "break" and "make" when expecting the enter "break" code. Seen under virtualized environments such as VMware ESX. Explanations: 1) Holding down 'enter' will not set a repeating sequence of 0x1c(make)-0x9c(make), but a repeating sequence of make codes, followed by one break code when the key is released. Thus, it's wrong to expect the break code after seeing the 'enter' make code. 2) Keypad enter generates different make/break, namely 0xe0 0x1c and 0xe0 0x9c. The 'generic' logic handles the 0xe0 escape already, but the special 'enter' logic always expects '0x9c' and not '0xe0 0x9c', so you get a warning message, again. 3) When expecting the 'enter' break code, the code polls the status register in a tight loop, like so - > while ((inb(KBD_STATUS_REG) & KBD_STAT_OBF) == 0); However, it really should do something like - > while ((inb(KBD_STATUS_REG) & KBD_STAT_OBF) == 0) > cpu_relax(); /* pause */ Basically, it's a common optimization to have a fast path for accessing often accessed and slow changing I/O in a virtualized environment. The tight spinning in KDB seems to run against the logic by ESX keyboard virtualization code to detect when the fast path or the slow path should be used to satisfy the keyboard status read, leading to multi-second timeouts before the 'real' status comes through. Without knowing ESX internals, it's hard to say if this is an ESX bug or not, but letting the VM be explicitely descheduled seems to resolve the problem. I've seen something similar with shared MMIO buffers with VMs on Hyper-V. Anyway, given (3), (2) and (1), we might as well blow away the entire special casing for 'enter'. The break codes will already be handled correctly, and we get rid of the bugs with repeat enters and keypad enter key. And of course, there is no need to AND with 0x7f when checking for 'enter', because we'll never ever get to this code with a break code (checked for much earlier). Also, fix all tight inb loops to do cpu_relax(). A similar patch is being discussed with Jason Wessel for the mainline KDB. He brought up the point of stray make/break codes getting introduced (from the enter) on KDB exit, which is a problem that doesn't exist in mainline KDB (input device is reset). For LKDB, I could see that this can happen, although I haven't seen any strange behavior per se. I wanted to get some feedback before I modified kdba_local_arch_cleanup to flush the RX FIFO. Tested on ESX 5.0 and QEMU. Signed-off-by: Andrei Warkentin <andreiw(a)vmware.com> --- arch/x86/kdb/kdba_io.c | 67 ++++++++++++++++++++---------------------------- 1 files changed, 28 insertions(+), 39 deletions(-) diff --git a/arch/x86/kdb/kdba_io.c b/arch/x86/kdb/kdba_io.c index 8fdf59c..39cd7ce 100644 --- a/arch/x86/kdb/kdba_io.c +++ b/arch/x86/kdb/kdba_io.c @@ -46,10 +46,12 @@ static void kdb_kbdsend(unsigned char byte) { int timeout; - for (timeout = 200 * 1000; timeout && (inb(KBD_STATUS_REG) & KBD_STAT_IBF); timeout--); + for (timeout = 200 * 1000; timeout && (inb(KBD_STATUS_REG) & KBD_STAT_IBF); timeout--) + cpu_relax(); outb(byte, KBD_DATA_REG); udelay(40); - for (timeout = 200 * 1000; timeout && (~inb(KBD_STATUS_REG) & KBD_STAT_OBF); timeout--); + for (timeout = 200 * 1000; timeout && (~inb(KBD_STATUS_REG) & KBD_STAT_OBF); timeout--) + cpu_relax(); inb(KBD_DATA_REG); udelay(40); } @@ -281,31 +283,6 @@ static int get_kbd_char(void) } if ((scancode & 0x7f) == 0x1c) { - /* - * enter key. All done. Absorb the release scancode. - */ - while ((inb(KBD_STATUS_REG) & KBD_STAT_OBF) == 0) - ; - - /* - * Fetch the scancode - */ - scancode = inb(KBD_DATA_REG); - scanstatus = inb(KBD_STATUS_REG); - - while (scanstatus & KBD_STAT_MOUSE_OBF) { - scancode = inb(KBD_DATA_REG); - scanstatus = inb(KBD_STATUS_REG); - } - - if (scancode != 0x9c) { - /* - * Wasn't an enter-release, why not? - */ - lkdb_printf("kdb: expected enter got 0x%x status 0x%x\n", - scancode, scanstatus); - } - lkdb_printf("\n"); return 13; } @@ -376,21 +353,27 @@ void kdba_local_arch_setup(void) if (!kdb_check_kbd_exists()) return; - while (kbd_read_status() & KBD_STAT_IBF); + while (kbd_read_status() & KBD_STAT_IBF) + cpu_relax(); kbd_write_command(KBD_CCMD_READ_MODE); mdelay(1); - while (kbd_read_status() & KBD_STAT_IBF); + while (kbd_read_status() & KBD_STAT_IBF) + cpu_relax(); for (timeout = 200 * 1000; timeout && - (!(kbd_read_status() & KBD_STAT_OBF)); timeout--); + (!(kbd_read_status() & KBD_STAT_OBF)); timeout--) + cpu_relax(); c = kbd_read_input(); c &= ~KBD_MODE_KBD_INT; - while (kbd_read_status() & KBD_STAT_IBF); + while (kbd_read_status() & KBD_STAT_IBF) + cpu_relax(); kbd_write_command(KBD_CCMD_WRITE_MODE); mdelay(1); - while (kbd_read_status() & KBD_STAT_IBF); + while (kbd_read_status() & KBD_STAT_IBF) + cpu_relax(); kbd_write_output(c); mdelay(1); - while (kbd_read_status() & KBD_STAT_IBF); + while (kbd_read_status() & KBD_STAT_IBF) + cpu_relax(); mdelay(1); #endif /* CONFIG_VT_CONSOLE */ } @@ -404,21 +387,27 @@ void kdba_local_arch_cleanup(void) if (!kdb_check_kbd_exists()) return; - while (kbd_read_status() & KBD_STAT_IBF); + while (kbd_read_status() & KBD_STAT_IBF) + cpu_relax(); kbd_write_command(KBD_CCMD_READ_MODE); mdelay(1); - while (kbd_read_status() & KBD_STAT_IBF); + while (kbd_read_status() & KBD_STAT_IBF) + cpu_relax(); for (timeout = 200 * 1000; timeout && - (!(kbd_read_status() & KBD_STAT_OBF)); timeout--); + (!(kbd_read_status() & KBD_STAT_OBF)); timeout--) + cpu_relax(); c = kbd_read_input(); c |= KBD_MODE_KBD_INT; - while (kbd_read_status() & KBD_STAT_IBF); + while (kbd_read_status() & KBD_STAT_IBF) + cpu_relax(); kbd_write_command(KBD_CCMD_WRITE_MODE); mdelay(1); - while (kbd_read_status() & KBD_STAT_IBF); + while (kbd_read_status() & KBD_STAT_IBF) + cpu_relax(); kbd_write_output(c); mdelay(1); - while (kbd_read_status() & KBD_STAT_IBF); + while (kbd_read_status() & KBD_STAT_IBF) + cpu_relax(); mdelay(1); #endif /* CONFIG_VT_CONSOLE */ } -- 1.7.8.3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 years

[opensuse-kernel] [PATCH 1/2] acer-wmi: No wifi rfkill on Lenovo machines

by Lee, Chun-Yi

From: Ike Panhc <ike.pan(a)canonical.com> Git-commit: 461e74377cfcfc2c0d6bbdfa8fc5fbc21b052c2a Patch-mainline: v3.3-rc8 References: bnc#745236 We have several reports which says acer-wmi is loaded on ideapads and register rfkill for wifi which can not be unblocked. Since ideapad-laptop also register rfkill for wifi and it works reliably, it will be fine acer-wmi is not going to register rfkill for wifi once VPC2004 is found. Also put IBM0068/LEN0068 in the list. Though thinkpad_acpi has no wifi rfkill capability, there are reports which says acer-wmi also block wireless on Thinkpad E520/E420. Signed-off-by: Ike Panhc <ike.pan(a)canonical.com> Signed-off-by: Matthew Garrett <mjg(a)redhat.com> Acked-by: Lee, Chun-Yi <jlee(a)suse.com> --- drivers/platform/x86/acer-wmi.c | 30 +++++++++++++++++++++++++++++- 1 file changed, 29 insertions(+), 1 deletion(-) --- a/drivers/platform/x86/acer-wmi.c +++ b/drivers/platform/x86/acer-wmi.c @@ -668,6 +668,32 @@ static acpi_status AMW0_find_mailled(voi return AE_OK; } +static int AMW0_set_cap_acpi_check_device_found; + +static acpi_status AMW0_set_cap_acpi_check_device_cb(acpi_handle handle, + u32 level, void *context, void **retval) +{ + AMW0_set_cap_acpi_check_device_found = 1; + return AE_OK; +} + +static const struct acpi_device_id norfkill_ids[] = { + { "VPC2004", 0}, + { "IBM0068", 0}, + { "LEN0068", 0}, + { "", 0}, +}; + +static int AMW0_set_cap_acpi_check_device(void) +{ + const struct acpi_device_id *id; + + for (id = norfkill_ids; id->id[0]; id++) + acpi_get_devices(id->id, AMW0_set_cap_acpi_check_device_cb, + NULL, NULL); + return AMW0_set_cap_acpi_check_device_found; +} + static acpi_status AMW0_set_capabilities(void) { struct wmab_args args; @@ -681,7 +707,9 @@ static acpi_status AMW0_set_capabilities * work. */ if (wmi_has_guid(AMW0_GUID2)) { - interface->capability |= ACER_CAP_WIRELESS; + if ((quirks != &quirk_unknown) || + !AMW0_set_cap_acpi_check_device()) + interface->capability |= ACER_CAP_WIRELESS; return AE_OK; } -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 years, 1 month

[opensuse-kernel] [PATCH] config: disable CONFIG_COMPAT_VDSO to allow better ASLR

by Marcus Meissner

Hi, This should be pretty safe these days. for master branch in relation to FATE#313171 (other patch upcoming) Ciao, Marcus --- config/i386/debug | 2 +- config/i386/default | 2 +- config/i386/desktop | 2 +- config/i386/ec2 | 2 +- config/i386/pae | 2 +- config/i386/trace | 2 +- config/i386/vanilla | 2 +- config/i386/xen | 2 +- config/x86_64/debug | 2 +- config/x86_64/default | 2 +- config/x86_64/desktop | 2 +- config/x86_64/ec2 | 2 +- config/x86_64/trace | 2 +- config/x86_64/vanilla | 2 +- config/x86_64/xen | 2 +- 15 files changed, 15 insertions(+), 15 deletions(-) diff --git a/config/i386/debug b/config/i386/debug index acb5d9f..99de895 100644 --- a/config/i386/debug +++ b/config/i386/debug @@ -507,7 +507,7 @@ CONFIG_RELOCATABLE=y CONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_USE_PERCPU_NUMA_NODE_ID=y diff --git a/config/i386/default b/config/i386/default index 6ce4ef9..4365a3b 100644 --- a/config/i386/default +++ b/config/i386/default @@ -492,7 +492,7 @@ CONFIG_RELOCATABLE=y CONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y diff --git a/config/i386/desktop b/config/i386/desktop index e39d468..c3ca482 100644 --- a/config/i386/desktop +++ b/config/i386/desktop @@ -511,7 +511,7 @@ CONFIG_RELOCATABLE=y CONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_USE_PERCPU_NUMA_NODE_ID=y diff --git a/config/i386/ec2 b/config/i386/ec2 index eb97ba5..4bf8324 100644 --- a/config/i386/ec2 +++ b/config/i386/ec2 @@ -394,7 +394,7 @@ CONFIG_SCHED_HRTICK=y CONFIG_PHYSICAL_START=0x2000 CONFIG_PHYSICAL_ALIGN=0x2000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set # diff --git a/config/i386/pae b/config/i386/pae index 3558436..f5c7a92 100644 --- a/config/i386/pae +++ b/config/i386/pae @@ -508,7 +508,7 @@ CONFIG_RELOCATABLE=y CONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_USE_PERCPU_NUMA_NODE_ID=y diff --git a/config/i386/trace b/config/i386/trace index b7461ca..e4d137c 100644 --- a/config/i386/trace +++ b/config/i386/trace @@ -508,7 +508,7 @@ CONFIG_RELOCATABLE=y CONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_USE_PERCPU_NUMA_NODE_ID=y diff --git a/config/i386/vanilla b/config/i386/vanilla index 2e43b28..bfaa572 100644 --- a/config/i386/vanilla +++ b/config/i386/vanilla @@ -482,7 +482,7 @@ CONFIG_RELOCATABLE=y CONFIG_X86_NEED_RELOCS=y CONFIG_PHYSICAL_ALIGN=0x200000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y diff --git a/config/i386/xen b/config/i386/xen index 7208992..404d807 100644 --- a/config/i386/xen +++ b/config/i386/xen @@ -419,7 +419,7 @@ CONFIG_KEXEC=y CONFIG_PHYSICAL_START=0x2000 CONFIG_PHYSICAL_ALIGN=0x2000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set # diff --git a/config/x86_64/debug b/config/x86_64/debug index 67ff4b6..b9c5ee9 100644 --- a/config/x86_64/debug +++ b/config/x86_64/debug @@ -469,7 +469,7 @@ CONFIG_PHYSICAL_START=0x200000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y diff --git a/config/x86_64/default b/config/x86_64/default index d1788ea..e03339b 100644 --- a/config/x86_64/default +++ b/config/x86_64/default @@ -469,7 +469,7 @@ CONFIG_PHYSICAL_START=0x200000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y diff --git a/config/x86_64/desktop b/config/x86_64/desktop index ccbb42e..c3ed65a 100644 --- a/config/x86_64/desktop +++ b/config/x86_64/desktop @@ -472,7 +472,7 @@ CONFIG_PHYSICAL_START=0x200000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y diff --git a/config/x86_64/ec2 b/config/x86_64/ec2 index 7a9333b..fa69f54 100644 --- a/config/x86_64/ec2 +++ b/config/x86_64/ec2 @@ -364,7 +364,7 @@ CONFIG_SCHED_HRTICK=y CONFIG_PHYSICAL_START=0x2000 CONFIG_PHYSICAL_ALIGN=0x2000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set # diff --git a/config/x86_64/trace b/config/x86_64/trace index 6e5578b..9bb288f 100644 --- a/config/x86_64/trace +++ b/config/x86_64/trace @@ -469,7 +469,7 @@ CONFIG_PHYSICAL_START=0x200000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y diff --git a/config/x86_64/vanilla b/config/x86_64/vanilla index 5056301..2caa327 100644 --- a/config/x86_64/vanilla +++ b/config/x86_64/vanilla @@ -457,7 +457,7 @@ CONFIG_PHYSICAL_START=0x200000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y diff --git a/config/x86_64/xen b/config/x86_64/xen index d255bbf..6b08eaf 100644 --- a/config/x86_64/xen +++ b/config/x86_64/xen @@ -389,7 +389,7 @@ CONFIG_KEXEC=y CONFIG_PHYSICAL_START=0x2000 CONFIG_PHYSICAL_ALIGN=0x2000 CONFIG_HOTPLUG_CPU=y -CONFIG_COMPAT_VDSO=y +# CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set # -- 1.7.9 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 years, 1 month

[opensuse-kernel] [PATCH] enable x220 micmute led

by Dinar Valeev

Hi, I have x220 laptop. I've found that micmute led doesn't work. I've found a patch, tested it and it works. Please apply attached patch. Thanks, Dinar

9 years, 1 month

[opensuse-kernel] openSUSE 12.1 Can Not be Used until Rebooting from Windows (Dual Boot)

by Andi Sugandi

Hi all, I post it in kernel list because the issue is resolved "automagically" after upgrading to Linux 3.3: > rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE}\n%{VENDOR}\n%{DISTRIBUTION}\n' kernel-desktop kernel-desktop-3.3.0-1.1 obs://build.opensuse.org/Kernel Kernel:stable The problem was that after (in the first) booting to openSUSE 12.1 on the Zyrex netbook(1), it seemed not responding: (1) http://www.zyrex.com/ , an Indonesia branded computer vendor [1] The system COULD enter to KDE workspace but there were no responses when moving (mouse) cursor or pressing any keyboard buttons (even when trying to go to all terminals/ttyX by pressing Ctrl+Alt FX), EXCEPT pressing the *power button* (Power Devil?): so KDE Logout dialog appeared (but still, i could not choose any actions to be selected by mouse or keyboard whether going to logout, shutdown or reboot). This would bring the system to logout after leaving KDE Logut dialog untouched in 30 seconds(?). In this stage I could safely go to shutdown the computer by pressing the power button once again. [2] Btw, this ONLY went "normal" when it powered up, it booted to Windows, then rebooting from there to boot to openSUSE 12.1. Then enter to KDE workspace just like any normal Linux computer does. [3] This also worked fine when rebooting from running openSUSE, then return to openSUSE. I'm glad that after upgrading to Linux 3.3 the problem is solved, while using the official openSUSE kernel or earlier versions (like 3.2) the problem still persist. Btw, It is actually my collage's netbook in school, so she will be happy to use openSUSE without booting first to Windows.. :) Is it known issue? What kind of info i should know if I find similar on other computer? Is it really about kernel (not desktop bug)? If so, which feature/bug fix that solves the issue (curiosity)? Thanks in advance. Best regards, -- Andi Sugandi. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 years, 1 month

[opensuse-kernel] BTRFS bug, 3.3 rc6 ..system screwed up

by Cristian Rodríguez

hi: My workstation got screwed up today, I cannot delete any file, nor write anything to the root filesystem, even though "mount" says there are a few GB free... any operation, including btrfs balance, defragment etc or "no space left on device" :-((( I think I figured out what's going on, for some reason snapper wrote snapshots to the root filesystem in a directory called ".snapshots" those apparently are filling this small ssd drive.. attempting to delete subvolumes results in two different kind of mess ;) - If I attempt to rm -rf .snapshots it says that it is read only fs -If I attempt to delete using either snapper or btrfs subvolume, the kernel oopses and the the machine freezes up, REISUB has to be used to make it run again... Unfortunaly my camera is also broken and I cannot take a photo of the crash.. aby hints appreciated,,, -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 years, 2 months

[opensuse-kernel] [PATCH] rpm: include crtsavres.o on ppc

by Marcus Meissner

Hi, This hunk lives already in SLE11-SP2, and we need it for master too: Please apply to "master". Ciao, Marcus --- rpm/kernel-binary.spec.in | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/rpm/kernel-binary.spec.in b/rpm/kernel-binary.spec.in index 8aa7d05..5451966 100644 --- a/rpm/kernel-binary.spec.in +++ b/rpm/kernel-binary.spec.in @@ -616,6 +616,12 @@ if [ %CONFIG_MODULES = y ]; then fi fi + # arch/powerpc/lib/crtsavres.o is required for building external + # modules on powerpc + if [ -f %kernel_build_dir/arch/powerpc/lib/crtsavres.o ]; then + echo arch/powerpc/lib/crtsavres.o >> %my_builddir/obj-files + fi + tar -cf - -T %my_builddir/obj-files | \ tar -xf - -C %rpm_install_dir/%cpu_arch_flavor # bnc#507084 -- 1.7.9 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 years, 2 months

[opensuse-kernel] 11.4 kernel on 12.1

by Wolfgang Rosenauer

Hi, I'm highly disappointed of 12.1 and its kernel :-( Before openSUSE 11.4 it was basically impossible to print on my local HP USB printer for several years (back to 2007 or so). With openSUSE 11.4 it finally worked (always!). Now with 12.1 I got the very same issue as in the past. Therefore the main question: Is it possible to use the 11.4 kernel on 12.1 (even if only for testing purposes)? Second: What can I do to make openSUSE finally work with my printer? Below are the log messages when the error happens. >From what I can see these are USB bus resets happening for no reason. In the past people always claimed that some hardware is broken but I do not buy that argument as 11.4 demonstrated that it can just work with 100% same hardware. With luck I can print one page at the moment before the USB bus breaks and no single event like that happened with 11.4. Any pointers? Thanks, Wolfgang Mar 6 18:37:11 Hygiea kernel: [45807.289799] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:37:11 Hygiea kernel: [45807.290418] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:37:11 Hygiea kernel: [45807.291544] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:37:11 Hygiea kernel: [45807.292428] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:37:11 Hygiea kernel: [45807.293054] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:37:11 Hygiea kernel: [45807.293926] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:37:11 Hygiea kernel: [45807.294541] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:37:11 Hygiea kernel: [45807.526456] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:37:35 Hygiea dbus-daemon[1228]: (packagekitd:21109): PackageKit-Zypp-DEBUG: zypp_backend_destroy Mar 6 18:37:42 Hygiea kernel: [45838.854035] usb 1-4: reset high speed USB device number 5 using ehci_hcd Mar 6 18:37:42 Hygiea hp[21391]: io/hpmud/musb.c 1043: bulk_write failed buf=0x7fff7b5aed40 size=8192 len=-34: Success Mar 6 18:37:42 Hygiea hp[21391]: io/hpmud/musb.c 1423: unable to write data hp:/usb/Officejet_6300_series?serial=CN69DCH2GW04M4: Success Mar 6 18:37:42 Hygiea kernel: [45838.969179] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:37:42 Hygiea kernel: [45838.969189] usb 1-4: usbfs: process 21391 (hp) did not claim interface 1 before use Mar 6 18:37:54 Hygiea kernel: [45850.923618] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:37:56 Hygiea kernel: [45852.924164] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:37:58 Hygiea kernel: [45854.924664] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:00 Hygiea kernel: [45856.925197] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:01 Hygiea kernel: [45857.375039] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:01 Hygiea kernel: [45857.375641] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:01 Hygiea kernel: [45857.376770] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:01 Hygiea kernel: [45857.377515] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:01 Hygiea kernel: [45857.378140] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:01 Hygiea kernel: [45857.379028] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:01 Hygiea kernel: [45857.379637] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:01 Hygiea kernel: [45857.609801] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:32 Hygiea kernel: [45888.838037] usb 1-4: reset high speed USB device number 5 using ehci_hcd Mar 6 18:38:32 Hygiea hp[21613]: io/hpmud/musb.c 1043: bulk_write failed buf=0x7fffc0083ec0 size=8192 len=-34: Success Mar 6 18:38:32 Hygiea hp[21613]: io/hpmud/musb.c 1423: unable to write data hp:/usb/Officejet_6300_series?serial=CN69DCH2GW04M4: Success Mar 6 18:38:32 Hygiea kernel: [45888.953228] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:32 Hygiea kernel: [45888.953237] usb 1-4: usbfs: process 21613 (hp) did not claim interface 1 before use Mar 6 18:38:47 Hygiea kernel: [45904.055111] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:49 Hygiea kernel: [45906.055536] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:51 Hygiea kernel: [45908.056053] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:53 Hygiea kernel: [45910.056555] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:54 Hygiea kernel: [45910.488905] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:54 Hygiea kernel: [45910.489512] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:54 Hygiea kernel: [45910.490387] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:54 Hygiea kernel: [45910.491034] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:54 Hygiea kernel: [45910.491512] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:54 Hygiea kernel: [45910.492523] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:54 Hygiea kernel: [45910.493139] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:38:54 Hygiea kernel: [45910.712807] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:39:25 Hygiea kernel: [45941.830032] usb 1-4: reset high speed USB device number 5 using ehci_hcd Mar 6 18:39:25 Hygiea hp[21952]: io/hpmud/musb.c 1043: bulk_write failed buf=0x7ffffb0b5d10 size=8192 len=-34: Success Mar 6 18:39:25 Hygiea hp[21952]: io/hpmud/musb.c 1423: unable to write data hp:/usb/Officejet_6300_series?serial=CN69DCH2GW04M4: Success Mar 6 18:39:25 Hygiea kernel: [45941.944987] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:39:25 Hygiea kernel: [45941.944996] usb 1-4: usbfs: process 21952 (hp) did not claim interface 1 before use Mar 6 18:39:31 Hygiea hp-toolbox: hp-toolbox[22258]: warning: Reportlab not installed. Fax coverpages disabled. Mar 6 18:39:31 Hygiea hp-toolbox: hp-toolbox[22258]: warning: Please install version 2.0+ of Reportlab for coverpage support. Mar 6 18:39:32 Hygiea hp[21952]: io/hpmud/musb.c 1043: bulk_write failed buf=0x7ffffb0b5d10 size=8192 len=-34: Success Mar 6 18:39:32 Hygiea kernel: [45948.423907] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:39:32 Hygiea hp[21952]: io/hpmud/musb.c 1423: unable to write data hp:/usb/Officejet_6300_series?serial=CN69DCH2GW04M4: Success Mar 6 18:39:32 Hygiea hp[21952]: io/hpmud/musb.c 749: invalid deviceid ret=-5: Input/output error Mar 6 18:39:32 Hygiea kernel: [45948.424048] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:39:32 Hygiea kernel: [45948.424058] usb 1-4: usbfs: process 21952 (hp) did not claim interface 1 before use Mar 6 18:39:32 Hygiea hp[21952]: prnt/backend/hp.c 625: ERROR: 5021 device communication error! Mar 6 18:39:32 Hygiea kernel: [45948.424352] usb 1-4: usbfs: process 21952 (hp) did not claim interface 1 before use Mar 6 18:39:32 Hygiea kernel: [45948.424904] Did not find alt setting 1 for intf 0, config 1 Mar 6 18:39:32 Hygiea kernel: [45948.425660] Did not find alt setting 1 for intf 0, config 1 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 years, 2 months

[opensuse-kernel] eth0 and dbus problems after upgrade to 12.1

by Dave Plater

Already sent to opensuse list with no reply yet. I updated via 12.1 x86_64 dvd and because I maintain multimedia, I included a few build service repos in thye upgrade. I used zypper dup from 11.3 to 11.4 without problems but this time there are problems which I assume stem from /var/run being a tempfs. I've searched threads on this list and factory list and googling only brought up similar Ubuntu problems but no real help. First problem was having to manually "ifup eth0" to get my network going, I've fixed that with adding "ifup eth0" to "/etc/init.d/boot.local" but the other problem has me stumped. As kde is starting it halts on a message box stating a similar message to this syslog one, clicking ok continues to desktop : pam_systemd(xdm-np:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Thinking that this was caused by the tempfs I also created the dbus directory in boot.local but it doesn't fix anything. I'm surprised that no one has reported a bug and it seems I'm the only one to have this problem, it's maybe leftover from my 11.4 kernel getting mangled when I recompiled with certain extra cdc_phonenet options and then when I updated my non openSUSE VirtualBox-4.1 to 4.1.8 my network died. I fixed this with the 11.4 tumbleweed kernel. Please help, here's a section of my /var/log/messages with lots of the above error message and my boot.msg is at http://pastebin.com/Zpn9AnTp , I'm a bit nervous using pastebin for this so it expires after one day. : Mar 7 10:56:02 Arbuthnot kdm: :0[2184]: pam_systemd(xdm-np:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 10:56:04 Arbuthnot checkproc: checkproc: can not get session id for process 2396! Mar 7 10:56:50 Arbuthnot kernel: [ 5373.607165] fuse init (API version 7.17) Mar 7 10:56:50 Arbuthnot mount[3411]: mount: fusectl already mounted or /sys/fs/fuse/connections busy Mar 7 10:56:50 Arbuthnot mount[3411]: mount: according to mtab, fusectl is already mounted on /sys/fs/fuse/connections Mar 7 10:56:50 Arbuthnot systemd[1]: sys-fs-fuse-connections.mount mount process exited, code=exited status=32 Mar 7 10:57:14 Arbuthnot sudo: davepl : TTY=pts/2 ; PWD=/home/davepl ; USER=root ; COMMAND=/usr/bin/tailf /var/log/messages Mar 7 10:57:15 Arbuthnot sudo: pam_systemd(sudo:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 10:57:14 Arbuthnot sudo: davepl : TTY=pts/2 ; PWD=/home/davepl ; USER=root ; COMMAND=/usr/bin/tailf /var/log/messages Mar 7 10:57:15 Arbuthnot sudo: pam_systemd(sudo:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 10:57:40 Arbuthnot su: (to root) davepl on /dev/pts/1 Mar 7 10:57:40 Arbuthnot su: pam_systemd(su:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 11:15:09 Arbuthnot logrotate: ALERT exited abnormally with [1] Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/log/atftpd" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/lib/mailman/logs" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 logrotate: last message repeated 11 times Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/lib/privoxy/log" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/lib/privoxy/log" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/log/quagga" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 logrotate: last message repeated 5 times Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/log/squid" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 logrotate: last message repeated 2 times Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/log/squidGuard" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 Arbuthnot logrotate: error: "/var/log/news" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file. Mar 7 11:15:09 logrotate: last message repeated 2 times Mar 7 11:15:09 Arbuthnot run-crons[3889]: logrotate: OK Mar 7 11:15:09 Arbuthnot run-crons[3889]: suse-clean_catman: OK Mar 7 11:15:19 Arbuthnot run-crons[3889]: suse-do_mandb: OK Mar 7 11:16:05 Arbuthnot run-crons[3889]: suse-texlive: OK Mar 7 11:16:06 Arbuthnot su: (to nobody) root on none Mar 7 11:16:06 Arbuthnot su: pam_systemd(su:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 11:16:06 Arbuthnot su: (to nobody) root on none Mar 7 11:16:06 Arbuthnot su: pam_systemd(su:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 11:16:06 Arbuthnot su: (to nobody) root on none Mar 7 11:16:06 Arbuthnot su: pam_systemd(su:session): Failed to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Mar 7 11:22:22 Arbuthnot run-crons[3889]: suse-updatedb: OK Mar 7 11:22:22 Arbuthnot run-crons[3889]: suse.cron-sa-update: OK Mar 7 11:22:25 Arbuthnot run-crons[3889]: suse.de-backup-rc.config: OK Mar 7 11:22:48 Arbuthnot run-crons[3889]: suse.de-backup-rpmdb: OK Mar 7 11:22:49 Arbuthnot run-crons[3889]: suse.de-check-battery: OK Mar 7 11:22:49 Arbuthnot run-crons[3889]: suse.de-clean-tmp: OK Mar 7 11:22:49 Arbuthnot run-crons[3889]: suse.de-cron-local: OK Mar 7 11:26:40 Arbuthnot run-crons[3889]: suse.de-rkhunter: OK Mar 7 11:26:40 Arbuthnot run-crons[3889]: suse.de-snapper: OK Mar 7 11:26:44 Arbuthnot run-crons[3889]: tmpwatch: OK Mar 7 11:30:01 Arbuthnot run-crons[18484]: suse.de-snapper: OK Thanks in advance for any help Dave P -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 years, 2 months

[opensuse-kernel] efika kernel

by Peter Czanik

Hello, There is a kernel config patch for the imx51 kernel from Bernhard, which are still not applied ( http://lists.opensuse.org/opensuse-kernel/2012-02/msg00036.html ). It was sent 9th February, and the latest imx51 kernel is a few weeks older: czanik@linux-6965:/tmp> rpm -qp --changelog kernel-imx51-3.2.0-2.2.armv7l.rpm | head warning: kernel-imx51-3.2.0-2.2.armv7l.rpm: Header V3 DSA/SHA1 Signature, key ID a4e5a8f4: NOKEY * Wed Jan 25 2012 dkukawka(a)suse.de - fix NULL pointer dereference in DSS2 VENC sysfs debug attr on OMAP4. - commit 2206a5c * Wed Jan 25 2012 mmarek(a)suse.cz - proc: clean up and fix /proc/<pid>/mem handling (bnc#742279, CVE-2012-0056). - commit 4fb112d Could you apply it? Even without graphics, it's more useful, than the current one... Bye, CzP -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 years, 2 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openSUSE Kernel March 2012