July 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 637235] New: kernel:huh, entered softirq 3 NET_RX ffffffff813d1a10 preempt_count 00000102, exited with 00000103?
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637235 https://bugzilla.novell.com/show_bug.cgi?id=637235#c0 Summary: kernel:huh, entered softirq 3 NET_RX ffffffff813d1a10 preempt_count 00000102, exited with 00000103? Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: crrodriguez(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: No Using Kernel:HEAD http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.3/ I get this message repeteadly, machine takes ages to boot or simple freezes. "kernel: [ 1295.239519] huh, entered softirq 3 NET_RX ffffffff813d1a10 preempt_count 00000102, exited with 00000103?" all accompanied with this crash: <6>[ 8.068993] PCI: Discovered peer bus ff <1>[ 8.070635] BUG: unable to handle kernel NULL pointer dereference at 00000000000001a4 <1>[ 8.070860] IP: [<ffffffffa01cee78>] edac_create_mci_instance_attributes+0xe8/0x1a0 [edac_core] <4>[ 8.071055] PGD 13e7d3067 PUD 13c840067 PMD 0 <0>[ 8.071251] Oops: 0000 [#1] PREEMPT SMP <0>[ 8.071445] last sysfs file: /sys/devices/pci0000:ff/0000:ff:06.0/class <4>[ 8.071548] CPU 1 <4>[ 8.071585] Modules linked in: i7core_edac(+) kvm snd_page_alloc r8169 wmi iTCO_wdt sg i2c_i801 usb_storage edac_core cfg80211 pcspkr button serio_raw rfkill iTCO_vendor_support ext4 jbd2 crc16 ata_generic sd_mod pata_jmicron ahci libahci libata scsi_mod fan thermal processor thermal_sys <4>[ 8.072974] <4>[ 8.073067] Pid: 548, comm: modprobe Not tainted 2.6.36-rc3-10-desktop #1 0X501H/Studio XPS 435T/9000 <4>[ 8.073227] RIP: 0010:[<ffffffffa01cee78>] [<ffffffffa01cee78>] edac_create_mci_instance_attributes+0xe8/0x1a0 [edac_core] <4>[ 8.073429] RSP: 0018:ffff88013c8c7b98 EFLAGS: 00010282 <4>[ 8.073527] RAX: 00000000000001a4 RBX: ffffffffa0109eb8 RCX: 0000000000000000 <4>[ 8.073629] RDX: ffff88013e23c0f0 RSI: ffffffffa01d43c0 RDI: ffff88013f3c5450 <4>[ 8.073732] RBP: ffff88013f3c5440 R08: 0000000000000000 R09: ffff88013f3c5440 <4>[ 8.073835] R10: ffff88013fc8a450 R11: 0000000000000000 R12: ffff88013b9e5850 <4>[ 8.073937] R13: ffff88013e23c000 R14: ffff88013f3c5450 R15: ffff88013e23c130 <4>[ 8.074040] FS: 00007f3eaa833700(0000) GS:ffff880001e20000(0000) knlGS:0000000000000000 <4>[ 8.074197] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b <4>[ 8.074295] CR2: 00000000000001a4 CR3: 000000013e7d6000 CR4: 00000000000006e0 <4>[ 8.074398] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 <4>[ 8.074503] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 <4>[ 8.074607] Process modprobe (pid: 548, threadinfo ffff88013c8c6000, task ffff88013c34e6c0) <0>[ 8.074765] Stack: <4>[ 8.074856] ffff88013c8c7ba8 0000000000000000 ffff88013e23c0f0 ffff88013c8c7fd8 <4>[ 8.075056] <0> ffff88013c0f0460 ffffffffa0109dc8 ffff88013b9e5840 ffff88013e23c0f0 <4>[ 8.075371] <0> ffff88013e23c000 ffff88013b9e5850 ffff88013e23c130 ffffffffa01cee99 <0>[ 8.075778] Call Trace: <4>[ 8.075881] [<ffffffffa01cee99>] edac_create_mci_instance_attributes+0x109/0x1a0 [edac_core] <4>[ 8.076039] [<ffffffffa01cf7b4>] edac_create_sysfs_mci_device+0x64/0x150 [edac_core] <4>[ 8.076197] [<ffffffffa01cdbf6>] edac_mc_add_mc+0x36/0xe0 [edac_core] <4>[ 8.076296] [<ffffffffa0108144>] i7core_register_mci+0x104/0x210 [i7core_edac] <4>[ 8.076450] [<ffffffffa01087c3>] i7core_probe+0x10e/0x185 [i7core_edac] <4>[ 8.076552] [<ffffffff81277515>] local_pci_probe+0x55/0xd0 <4>[ 8.076649] [<ffffffff812786e2>] pci_device_probe+0x132/0x140 <4>[ 8.076747] [<ffffffff81320bb0>] really_probe+0x70/0x260 <4>[ 8.076844] [<ffffffff81320fa7>] driver_probe_device+0x47/0xb0 <4>[ 8.076941] [<ffffffff813210a3>] __driver_attach+0x93/0xa0 <4>[ 8.077036] [<ffffffff8131faee>] bus_for_each_dev+0x4e/0x80 <4>[ 8.077132] [<ffffffff813204f0>] bus_add_driver+0x160/0x330 <4>[ 8.077228] [<ffffffff813212fa>] driver_register+0x6a/0x130 <4>[ 8.077325] [<ffffffff8127895c>] __pci_register_driver+0x4c/0xc0 <4>[ 8.077422] [<ffffffffa010f086>] i7core_init+0x86/0xa8 [i7core_edac] <4>[ 8.077523] [<ffffffff810002da>] do_one_initcall+0x3a/0x170 <4>[ 8.077621] [<ffffffff8109396a>] sys_init_module+0xba/0x210 <4>[ 8.077717] [<ffffffff8100303b>] system_call_fastpath+0x16/0x1b <4>[ 8.077815] [<00007f3eaa19aeda>] 0x7f3eaa19aeda <0>[ 8.077907] Code: 10 4c 89 7d 00 48 8b 54 24 10 48 c7 c6 c0 43 1d a0 4c 89 f7 48 89 45 08 48 89 28 48 8b 43 10 4c 89 6d 58 48 89 45 50 48 8b 43 10 <48> 8b 08 31 c0 e8 4e 8b 08 e1 85 c0 75 22 48 8b 45 50 4c 89 f2 <1>[ 8.080114] RIP [<ffffffffa01cee78>] edac_create_mci_instance_attributes+0xe8/0x1a0 [edac_core] <4>[ 8.080299] RSP <ffff88013c8c7b98> <0>[ 8.080389] CR2: 00000000000001a4 <4>[ 8.080484] ---[ end trace e37de668754c1f33 ]--- went back to stable kernel, but if you need more info, I might try to get it. -- 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 13

