March 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 370872] New: "pccardctl eject" hangs in state D
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=370872 Summary: "pccardctl eject" hangs in state D Product: openSUSE 11.0 Version: Alpha 2plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: seife(a)novell.com QAContact: qa(a)suse.de CC: fseidel(a)novell.com Found By: Development During suspend, one thing we do is eject PCMCIA card with "pccardctl eject". I quite frequently see that command hanging in state D, which makes suspend fail. Attempting to shut down the machine cleanly lead to a hang when the sound modules are unloaded, a clean shutdown does only happen if i do a sysrq-e to kill the hanging processes and make init proceed. I have seen this with various 3G/UMTS CardBus cards, both USB-serial based and nozomi based, so i believe this to be a generic PCMCIA issue. Will attach sysrq-T -- 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 108

[Bug 362947] New: evaluate debian/ubuntu libtool patch
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=362947 Summary: evaluate debian/ubuntu libtool patch Product: openSUSE 11.0 Version: Alpha 2 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: P5 - None Component: Development AssignedTo: schwab(a)novell.com ReportedBy: crrodriguez(a)novell.com QAContact: qa(a)suse.de Found By: Development Both debian and Ubuntu are using a libtool patch{1} that sets link_all_deplibs=no on ELF systems, this will help a lot reducing unedded library dependencies in packages. {1} http://patches.ubuntu.com/by-release/extracted/debian/libt/libtool/1.5.26-1… This is just a suggestion, I think this may work for us as well ( ubuntu and debian archives are a biiiigg test ;) ) -- 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

[Bug 341350] New: severe limitations in xen-tools python scripts
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=341350 Summary: severe limitations in xen-tools python scripts Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: duwe(a)novell.com QAContact: qa(a)suse.de Found By: Development qemu-dm appears to be accepting the same type of arguments as qemu does; however the automatically generated command line is impossible to contain 1st) multiple "-usbdevice" switches -- one is already used up by the "tablet" option. 2nd) a "-parallel" switch This may not be serious for a server virtualisation, but it surely hurts on the desktop. -- 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 343180] New: XEN keymap problem.
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=343180 Summary: XEN keymap problem. Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: nice(a)titanic.nyme.hu QAContact: qa(a)suse.de Found By: Other I installed Vindows Vista on Xen by vm-install ran from YaST with the following settings (/etc/xen/vm/windowsvista): ############################################### name="windowsvista" ostype="windowsvista" uuid="cf93a3e0-c33f-50c4-dd3f-b68691418a40" memory=1024 vcpus=1 on_crash="destroy" on_poweroff="destroy" on_reboot="restart" localtime=1 builder="hvm" extid=0 device_model="/usr/lib/xen/bin/qemu-dm" kernel="/usr/lib/xen/boot/hvmloader" boot="c" disk=[ 'file:/mnt/xen/vista.bin,hda,w', 'phy:/dev/cdrom,hdc:cdrom,r', ] vif=[ 'mac=00:16:3e:1a:4d:7d,model=rtl8139,type=ioemu', ] stdvga=0 vnc=1 vncunused=1 apic=0 acpi=1 pae=1 usb=1 usbdevice='tablet' serial="pty" ############################################### I tried to manage this qemu-dm assisted fully virtualized host either via VNC or SDL (changing the config file above), but I realized that the host's keyboard map was incomplete and incorrect. Let's see a sort example from the file /var/log/xen qemu-dm.29632.log: ############################################### Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 501 Warning: no scancode found for keysym 501 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 ############################################### I figured out that the problem could by corrected by make qemu-dm use some of the keymaps under /usr/share/xen/qemu/keymaps by passing a -key CODE parameter to it. Or am I wrong? I also figured out that I can make xend to pass this parameter to qemu-dm by adding a keymap='CODE' line to the /etc/xen/vm/VM file. So I added the line keymap='hu' to the vm config file, and qemu-vm's command line really changed: milleniumfalcon:/var/log/xen # cat /proc/8046/cmdline | sed y/'\x0'/' '/ /usr/lib/xen/bin/qemu-dm -d 2 -vcpus 1 -boot c -localtime -serial pty -acpi -usb -usbdevice tablet -k hu -domain-name windowsvista -net nic,vlan=1,macaddr=00:16:3e:1a:4d:7d,model=rtl8139 -net tap,vlan=1 -vncunused -vnclisten 127.0.0.1 milleniumfalcon:/var/log/xen # cat /proc/8046/cmdline | sed y/'\x0'/' '/ The keyboard got a bit better but there are still missing keys, "ű" for example. I tried other keymaps with similar results. What may be wrong with these keymaps? Are they defectivein a way? I have no idea. Thist bug report is primarily about the possible errors int these keymap files, but I have other related quetions too: It wold be good to make it possible to change the keymap setting in vm-install if it is necessary at all. Furthermore I do not know where virt-manager gets the information about VMs from. Once I moved every file from /etc/xen/vm to the root directory, restarted virt-manager and in spite of the lack of VM description files it still remebered my guest VM. I also do not know, what keeps the files /etc/xen/vm/VM and /etc/xen/vm/VM.xml in synchron. So, if i add a keymap to the file /etc/xen/vm/VM then that VM will use that keymap if I start if by the xm command. But what happens if i start that VM from virt-manager? Do I also need to add the keymap to the file /etc/xen/vm/VM.xml? Or to a third file? -- 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 285914] New: Sound hangs on CPU frequency change
by bugzilla_noreply＠novell.com 30 Mar '09

