May 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 797966] New: pm-utils intel-audio-powersave script error results in logging errors in pm-powersave.log
by bugzilla_noreply＠novell.com 02 May '13

02 May '13

https://bugzilla.novell.com/show_bug.cgi?id=797966 https://bugzilla.novell.com/show_bug.cgi?id=797966#c0 Summary: pm-utils intel-audio-powersave script error results in logging errors in pm-powersave.log Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: d_werner(a)gmx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 The script /usr/lib/pm-utils/power.d/intel-audio-powersave contains errors which result in error entries in /var/log/pm-powersave.log The problem exists in pm-utils-1.4.1-18.6.1.x86_64 (current version of openSUSE 12.2) and also in pm-utils-1.4.1-24.2.x86_64 (current version of openSUSE factory/12.3MS2). The faulty log entry looks like this: Running hook /usr/lib/pm-utils/power.d/intel-audio-powersave false: /usr/lib/pm-utils/power.d/intel-audio-powersave: line 25: printf: {/sys/module/snd_ac97_codec##*/}: invalid number Setting power savings for to 0...Setting power savings for to 0...Done. following patch solves the problem: 25c25 < printf "Setting power savings for %s to %d..." "${dev##*/}" "$1" --- > printf "Setting power savings for $s to %d..." "{$dev##*/}" "$1" With this patch the log entry looks like this: /usr/lib/pm-utils/power.d/hal-cd-polling false: success. Running hook /usr/lib/pm-utils/power.d/intel-audio-powersave false: Setting power savings for snd_ac97_codec to 0...Done. Reproducible: Always Steps to Reproduce: 1.audio hardware detected by the script exists /sys/module/snd_* 2.intel-audio-powersave must apply settings (e.g. at system startup) 3.check /var/log/pm-powersave.log Actual Results: log data in /var/log/pm-powersave.log: Running hook /usr/lib/pm-utils/power.d/intel-audio-powersave false: /usr/lib/pm-utils/power.d/intel-audio-powersave: line 25: printf: {/sys/module/snd_ac97_codec##*/}: invalid number Setting power savings for to 0...Setting power savings for to 0...Done. Expected Results: no errors in /var/log/pm-powersave.log, correct devicename. patch for /usr/lib/pm-utils/power.d/intel-audio-powersave 25c25 < printf "Setting power savings for %s to %d..." "${dev##*/}" "$1" --- > printf "Setting power savings for $s to %d..." "{$dev##*/}" "$1" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 782891] New: Unify grub2 and grub2-efi package
by bugzilla_noreply＠novell.com 02 May '13

02 May '13

https://bugzilla.novell.com/show_bug.cgi?id=782891 https://bugzilla.novell.com/show_bug.cgi?id=782891#c0 Summary: Unify grub2 and grub2-efi package Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: arvidjaar(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 Current split between grub2 and grub2-efi is confusing. Configuration files appear in different directories (/boot/grub2 and /boot/grub2-efi), moreover, they are split between both for grub2-efi. Command names are rather unexpected - if grub2 prefix is more or less known, grub2-efi comes as surprise. Separate prefix for grub2 and grub2-efi is really nor needed and more. Grub2 fully supports multi-architecture setup, and grub-install does the right thing by default. Actually, I do not think that separating grub2 and grub2-efi is required at all today. So suggestion is to merge them in single grub2 package. Or - if there are reasons not to - at least build grub2-efi with the same prefix as grub2. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 22

[Bug 633491] New: s2disk fails after upgrade from 11.2 to 11.3
by bugzilla_noreply＠novell.com 02 May '13

02 May '13

https://bugzilla.novell.com/show_bug.cgi?id=633491 https://bugzilla.novell.com/show_bug.cgi?id=633491#c0 Summary: s2disk fails after upgrade from 11.2 to 11.3 Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i586 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: lmuelle(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: No The system is a ThinkPad X31. s2disk worked with 11.2. After an upgrade to 11.3 s2disk hangs while suspend. For testing I installed the latest 11.2 kernel default (2.6.31.12-0.2-default) from the update/11.2 tree and with this version s2disk and resume works. I'm trying to gather more information by passing no_console_suspend as additional boot argument to the kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 23