[Bug 637201] New: YaST Package Manager: window saying ''Starting Package Manager'' when closing YaST
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637201 https://bugzilla.novell.com/show_bug.cgi?id=637201#c0 Summary: YaST Package Manager: window saying ''Starting Package Manager'' when closing YaST Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: marcos(a)meebee.ven.bz QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.9.0.15) Gecko/2009102815 Ubuntu/9.04 (jaunty) Firefox/3.0.15 Versions: openSUSE 11.3 KDE 4.4.4 YaST Packager 2.19.7-1.5 Libzypp 7.7.5-7.2 ================================================================================= Problem: I opened YaST for removing some packages, but then I decided to close it. There were some conflicts so I passed. When closing, a window stating ''Starting Package Manager'' appears. I don't know the exact sentence (my openSUSE 11.3 is in Spanish). After 1 or 2 seconds, it disappears. I know this isn't very annoying, but, why don't YaST close quickly without ''Starting Package Manager''? Thanks! Reproducible: Always Steps to Reproduce: 1. Open YaST package manager 2. Close it by clicking X in the title bar. Actual Results: The ''Starting Package Manager'' window Expected Results: No window, just YaST closed instead. -- 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 637187] New: rpmlint/post-build-checks: %run_ldconfig gives incomplete warning message
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637187 https://bugzilla.novell.com/show_bug.cgi?id=637187#c0 Summary: rpmlint/post-build-checks: %run_ldconfig gives incomplete warning message Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- aufs.src:98: W: deprecated-use-of-%run_ldconfig aufs.src:104: W: deprecated-use-of-%run_ldconfig According to the new SUSE Packaging Conventions, the use of %run_ldconfig is deprecated. use %post(un) -p /sbin/ldconfig instead. But my %post section reads %post [ -x /sbin/mkinitrd_setup ] && /sbin/mkinitrd_setup %run_ldconfig So doing %post -p is not a good idea, because ldconfig cannot run mkinitrd_setup. -- 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 637183] New: /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637183 https://bugzilla.novell.com/show_bug.cgi?id=637183#c0 Summary: /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: martin(a)oneiros.de QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=387614) --> (http://bugzilla.novell.com/attachment.cgi?id=387614) boot.msg User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 At bootup I get these messages: ------------------ <notice -- Sep 4 15:27:57.953566000> service earlyxdm doneStarting service kdmdone Setting up (localfs) network interfaces: lo lo IP address: 127.0.0.1/8 IP address: 127.0.0.2/8 lo done eth0 device: Broadcom Corporation NetXtreme BCM5755M Gigabit Ethernet PCI Express (rev 02) eth0 is controlled by ifplugd eth0 waiting wlan0 device: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) wlan0 is controlled by ifplugd wlan0 waiting eth0 device: Broadcom Corporation NetXtreme BCM5755M Gigabit Ethernet PCI Express (rev 02) eth0 ifplugd is running eth0 no cable connected eth0 . . . is just beeing set up eth0 done wlan0 device: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) wlan0 ifplugd is running /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument /etc/sysconfig/network/scripts/ifplugd-selectif: line 40: read: read error: 0: Invalid argument wlan0 no cable connected wlan0 . . . is just beeing set up wlan0 is down wlan0 ------------------ dmesg etc. are attached. The wlan is disabled via kill switch. 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 23