30 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=285914 Summary: Sound hangs on CPU frequency change Product: openSUSE 10.3 Version: Alpha 5 Platform: x86-64 OS/Version: openSUSE 10.2 Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: ray(a)openland.cz QAContact: qa(a)suse.de Found By: --- First of all I must say, that I am using openSUSE 10.2, but I have selected openSUSE 10.3 product, because I am using latest kernel from HEAD repository. Hardware Environment: Asus A6Km Software Environment: e.g. Amarok audio player Problem Description: I have Asus A6Km with AMD Turion 3200+. It has Realtek ALC650 integrated sound card and is working fine. Recently, I bought Creative Sound Blaster Live! 5.1 24-bit External for this laptop, because I have already one connected to my desktop computer (openSUSE 10.2 x86) and works fine too. However, when I connect Sound Blaster to my laptop, sound hangs randomly. I spent lot of time finding the reason, because there was nothing in logs, dmesg etc. Finally I found, that it is caused by CPU frequency scaling. When CPU speed is changed, than sound hangs - to reboot help only disconnection of Sound Blaster. When I fix CPU frequency, than Sound Blaster works like the other one in my desktop computer - fine. I found only two refs describing similar/same problem: http://www.linuxforums.org/forum/linux-laptops/63126-sound-problems-cpu-ste… http://alsa.opensrc.org/Tascam_US-224 Steps to reproduce: 1) Connect Sound Blaster Live! 5.1 24-bit External 2) start some audio output with your favorite player 3) wait on frequency change 4) Sound hangs 5) For successful reboot, it is necessary to disconnect Sound Blaster Hope, you can help me. If you will need any other info, just ask me. I also submit bug to Alsa bugzilla (ID: 0003097) month ago and kernel bugzilla (ID: 8648), but there were no response. I am not sure whether this is sound subsystem related issue or USB subsystem issue (my laptop has SIS chipset, which is not so often used like others). May be I am absolutely wrong putting this bug report to this bugzilla, so if anyone from Novell staff decide, that this report is not related to this bugzilla, but only to kernel/alsa bugzilla, feel free to close 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 16

[Bug 368800] New: build status wrongly inaccuracy
by bugzilla_noreply＠novell.com 29 Mar '09

