July 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 238572] New: SCSI Subsystem Locks-up Machine
by bugzilla_noreply＠novell.com 15 Oct '08

15 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=238572 Summary: SCSI Subsystem Locks-up Machine Product: openSUSE 10.2 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jim(a)edwardsj7.com QAContact: qa(a)suse.de My system has the root, "/", and "/home" directories on two different SCSI drives on the same chain of an Adaptec 29320 (U320) card and they are using the AIC79xx driver version 3.0. From time to time the system will cease to function and the SCSI activity indicator LED will stay on at 100% (usually it only flashes very briefly) and the machine becomes unresponsive. Maybe after a long time it will seem to return, but really the SCSI drives are off-line and even a restart fails back to what looks like an "init 3" screen with "login" displayed, but nothing is accepted. A system hard RESET, or power off and on, is required to restore functionality. The ensuing reboot displays a large number of transactions being replayed for the "/" RFS, 800+ is not unusual, but nothing for the ext3 (when it was RFS it had some transactions). It seems that this lock-up is triggered by things that try to move a lot of data over the SCSI bus, like "mkisofs" or some other large file transfers. Moving "/home" to an IDE drive did not help. "/" is on an RFS version 3.6 partition and "/home" is on an ext3 partition (it was RFS, and changed to ext3 with no effect). The same system hardware (AMD Athlon XP 2500+ etc.) has been running Suse 9.0 successfully with no such problems, and still can, so it seems to me to be likely to be related to the newer drivers (version 9.0's are much older, version 1.3.something, I think), possibly in association with RFS ??? For info ... jim@linux:~> cat /proc/scsi/aic79xx/4 Adaptec AIC79xx driver version: 3.0 Adaptec 29320 Ultra320 SCSI adapter aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs Allocated SCBs: 68, SG List Length: 128 Serial EEPROM: 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x09f4 0x01c7 0x2807 0x0010 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0410 0xb458 Target 0 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Goal: 320.000MB/s transfers (160.000MHz DT|IU|QAS, 16bit) Curr: 320.000MB/s transfers (160.000MHz DT|IU|QAS, 16bit) Channel A Target 0 Lun 0 Settings Commands Queued 47423 Commands Active 0 Command Openings 32 Max Tagged Openings 32 Device Queue Frozen Count 0 Target 1 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Goal: 320.000MB/s transfers (160.000MHz DT|IU|QAS, 16bit) Curr: 320.000MB/s transfers (160.000MHz DT|IU|QAS, 16bit) Channel A Target 1 Lun 0 Settings Commands Queued 105578 Commands Active 0 Command Openings 32 Max Tagged Openings 32 Device Queue Frozen Count 0 Target 2 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 3 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 4 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 5 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 6 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Goal: 80.000MB/s transfers (40.000MHz, 16bit) Curr: 80.000MB/s transfers (40.000MHz, 16bit) Channel A Target 6 Lun 0 Settings Commands Queued 32843 Commands Active 0 Command Openings 1 Max Tagged Openings 0 Device Queue Frozen Count 0 Target 7 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 8 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 9 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 10 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 11 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 12 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 13 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 14 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 15 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Targets "0" and "1" are the two SCSI hard drives. Thanks for any help Jim -- 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, or are watching someone who is.

1 27

[Bug 230895] New: hotkey-setup & power button on compaq presario M2000 laptop
by bugzilla_noreply＠novell.com 15 Oct '08

15 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=230895 Summary: hotkey-setup & power button on compaq presario M2000 laptop Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: behlert(a)novell.com ReportedBy: f.alabas(a)ttnet.net.tr QAContact: qa(a)suse.de Hotkeys on my laptop is all recognized well, except of Fn-F6 ($KEY_COFFEE) that is for simply locking the screen. It is not recognized when configuring as a input action or as a keyboard shortcut on KDE. In addition, power button is not responding although it has been configured as "wm_shutdown" in etc/sysconfig/poversave/events file. However this was already working at Suse Linux 10.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, or are watching someone who is.

1 8

[Bug 286769] New: bluetooth: MacBookPro bluetooth requires hid2hci to work
by bugzilla_noreply＠novell.com 15 Oct '08

15 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=286769 Summary: bluetooth: MacBookPro bluetooth requires hid2hci to work Product: openSUSE 10.3 Version: Alpha 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: seife(a)novell.com ReportedBy: ro(a)novell.com QAContact: qa(a)suse.de Found By: --- usb-id on bootup: + 1000 Bluetooth HCI MacBookPro (uninitialized) usb-id after hid2hci has been run: + 8205 Bluetooth HCI MacBookPro (vendor in both cases 0x05ac Apple) -- 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 255455] New: pm-utils should return a errorcode != 0 if a suspend fail
by bugzilla_noreply＠novell.com 15 Oct '08