[Bug 807540] New: rabbitmq-server init script does not properly daemonize
by bugzilla_noreply＠novell.com 02 May '13

02 May '13

https://bugzilla.novell.com/show_bug.cgi?id=807540 https://bugzilla.novell.com/show_bug.cgi?id=807540#c0 Summary: rabbitmq-server init script does not properly daemonize Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: rhafer(a)suse.com ReportedBy: jdsn(a)suse.com QAContact: qa-bugs(a)suse.de CC: bwiedemann(a)suse.com Found By: Development Blocker: --- Created an attachment (id=528219) --> (http://bugzilla.novell.com/attachment.cgi?id=528219) patch to use startproc Steps to reproduce: ssh root@localhost "/etc/init.d/rabbitmq-server restart ; echo \$?; date" With this call the ssh connection is never closed. Patch attached. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 815265] cannot change locale to .UTF-8 on firstboot
by bugzilla_noreply＠novell.com 02 May '13

02 May '13

https://bugzilla.novell.com/show_bug.cgi?id=815265 https://bugzilla.novell.com/show_bug.cgi?id=815265#c Jiří Suchomel <jsuchome(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |thardeck(a)suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 815265] cannot change locale to .UTF-8 on firstboot
by bugzilla_noreply＠novell.com 02 May '13

02 May '13

https://bugzilla.novell.com/show_bug.cgi?id=815265 https://bugzilla.novell.com/show_bug.cgi?id=815265#c30 --- Comment #30 from Jiří Suchomel <jsuchome(a)suse.com> 2013-05-02 07:49:00 UTC --- Created an attachment (id=537632) --> (http://bugzilla.novell.com/attachment.cgi?id=537632) new patch for /usr/share/YaST2/modules/Language.ycp OK, let's add also this patch for Language.ycp fix the 'detection' of UTF environment. You need both: patch for language.sh (part of yast2-installation) and this one for Language.ycp (including new Language.ybc, part of yast2-country) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 808680] New: mokutil looks into wrong path
by bugzilla_noreply＠novell.com 02 May '13

02 May '13

https://bugzilla.novell.com/show_bug.cgi?id=808680 https://bugzilla.novell.com/show_bug.cgi?id=808680#c0 Summary: mokutil looks into wrong path Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: glin(a)suse.com ReportedBy: lnussel(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- # mokutil --sb-state Failed to read SecureBoot turns out it looks into /sys/firmware/efi/efivars instead of /sys/firmware/efi/vars -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 783242] New: Failure to complete remote network installation
by bugzilla_noreply＠novell.com 02 May '13

02 May '13

https://bugzilla.novell.com/show_bug.cgi?id=783242 https://bugzilla.novell.com/show_bug.cgi?id=783242#c0 Summary: Failure to complete remote network installation Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: PC OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: comes(a)naic.edu QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 On certain conditions a remote network installation does not complete. I start the installation process and I do the usual selections in the Linuxrc menu (VNC enable). Before the graphic installation menu starts I can see on the console: starting VNC server together with the list of the network interfaces I can use to connect remotely to the VNC server. I start the VNC client on another machine and perform the usual selections in the graphic menu. Then the installation of the packages start. At the end of the installation the computer reboot. After reboot on the console there is again the message to connect to the VNC server. I connect and I start the configuration process: In the Network Configuration screen General Network Settings Network Mode: I select Network Manager In the Test Internet Connection screen I select No, Skip This Test and click on Next Then a small windows appears with the text: Starting service network... and the vnc client hangs there. On the console there is the message: Dependency failed. Aborted start of Network Manager Wait Online [ ABORT ] Stopped Network Manager Wait Online [ OK ] Stopped Network Manager [ OK ] At this point it is not possible to continue the remote installation. I can continue the installation locally starting the X server (xinit /usb/bin/xterm -- :1), then the vnc client (vncviewer :1) and complete the configuration steps. Reproducible: Always Steps to Reproduce: 1.Do a network remote installation. 2.After reboot in the network configuration screen select Network Manager 3. Actual Results: The network service will fail to restart. Remote installation cannot be completed. Expected Results: Remote installation can be completed without errors. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 818064] New: [NTAP-394811] SLES 11.3 x64 SANboot host hangs during stress IO with LPe16002 HBA and DMMP failover
by bugzilla_noreply＠novell.com 02 May '13