29 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=368800 Summary: build status wrongly inaccuracy Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: poeml(a)novell.com QAContact: adrian(a)novell.com Found By: --- The build status "succeeded" often doesn't reflect reality. A packager frequently sees the following. First, after a commit: poeml@batavia510 ~/bs/openSUSE:Tools/osc % osc results CentOS_5 i586 scheduled CentOS_5 x86_64 building Debian_Etch i586 scheduled Debian_Etch x86_64 scheduled Fedora_7 i586 succeeded Fedora_7 x86_64 scheduled Fedora_8 i586 succeeded Fedora_8 x86_64 succeeded Fedora_Core_6 i586 succeeded Fedora_Core_6 x86_64 succeeded Mandriva_2006 i586 succeeded Mandriva_2007 i586 succeeded Mandriva_2007 x86_64 succeeded Mandriva_2008 i586 succeeded Mandriva_2008 x86_64 succeeded openSUSE_10.2 i586 succeeded openSUSE_10.2 x86_64 succeeded openSUSE_10.3 i586 succeeded openSUSE_10.3 x86_64 succeeded openSUSE_Factory i586 succeeded openSUSE_Factory x86_64 succeeded RHEL_5 i586 succeeded RHEL_5 x86_64 succeeded SLES_9 i586 disabled SLES_9 x86_64 disabled SLE_10 i586 succeeded SLE_10 x86_64 succeeded SUSE_Linux_10.1 i586 succeeded SUSE_Linux_10.1 x86_64 succeeded xUbuntu_6.06 i586 succeeded xUbuntu_7.04 i586 succeeded xUbuntu_7.10 i586 succeeded xUbuntu_7.10 x86_64 succeeded Fine -- I just don't believe it's succeeded already, because I committed only a minute ago. But I know what to think. Later, things get confusing: poeml@batavia510 ~/bs/openSUSE:Tools/osc % osc results CentOS_5 i586 finished CentOS_5 x86_64 building Debian_Etch i586 succeeded Debian_Etch x86_64 succeeded Fedora_7 i586 succeeded Fedora_7 x86_64 succeeded Fedora_8 i586 succeeded Fedora_8 x86_64 succeeded Fedora_Core_6 i586 finished Fedora_Core_6 x86_64 succeeded Mandriva_2006 i586 succeeded Mandriva_2007 i586 finished Mandriva_2007 x86_64 succeeded Mandriva_2008 i586 succeeded Mandriva_2008 x86_64 building openSUSE_10.2 i586 building openSUSE_10.2 x86_64 succeeded openSUSE_10.3 i586 finished openSUSE_10.3 x86_64 succeeded openSUSE_Factory i586 finished openSUSE_Factory x86_64 succeeded RHEL_5 i586 building RHEL_5 x86_64 succeeded SLES_9 i586 disabled SLES_9 x86_64 disabled SLE_10 i586 succeeded SLE_10 x86_64 succeeded SUSE_Linux_10.1 i586 succeeded SUSE_Linux_10.1 x86_64 succeeded xUbuntu_6.06 i586 succeeded xUbuntu_7.04 i586 succeeded xUbuntu_7.10 i586 finished xUbuntu_7.10 x86_64 succeeded Can you tell which of them are already succeeded, and which ones are still "succeeded"? It would be better if the commit would invalidate the "succeeded" state. The "succeeded should only be reached again once the package has actually been built (successfully of course). -- 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 4

[Bug 372261] New: Kdebase-samba module not accessible.
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=372261 Summary: Kdebase-samba module not accessible. Product: openSUSE 11.0 Version: Factory Platform: 64bit OS/Version: openSUSE 11.0 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: monkey9(a)iae.nl QAContact: qa(a)suse.de Found By: Beta-Customer There is no option to set the proper options to login linuxshares, not from linux, nor from other os. This module is, unfortunately, needed to grant guest logins, or set passwords. As the samba alone, is not enough to arrange logins into linux shares. Now, the password requester pops up, but as there is no possibility to set a password or username, there is no possibility to get into the shares. If you ask me, why is samba alone not enough? -- 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 340331] New: Tray icon of KNetworkmanager not transparent
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=340331#c331580 Summary: Tray icon of KNetworkmanager not transparent Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: ma2412ma(a)hotmail.com QAContact: qa(a)suse.de Found By: --- Created an attachment (id=182688) --> (https://bugzilla.novell.com/attachment.cgi?id=182688) Tray icon for KNetworkmanager should be transparent In addition to not redrawing correctly (see bug #331580), the icon is also not transparent in the background - see attached screenshot. -- 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 5