15 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=255455 Summary: pm-utils should return a errorcode != 0 if a suspend fail Product: openSUSE 10.3 Version: Alpha 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Mobile Devices AssignedTo: seife(a)novell.com ReportedBy: dkukawka(a)novell.com QAContact: qa(a)suse.de CC: hmacht(a)novell.com, fseidel(a)novell.com Currently pm-utils return always 0 also if a error while suspend/resumue occurs. pm-utils should return usefull error codes. At least something != 0 to give tools a chance to detect if the resume was successful. -- 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, or are watching someone who is.

1 9

[Bug 233122] New: no debuginfo packages for fixed packages
by bugzilla_noreply＠novell.com 15 Oct '08

15 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=233122 Summary: no debuginfo packages for fixed packages Product: openSUSE 10.2 Version: RC 5 Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: olh(a)novell.com QAContact: qa(a)suse.de 10.2 has appearently no debuginfo packages for security/bugfix packages. another install source is required to provide also the -debuginfo.rpm for the very latest release of a package. The current situation confuses yast, as seen in bug #231183 -- 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, or are watching someone who is.

1 76

[Bug 222222] New: Yast sw_single (and inst_source) fails if remote repository is added, but the network connection is down (Refresh Off ignored?)
by bugzilla_noreply＠novell.com 14 Oct '08