02 May '13

https://bugzilla.novell.com/show_bug.cgi?id=818064 https://bugzilla.novell.com/show_bug.cgi?id=818064#c0 Summary: [NTAP-394811] SLES 11.3 x64 SANboot host hangs during stress IO with LPe16002 HBA and DMMP failover Classification: openSUSE Product: openSUSE 11.4 Version: RC 1 Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: luis.salmeron(a)netapp.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=537592) --> (http://bugzilla.novell.com/attachment.cgi?id=537592) Host console logs User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C) A SLES 11 SP3 RC1 x64 host installed to a SAN volume will become unresponsive after 2-3 hours of failover tesing. The error is seen when failover is caused by continuous resets of the storage array controllers, failing of switch ports, or offlining of controllers. The message "Kernel panic - not syncing: Out of memory and no killable processes..." is seen at the time of the error. The volume storing the OS had a 100GB capacity and the server had 8GB of RAM. The host bus adapter used on this server is a 16GB Exulex LPe16002. The lpfc driver being used is the inbox driver version 8.3.7.10.2p. The firmware and BIOS for the HBA are 1.1.35.0 and KA6.01a12 respectively. The inbox Device Mapper Multipath is being used which is version 0.4.9-0.77.5. The only way to release the host from its unresponsive state is to power cycle the server. The servers that have seen this problem were a Dell PowerEdge R710 and a Dell PowerEdge R720. The same OS/array scenario has been attempted with Qlogic QLe2672 HBAs, Brocade 1860 HBAs, and Emulex LPe12002 HBAs and the error was not reproduced. Reproducible: Always Steps to Reproduce: 1. Install SLES 11 SP3 RC1 x64 on a volume on a storage array through an LPe16002 HBA. During the installation, the drive should be run as a multipath device. 2. Once installed, enable DMMP and map another 64 1GB volumes from two NetApp storage arrays 3. Create ext3 filesytems on 2 of the volumes and mount them to unused directories on the OS. Run filesystem IO to these 2 targets and raw IO to the remaining 62 volumes 4. Reset or offline a controller from one of the storage arrays, wait 10 minutes, reset another controller from the other storage array or bring the offlined controller back online, wait 10 minutes, repeat these steps while always alternating arrays and controller paths. Actual Results: After 2-3 hours of stressed IO, the system would become unresponsive and could not be brought back up unless it was power cycled Expected Results: The system should have ran IO for at least 16 hours without errors while the storage arrays continued their resets or offline/online tests. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 733283] New: mdadm -- incremental
by bugzilla_noreply＠novell.com 01 May '13

01 May '13

https://bugzilla.novell.com/show_bug.cgi?id=733283 https://bugzilla.novell.com/show_bug.cgi?id=733283#c0 Summary: mdadm -- incremental Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: petr.m(a)seznam.cz QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Win64; x64; Trident/5.0) During boot I've got this error udevd [201]: failed to execute '/sbin/mdadm' '/sbin/mdadm --incremental /dev/sda1': No such file or directory udevd [205]: failed to execute '/sbin/mdadm' '/sbin/mdadm --incremental /dev/sdb1': No such file or directory udevd [208]: failed to execute '/sbin/mdadm' '/sbin/mdadm --incremental /dev/sdc1': No such file or directory udevd [209]: failed to execute '/sbin/mdadm' '/sbin/mdadm --incremental /dev/sdd1': No such file or directory Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 41