[Bug 637069] New: gdm: Unable to Connect with XDMCP (thin clients)
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637069 https://bugzilla.novell.com/show_bug.cgi?id=637069#c0 Summary: gdm: Unable to Connect with XDMCP (thin clients) Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: drichard(a)largo.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b4) Gecko/20100818 Firefox/4.0b4 gdm was broken and did not allow XDMCP connections in 11.3 Halfline cooked a patch and I was able to get it to merge and compile and it indeed is now working. I'm uploading the two patches along with the updated gdm.spec file. They are listed as Patch98 and Patch99 in the spec. 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 14

[Bug 636980] New: closing window of live installer have strange effect
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=636980 https://bugzilla.novell.com/show_bug.cgi?id=636980#c0 Summary: closing window of live installer have strange effect Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: aschnell(a)novell.com QAContact: jsrain(a)novell.com Found By: Development Blocker: --- When trying to close the window of the live installer on the KDE Live CD using the button with a x of the window decoration the window does not close. Instead, when you are at the "Live Installation Setting" and press the close button you get back to the "Create New User" dialog. Pressing the button again presents a popup stating that the computer must be rebooted. At least after selecting "Reboot Later" the YaST window finally disappears. -- 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 636347] New: [virtualbox-ose-guest-tools] 'mount -t vboxsf' fails due to packaging bug
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=636347 https://bugzilla.novell.com/show_bug.cgi?id=636347#c0 Summary: [virtualbox-ose-guest-tools] 'mount -t vboxsf' fails due to packaging bug Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ma(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- # mount -t vboxsf myshare /Local mount: wrong fs type, bad option, bad superblock on to, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program) ^^^^^^^^^^^^^^^^^^ The virtualbox-ose-guest-tools specfile uses %{sbindir}/mount.vboxsf, but that's /usr/sbin, so mount does not recognize it. # rpm -ql virtualbox-ose-guest-tools -i Name : virtualbox-ose-guest-tools Relocations: (not relocatable) Version : 3.2.6 Vendor: openSUSE Release : 1.4 Build Date: Mon 05 Jul 2010 . /usr/sbin/mount.vboxsf !!!!!!!!!!!!!!!!!!!!!! WORKAROUND: mv /usr/sbin/mount.vboxsf /sbin -- 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 11