14 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=222222 Summary: Yast sw_single (and inst_source) fails if remote repository is added, but the network connection is down (Refresh Off ignored?) Product: openSUSE 10.2 Version: Beta 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: amantia(a)kde.org QAContact: jsrain(a)novell.com I added a remote repository (packman by ftp) as install source. I explicitely disabled the refresh for that repository. Now when I run sw_single it gives me an error if my network connection is down (as it is in many cases, as I'm using dial-up), saying that: Cannot access installation media 20061116-230553 CD1 Check that server is accessible The details are: ftp://ftp2.lug.ro/packman/suse/10. Curl error for: ftp://ftp2.lug.ro/packman/suse/10.1/repodata/repomd.xml: Error code: Connection failed Error message: Couldn't resolve host 'ftp2.lug.ro' Choices are OK, Abort, Skip. If I select skip, I get a warning: There was an error in installation source initialization. ftp://ftp2.lug.ro/packman/suse/10.1/: Cannot create the installation source After this the Initializing screen is visible for a few seconds and I hear the DVD drive (containing the Beta2 DVD) spinning up, and I end up with an empty yast window, without texts or buttons on it. The only solution is to kill the y2base process. Now if I run inst_source, it tries to download the same file, it fails, and it removes the packman repository from the available sources. If I run inst_source with the network up, it refreshes the repository from the net... Of course, as I stated refresh is OFF for this repo. IIRC this worked correctly with Beta1. Just a note: if I add the repository, bring down the network and start sw_single it works for the first time, but if I start it some time later, it shows the bug. -- 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, or are watching someone who is.

1 8

[Bug 262054] New: boot always into maintenance mode with installer's version of fstab (fsck failed)
by bugzilla_noreply＠novell.com 14 Oct '08

14 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=262054 Summary: boot always into maintenance mode with installer's version of fstab (fsck failed) Product: openSUSE 10.3 Version: Alpha 2plus Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mrmazda(a)ij.net QAContact: qa(a)suse.de y2logs already available at https://bugzilla.novell.com/attachment.cgi?id=128746&action=view To get past problem in summary I have to edit fstab entries for what prior to SUSE's use of libata used to be called sda5, sda7 & sda8 to change fs_freq & fs_passno from 1 2 to 0 0. These partitions are on real Symbios SCSI. Factory installation / was to hda19, so hwprobe=-modules.pata was necessarily (AFAIK) used. -- 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, or are watching someone who is.

1 10

[Bug 258986] New: opensync: syncml-obex-client not working as a user
by bugzilla_noreply＠novell.com 13 Oct '08

13 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=258986 Summary: opensync: syncml-obex-client not working as a user Product: openSUSE 10.3 Version: Alpha 2plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: behlert(a)novell.com ReportedBy: felix(a)derklecks.de QAContact: qa(a)suse.de My opensync is working quiet well as root now. But as a normal user I allways get: # msynctool --sync handy Synchronizing group "handy" Member 2 of type file-sync just connected Member 1 of type syncml-obex-client had an error while connecting: Unable to connect to the interface Member 2 of type file-sync just disconnected All clients have disconnected The sync failed: Unable to connect one of the members dmesg: usb 3-1: new full speed USB device using uhci_hcd and address 2 usb 3-1: new device found, idVendor=0fce, idProduct=d043 usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 3-1: Product: Sony Ericsson V630 usb 3-1: Manufacturer: Sony Ericsson usb 3-1: SerialNumber: 3519410153340060 usb 3-1: configuration #3 chosen from 1 choice cdc_acm 3-1:3.1: ttyACM0: USB ACM device cdc_acm 3-1:3.3: ttyACM1: USB ACM device usbcore: registered new interface driver cdc_acm drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters usb0: register 'cdc_ether' at usb-0000:00:1d.1-1, CDC Ethernet Device, 02:80:37:fd:02:00 usbcore: registered new interface driver cdc_ether usb 3-1: usbfs: interface 1 claimed by cdc_acm while 'osplugin' sets config #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, or are watching someone who is.

1 34

[Bug 285472] New: network script does not work for /usr over NFS
by bugzilla_noreply＠novell.com 13 Oct '08

13 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=285472 Summary: network script does not work for /usr over NFS Product: openSUSE 10.3 Version: Alpha 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: zoz(a)novell.com ReportedBy: coolo(a)novell.com QAContact: qa(a)suse.de CC: thoenig(a)novell.com Found By: --- There is a small problem: the dbus init script should behind $remote_fs as it uses /usr - but that creates a loop as network requires 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 47

[Bug 287452] New: Suspend to disk conflicts with suspend to ram on Thinkpad
by bugzilla_noreply＠novell.com 09 Oct '08

09 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=287452 Summary: Suspend to disk conflicts with suspend to ram on Thinkpad Product: openSUSE 10.3 Version: Alpha 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Apache AssignedTo: bnc-team-apache(a)forge.provo.novell.com ReportedBy: felix.rommel(a)web.de QAContact: qa(a)suse.de Found By: --- Description: I choose suspend to disk from main menu and close the Thinkpad Z61m lid while suspend to disk is processed. After powering my laptop on again, it returns from suspend to disk. But after returning suddenly suspends to ram before graphical session is loaded. How to reproduce: 1. Choose in Gnome Power Manager "Suspend to ram" if laptop lid is closed 2. Choose suspend to disk from > Computer > Logout > Suspend to disk 3. Close the lid while suspend to disk is processed 4. Wait until suspend to disk is finish 5. Open the lid and power your laptop on again 6. It returns from disk but right after finishing it, it suspends to ram Expected behavior: Laptop shouldn't suspend to ram after returning from disk. It seems that Gnome Power Manager checks that lid is closed and wants to suspend to ram, although suspend to disk is processed. -- 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 10