[Bug 343874] New: If the system hybernates with an usb external drive mounted, weird things happen
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=343874 Summary: If the system hybernates with an usb external drive mounted, weird things happen Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de Found By: --- I hibernated forgotting to umount a manually mounted external HD on USB. The disk was on sda1, and mounted using this fstab line: LABEL=usb_sg60 /mnt/usb/usb_sg60 reiserfs noatime,user,noauto,acl,user_xattr 0 0 After hibernating, the disk moves to sdb1: nimrodel:~ # l /dev/disk/by-label/ | grep usb_sg60 lrwxrwxrwx 1 root root 10 Nov 24 14:10 usb_sg60 -> ../../sdb1 but the kernel thinks it is still mounted on sda1: nimrodel:~ # mount -l | grep usb_sg60 /dev/sda1 on /mnt/usb/usb_sg60 type reiserfs (rw,noexec,nosuid,nodev,noatime,acl,user_xattr) and it is possible to remount it correctly: nimrodel:~ # umount /mnt/usb/usb_sg60 nimrodel:~ # mount /mnt/usb/usb_sg60 nimrodel:~ # mount -l | grep usb_sg60 /dev/sdb1 on /mnt/usb/usb_sg60 type reiserfs (rw,noexec,nosuid,nodev,noatime,acl,user_xattr) [usb_sg60] but sda has dissapeared: nimrodel:~ # l /dev/sd?* brw-r----- 1 root disk 8, 16 Nov 24 14:10 /dev/sdb brw-r----- 1 root disk 8, 17 Nov 24 14:10 /dev/sdb1 Here goes the kernel log: Nov 24 14:09:32 nimrodel kernel: swsusp: critical section: Nov 24 14:09:32 nimrodel kernel: swsusp: Need to copy 113403 pages Nov 24 14:09:32 nimrodel kernel: Intel machine check architecture supported. Nov 24 14:09:32 nimrodel kernel: Intel machine check reporting enabled on CPU#0. Nov 24 14:09:32 nimrodel kernel: CPU0: Intel P4/Xeon Extended MCE MSRs (12) available Nov 24 14:09:32 nimrodel kernel: CPU0: Thermal monitoring enabled Nov 24 14:09:32 nimrodel kernel: PCI: Setting latency timer of device 0000:00:1e.0 to 64 Nov 24 14:09:32 nimrodel kernel: PM: Writing back config space on device 0000:00:1f.5 at offset 1 (was 2800005, writing 2800001) Nov 24 14:09:32 nimrodel kernel: ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 19 Nov 24 14:09:32 nimrodel kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64 Nov 24 14:09:32 nimrodel kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Nov 24 14:09:38 nimrodel kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 17 Nov 24 14:09:38 nimrodel kernel: usb usb2: root hub lost power or was reset Nov 24 14:09:38 nimrodel kernel: ACPI: PCI Interrupt 0000:02:02.1[B] -> GSI 19 (level, low) -> IRQ 18 Nov 24 14:09:38 nimrodel kernel: usb usb3: root hub lost power or was reset Nov 24 14:09:38 nimrodel kernel: ACPI: PCI Interrupt 0000:02:02.2[C] -> GSI 16 (level, low) -> IRQ 16 Nov 24 14:09:38 nimrodel kernel: usb usb1: root hub lost power or was reset Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:08 activated. Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:09 activated. Nov 24 14:09:38 nimrodel kernel: pnp: Failed to activate device 00:0b. Nov 24 14:09:38 nimrodel kernel: pnp: Failed to activate device 00:0c. Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:0d activated. Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:0e activated. Nov 24 14:09:38 nimrodel kernel: hda: selected mode 0x45 Nov 24 14:09:38 nimrodel kernel: hdb: selected mode 0x45 Nov 24 14:09:38 nimrodel kernel: hdc: selected mode 0x42 Nov 24 14:09:38 nimrodel kernel: hdd: selected mode 0x45 Nov 24 14:09:38 nimrodel kernel: usb_endpoint usbdev1.3_ep00: PM: resume from 0, parent 1-1 still 1 Nov 24 14:09:38 nimrodel kernel: usb-storage 1-1:1.0: PM: resume from 1, parent 1-1 still 1 Nov 24 14:09:38 nimrodel kernel: usb_endpoint usbdev1.3_ep02: PM: resume from 0, parent 1-1:1.0 still 1 Nov 24 14:09:38 nimrodel kernel: usb_endpoint usbdev1.3_ep86: PM: resume from 0, parent 1-1:1.0 still 1 Nov 24 14:09:38 nimrodel kernel: host0: PM: resume from 0, parent 1-1:1.0 still 1 Nov 24 14:09:38 nimrodel kernel: Restarting tasks ... <6>usb 1-1: USB disconnect, address 3 Nov 24 14:09:38 nimrodel kernel: Buffer I/O error on device sda1, logical block 7514 Nov 24 14:09:38 nimrodel kernel: lost page write due to I/O error on sda1 Nov 24 14:09:38 nimrodel kernel: Buffer I/O error on device sda1, logical block 7515 Nov 24 14:09:38 nimrodel kernel: lost page write due to I/O error on sda1 Nov 24 14:09:38 nimrodel kernel: REISERFS abort (device sda1): Journal write error in flush_commit_list Nov 24 14:09:38 nimrodel kernel: done. Nov 24 14:09:38 nimrodel kernel: swsusp: Basic memory bitmaps freed Nov 24 14:09:38 nimrodel kernel: usb 1-1: new high speed USB device using ehci_hcd and address 4 Nov 24 14:09:38 nimrodel kernel: usb 1-1: new device found, idVendor=04b4, idProduct=6830 Nov 24 14:09:38 nimrodel kernel: usb 1-1: new device strings: Mfr=56, Product=78, SerialNumber=100 Nov 24 14:09:38 nimrodel kernel: usb 1-1: Product: USB2.0 Storage Device Nov 24 14:09:38 nimrodel kernel: usb 1-1: Manufacturer: Cypress Semiconductor Nov 24 14:09:38 nimrodel kernel: usb 1-1: SerialNumber: DEF10000CE2DB1A Nov 24 14:09:38 nimrodel kernel: usb 1-1: configuration #1 chosen from 1 choice Nov 24 14:09:38 nimrodel kernel: scsi1 : SCSI emulation for USB Mass Storage devices Nov 24 14:09:38 nimrodel kernel: usb-storage: device found at 4 Nov 24 14:09:38 nimrodel kernel: usb-storage: waiting for device to settle before scanning Nov 24 14:09:38 nimrodel kernel: scsi 1:0:0:0: Direct-Access ST360020 A 0000 PQ: 0 ANSI: 0 Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] 117231408 512-byte hardware sectors (60022 MB) Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Write Protect is off Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Mode Sense: 27 00 00 00 Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] 117231408 512-byte hardware sectors (60022 MB) Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Write Protect is off Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Mode Sense: 27 00 00 00 Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through Nov 24 14:09:38 nimrodel kernel: sdb:<6>input: Power Button (FF) as /class/input/input18 Nov 24 14:09:38 nimrodel kernel: ACPI: Power Button (FF) [PWRF] Nov 24 14:09:38 nimrodel kernel: input: Power Button (CM) as /class/input/input19 Nov 24 14:09:38 nimrodel kernel: ACPI: Power Button (CM) [PWRB] Nov 24 14:09:38 nimrodel kernel: input: Sleep Button (CM) as /class/input/input20 Nov 24 14:09:38 nimrodel kernel: ACPI: Sleep Button (CM) [SLPB] Nov 24 14:10:03 nimrodel kernel: usb 1-1: reset high speed USB device using ehci_hcd and address 4 Nov 24 14:10:04 nimrodel kernel: sdb1 Nov 24 14:10:04 nimrodel kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Nov 24 14:10:04 nimrodel kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Nov 24 14:10:04 nimrodel kernel: usb-storage: device scan complete Nov 24 14:43:26 nimrodel kernel: scsi 0:0:0:0: rejecting I/O to dead device I suppose I could add my own hook to umount the device if I forget, but I propose that you could add a generic hook to umount usb devices on hybernate, or ensure that they resurrect on the correct device. -- 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 49

[Bug 357354] New: lenovo X60s jw collector bug
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=357354 Summary: lenovo X60s jw collector bug Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: jw(a)novell.com ReportedBy: jw(a)novell.com QAContact: qa(a)suse.de Depends on: 355128 Found By: --- This defect depends on all issues found with my X60s -- 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 99