[Bug 636083] New: YaST2 scanner configuration don't closes automatically after particular scanner configuration
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=636083 https://bugzilla.novell.com/show_bug.cgi?id=636083#c0 Summary: YaST2 scanner configuration don't closes automatically after particular scanner configuration Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: embar(a)super.lt QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=386678) --> (http://bugzilla.novell.com/attachment.cgi?id=386678) This is window, that I must close manually after finishing of particular scanner User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; lt; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 YaST2 window of particular (not overall) scanner configuration don't closes automatically, so I must to close it manually. Reproducible: Always Steps to Reproduce: 1. Open YaST2 scanner configuration module 2. Select scanner 3. Press button to configure it 4. Select vendor/model 5. Confirm selection 6. Wait while configuring Actual Results: I can wait many minutes after finishing of configuration. I must manually close progress window. After manual closing, I see main YaST2 window for scanner configuration. Expected Results: After configuration, dialog window closes automatically, and I see main YaST2 window for scanner configuration. -- 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 635920] New: hdparm v9.28 does not work with OCZ Vertex 2E SSD
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=635920 https://bugzilla.novell.com/show_bug.cgi?id=635920#c0 Summary: hdparm v9.28 does not work with OCZ Vertex 2E SSD Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Greg.Freemyer(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 Please upgrade oS 11.2 and 11.3 to hdparm v9.30 available on sourceforge. == background for request This bug relates to the hdparm --trim-sector-ranges-stdin capability which is invoked by the wiper.sh script which is also part of the hdparm package. Support for wiper.sh and hdparm --trim-sector-ranges-stdin is included in both openSUSE 11.2 and 11.3. Thomas Hertweck <Thomas.Hertweck at web.de> reported: > I have now installed openSUSE 11.3 on a OCZ Vertex 2E SSD. I used a > standard ext4 filesystem, the mount options at the moment are > "rw,noatime,acl,user_xattr". Unfortunately, wiper.sh doesn't work at all. > > No joy, obviously. I have asked Mark Lord (the hdparm maintainer) for feedback. He said the default max TRIM payload sent via hdparm has been lowered in the latest release of hdparm v2.30 and recommended we upgrade and see if it fixes the problem Reproducible: Always Steps to Reproduce: 1. Run wiper.sh against a Ext4 FS on a OCZ Vertex 2E SSD 2. 3. Actual Results: > $> wiper.sh --verbose --commit /dev/sdb1 > wiper.sh: Linux SATA SSD TRIM utility, version 2.6, by Mark Lord. > wiper.sh: This tool is DANGEROUS! Please read and understand > wiper.sh: /usr/share/doc/packages/hdparm/README.wiper > wiper.sh: before going any further. > rootdev=/dev/sdb1 > fsmode2: fsmode=read-write > /: fstype=ext4 > freesize = 45338732 KB, reserved = 453387 KB > Preparing for online TRIM of free space on /dev/sdb1 (ext4 mounted > read-write at /). > This operation could silently destroy your data. Are you sure (y/N)? y > Creating temporary file (44885345 KB).. > Syncing disks.. > Beginning TRIM operations.. > get_trimlist=/sbin/hdparm --fibmap WIPER_TMPFILE.13467 > /dev/sdb: > trimming 89770696 sectors from 1493 ranges > FAILED: Input/output error > Removing temporary file.. > Syncing disks.. > Aborted. Expected Results: All EXT4 unallocated space on the SSD should be "trimmed" such that the SSD can erase the unallocated sectors in advance of their being used, thus improving performance of the SSD. Note: There is a wiki entry that covers discard (trim) in openSUSE: http://en.opensuse.org/SDB:SSD_discard_%28trim%29_support Thread that originated the bug is available at: http://lists.opensuse.org/opensuse-kernel/2010-08/msg00068.html -- 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 18

[Bug 635830] New: AppArmor: ag_subdomain broken: Can't locate Immunix/Notify.pm
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=635830 https://bugzilla.novell.com/show_bug.cgi?id=635830#c0 Summary: AppArmor: ag_subdomain broken: Can't locate Immunix/Notify.pm Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: juhliarik(a)novell.com ReportedBy: mvidner(a)novell.com QAContact: jsrain(a)novell.com CC: kmachalkova(a)novell.com Found By: --- Blocker: --- $ /usr/lib/YaST2/servers_non_y2/ag_subdomain Can't locate Immunix/Notify.pm in @INC (@INC contains: [...]) at /usr/lib/YaST2/servers_non_y2/ag_subdomain line 23 yast2-apparmor contains the file as /usr/lib/perl5/vendor_perl/Immunix/Notify.pm but that path is not searched by Perl. It needs to be in vendor_perl/$VERSION/Immunix instead. I am not sure where exactly this hits the user, but surely at some point y2-apparmor calls the agent. Originally reported by ezekiellg at http://forums.opensuse.org/english/get-help-here/applications/445307-yast-p… -- 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 12