August 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 892885] New: Default KDE, NON-Automated, Installation Fails on Multiple Levels
by bugzilla_noreply＠novell.com 02 Sep '14

02 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=892885 https://bugzilla.novell.com/show_bug.cgi?id=892885#c0 Summary: Default KDE, NON-Automated, Installation Fails on Multiple Levels Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: secure(a)aphofis.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 I downloaded the software as of 21 August, 2014 and started a NON-Automated KDE Default Installation on X_64 Hardware. The installation failed on multiple levels. I think to ensure quality I would trust someone other than I do a NON_Automated Installation. The X_64 PC has 3 HDD which were added Together by a System (BIOS) CTRL+F to be 1 volume space via a RAID5 for which the installation failed to see. Despite the Boot from CD Operation occurring well beyond RAID 5 configure and standard BIOS support the hard disks were seen as 3 x Hard Disk Drives. The further installation was aborted at that Point. 1st Failure of the Installation! The second Installation was done after NO BIOS RAID support of LV was created. I had to get rid of the system set RAID5. At the point in Partitioner Suggested Option was only to provide a separate partition for /home and I allowed it to suggest and it auto allocated 0.5GB to the / (root) Mounted Partition. When I proceeded to permit the suggestion of Partitioning, the selection of additional Software Packages I was warned that / has NO space available. - Failure of Installation 2! I retreated back and Manually Partitioned the 3 Hard Drives. The Third Installation was of not as the software selection of 'Help and Documentation is NOT on by default. At the creation of the Network Interface where NO DHCP Services are offered on my secure LAN it failed to permit me to create a static IP once I took the immediate action when first presented to do so. As the wrong Network Discovery software had not run IFUP did not configure my Realteck Ethernet adapter what so ever. Failure of Installation 3! On the Fourth Installation I let it to proceed to Network Installation and used DHCP and then came back to edit as my secure LAN does NOT offer DHCP services what-so-ever. This installation part failed at it auto configured a bridge when one 1 Ethernet card was present Failure of Installation 4! At time of 5th installation I did as the above, however I edited out the Network brw and left one Static IP with an Realtek Ethernet Card and I proceeded to 'Test the Network card. This test indicated that the connection to the Internet had failed and so see logs. I would have had to fail the Installation at this moment in reality. Failure of Installation 5! The very same test of connection to the Internet has been flawed for many versions. If a static IP has been allocated the test will always fail, however if you ignore this issue and press onward it does in fact connect perfectly and the connection Logs are empty. I'll call this a successful Installation of a NON-Automated default KDE installation at number 6 attempt. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Complete failure of 5 Installations of 13.1 X_64 Expected Results: ???? I understand you will want a variety of Logs...Please be quite specific in asking me to supply them. Just want to get all the info you may need of the above all in 1 upload rather than many -- 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 894211] New: rcnetwork network start restart doesn't set default route for static address
by bugzilla_noreply＠novell.com 02 Sep '14

02 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=894211 https://bugzilla.novell.com/show_bug.cgi?id=894211#c0 Summary: rcnetwork network start restart doesn't set default route for static address Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Ralf.Friedl(a)online.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 I tried to set a static IPv4 address with a static default route. On system startup and on network reconfiguration by "yast lan", the default route is not set, even in cases where just DNS servers are changed and there is no need to reconfigure the interfaces or routes. As a result the server is not reachable, as I need the default rouch to connect to the server. I think the reason is that the interface is not yet up when trying to set the route: ifup[926]: eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) ifup[926]: eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) kernel: [ 5.368627] r8169 0000:02:00.0 eth0: link down kernel: [ 5.368682] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready kernel: [ 5.368701] r8169 0000:02:00.0 eth0: link down ifup[926]: Error while executing: ifup[926]: Command 'ip route replace to default via x.x.x.x dev eth0' returned: ifup[926]: RTNETLINK answers: Invalid argument ifup[926]: Configuration line: default x.x.x.x - eth0 ifup-route[1014]: Error while executing: ifup-route[1014]: Command 'ip route replace to default via x.x.x.x dev eth0' returned: ifup-route[1014]: RTNETLINK answers: Invalid argument ifup-route[1014]: Configuration line: default x.x.x.x - eth0 ... kernel: [ 8.406817] r8169 0000:02:00.0 eth0: link up kernel: [ 8.406831] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready As you can see, the route command is executed before the interface comes up. Can't we just get rid of systemd and go back to things that worked? Reproducible: Always Steps to Reproduce: 1. configure static IPv4 address, static default route Actual Results: Default route is not set, leaving the server unreachable. Expected Results: Default route is set. -- 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 894205] New: virt-manager refuses to complete creation of new network
by bugzilla_noreply＠novell.com 02 Sep '14

02 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=894205 https://bugzilla.novell.com/show_bug.cgi?id=894205#c0 Summary: virt-manager refuses to complete creation of new network Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: aspiers(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- [Couldn't see an appropriate bugzilla component to assign this too.] On recently patched openSUSE 13.1, if I start virt-manager > Edit > Connection Details > Virtual Networks > + (create button) > enter a network name > Forward > Forward > Forward then clicking the Finish button does absolutely nothing, i.e. the "Create virtual network Step 4 of 4" dialog remains there, and it is impossible to create the network via the GUI. Nothing new appears in /var/log/messages or on the console from which I started virt-manager. Relevant rpm versions: libvirt-1.1.2-2.32.1.x86_64 libvirt-client-1.1.2-2.32.1.x86_64 libvirt-daemon-1.1.2-2.32.1.x86_64 libvirt-daemon-config-network-1.1.2-2.32.1.x86_64 libvirt-daemon-config-nwfilter-1.1.2-2.32.1.x86_64 libvirt-daemon-debuginfo-1.2.6-413.1.x86_64 libvirt-daemon-driver-interface-1.1.2-2.32.1.x86_64 libvirt-daemon-driver-interface-debuginfo-1.2.6-413.1.x86_64 libvirt-daemon-driver-libxl-1.1.2-2.32.1.x86_64 libvirt-daemon-driver-lxc-1.1.2-2.32.1.x86_64 libvirt-daemon-driver-network-1.1.2-2.32.1.x86_64 libvirt-daemon-driver-network-debuginfo-1.2.6-413.1.x86_64 libvirt-daemon-driver-nodedev-1.1.2-2.32.1.x86_64 libvirt-daemon-driver-nwfilter-1.1.2-2.32.1.x86_64 libvirt-daemon-driver-nwfilter-debuginfo-1.2.6-413.1.x86_64 libvirt-daemon-driver-qemu-1.1.2-2.32.1.x86_64 libvirt-daemon-driver-secret-1.1.2-2.32.1.x86_64 libvirt-daemon-driver-storage-1.1.2-2.32.1.x86_64 libvirt-daemon-driver-uml-1.1.2-2.32.1.x86_64 libvirt-daemon-driver-vbox-1.1.2-2.32.1.x86_64 libvirt-daemon-driver-xen-1.1.2-2.32.1.x86_64 libvirt-daemon-lxc-1.1.2-2.32.1.x86_64 libvirt-daemon-qemu-1.1.2-2.32.1.x86_64 libvirt-daemon-uml-1.1.2-2.32.1.x86_64 libvirt-daemon-vbox-1.1.2-2.32.1.x86_64 libvirt-daemon-xen-1.1.2-2.32.1.x86_64 libvirt-devel-1.1.2-2.32.1.x86_64 libvirt-doc-1.1.2-2.32.1.x86_64 libvirt-glib-1_0-0-0.1.8-41.2.x86_64 libvirt-login-shell-1.1.2-2.32.1.x86_64 libvirt-python-1.1.2-2.32.1.x86_64 python-virtinst-0.600.4-5.6.1.x86_64 virt-manager-1.0.1-213.1.noarch virt-manager-common-1.0.1-213.1.noarch virt-utils-1.1.9-47.4.x86_64 virt-viewer-1.0-90.2.x86_64 -- 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 888052] New: dracut and LUKS-encrypted partitions
by bugzilla_noreply＠novell.com 02 Sep '14

02 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=888052 https://bugzilla.novell.com/show_bug.cgi?id=888052#c0 Summary: dracut and LUKS-encrypted partitions Classification: openSUSE Product: openSUSE Factory Version: 201407* Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 I upgraded from a long-working openSUSE 13.1 install to Factory. My first boot was not a happy one, as the new dracut system could not find my encrypted disk. I was able to (thanks to the emergency shell which mysteriously appeared after some time) cryptsetup the partition and continue the boot. I posited that /etc/crypttab needed to be explicitly set up, which I did and rebuilt the dracut initrd, and things have worked fine ever since. So, there are really two issues: 1. openSUSE 13.1 did not require /etc/crypttab (although I used it for swap, I did not use it for root) and - apparently - Factory does. 2. There is no indication as to /if/ or /when/ the emergency shell might appear - I could have saved myself a half-dozen failed boots if I had been more patient, but with an SSD even 30-60 seconds is a long time to wait. *Some* indication that "eventually, you might get an emergency shell" would be nice. Better yet, some way to get into the emergency shell right away would be /awesome/. 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 3

[Bug 894307] New: kiwi: EFI + grub2 doesn't work on AArch64
by bugzilla_noreply＠novell.com 02 Sep '14

02 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=894307 https://bugzilla.novell.com/show_bug.cgi?id=894307#c0 Summary: kiwi: EFI + grub2 doesn't work on AArch64 Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: aarch64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: ms(a)suse.com ReportedBy: agraf(a)suse.com QAContact: ms(a)suse.com Found By: --- Blocker: --- While trying to create an image with efi and grub2, kiwi failed to account for path names that were not i386 or x86_64. [ 259s] (cd /tmp/kiwiboot.fGUdty && cpio -i -d 'usr/share/grub2/themes/*' -d 'usr/lib/grub/i386-pc/*' -d 'usr/lib/grub/i386-efi/*' -d 2>&1)] [ 260s] Aug-30 23:00:36 <3> : No grub2 stage files found in boot image Instead, kiwi should look for arm64 path names. -- 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 860729] New: pm-suspend/pm-hibernate instantly waking up machine with usb mouse (temp fix found)
by bugzilla_noreply＠novell.com 02 Sep '14

02 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=860729 https://bugzilla.novell.com/show_bug.cgi?id=860729#c0 Summary: pm-suspend/pm-hibernate instantly waking up machine with usb mouse (temp fix found) Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: 32bit OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: eighter_ball(a)mail.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux i686) Presto/2.12.388 Version/12.15 Clean install, latest update. de - KDE4 If run from konsole pm-suspend - system do it, all turned off (HDD, coolers), just a moment, then it wake up as if i press power button, but i don't. Click on GUI button in kickoff menu lead to same result. When i disconnect my usb mice and try pm-suspend - all fine. Solution is adding module "ohci_pci" to /etc/pm/config.d/(anyname file) with line: SUSPEND_MODULES="ohci_pci" as described in /usr/lib/pm-utils/defaults pm-hibernate don't work properly (will write another bug) and wake up with mice too. Reproducible: Always Steps to Reproduce: 1. run pm-suspend or click button Suspend in kickoff 2. system suspending 3. system waking up Actual Results: immediately wake up after suspending Expected Results: wake up after pressing power button uname -a, lspci lsusb and pm-suspend.log - http://paste.opensuse.org/86657909 -- 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 2

[Bug 892480] New: swig-3.x segmentation fault when creating libzypp-bindings
by bugzilla_noreply＠novell.com 02 Sep '14

02 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=892480 https://bugzilla.novell.com/show_bug.cgi?id=892480#c0 Summary: swig-3.x segmentation fault when creating libzypp-bindings Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: mmarek(a)suse.com ReportedBy: ma(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- Created an attachment (id=602761) --> (http://bugzilla.novell.com/attachment.cgi?id=602761) Barcktrace based on swig-3.0.2-1.2.x86_64 Error log is available at https://build.opensuse.org/package/live_build_log/zypp:Head/libzypp-binding… (i586 as well). Backtrace based on swig-3.0.2-1.2.x86_64 is attached. Same libzypp code succeeds on SLE12 which is still using swig-2.x. -- 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 3

[Bug 866283] New: No automatic fsck on ext4 fs after checktime reached
by bugzilla_noreply＠novell.com 02 Sep '14

02 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=866283 https://bugzilla.novell.com/show_bug.cgi?id=866283#c0 Summary: No automatic fsck on ext4 fs after checktime reached Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: martin(a)oneiros.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=580532) --> (http://bugzilla.novell.com/attachment.cgi?id=580532) /etc/fstab User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 I have these messages in my dmesg: [ 20.526382] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem [ 20.572718] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: acl,user_xattr [ 20.653012] EXT4-fs (dm-0): warning: checktime reached, running e2fsck is recommended [ 20.700149] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: acl,user_xattr,journal_checksum [ 20.780360] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 20.877039] EXT4-fs (dm-2): warning: checktime reached, running e2fsck is recommended [ 20.891707] XFS (dm-6): Mounting Filesystem [ 20.911392] XFS (dm-7): Mounting Filesystem [ 20.913928] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: acl,user_xattr,journal_checksum [ 20.960387] XFS (dm-8): Mounting Filesystem [ 21.907109] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: acl,user_xattr [ 21.928877] EXT4-fs (dm-9): warning: checktime reached, running e2fsck is recommended [ 21.929530] XFS (dm-7): Ending clean mount [ 21.945120] XFS (dm-8): Ending clean mount [ 21.966153] EXT4-fs (dm-9): mounted filesystem with ordered data mode. Opts: acl,user_xattr,journal_checksum [ 22.015595] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: acl,user_xattr,journal_checksum [ 22.193371] XFS (dm-6): Ending clean mount Although the relevant filesystems have the right flags in /etc/fstab, no automatic fsck is run. This is a system with LVM on RAID5. mounts: > mount|fgrep ext4 /dev/mapper/system-root on / type ext4 (rw,relatime,journal_checksum,data=ordered) /dev/mapper/system-home on /home type ext4 (rw,relatime,journal_checksum,data=ordered) /dev/mapper/system-space on /space type ext4 (rw,relatime,journal_checksum,data=ordered) /dev/mapper/raid-nelson--boot on /raid/nelson/boot type ext4 (ro,relatime,stripe=256,data=ordered) /dev/mapper/raid-backup on /raid/backup type ext4 (rw,relatime,journal_checksum,stripe=64,data=ordered) /dev/mapper/raid-raid on /raid/raid type ext4 (rw,relatime,journal_checksum,stripe=64,data=ordered) > l /dev/mapper/ insgesamt 0 drwxr-xr-x 2 root root 260 28. Feb 13:52 ./ drwxr-xr-x 20 root root 4300 28. Feb 13:52 ../ crw------- 1 root root 10, 236 28. Feb 13:52 control lrwxrwxrwx 1 root root 7 28. Feb 13:52 raid-backup -> ../dm-9 lrwxrwxrwx 1 root root 7 28. Feb 13:52 raid-nelson--boot -> ../dm-5 lrwxrwxrwx 1 root root 7 28. Feb 13:52 raid-nelson--home -> ../dm-6 lrwxrwxrwx 1 root root 7 28. Feb 13:52 raid-nelson--root -> ../dm-7 lrwxrwxrwx 1 root root 7 28. Feb 13:52 raid-nelson--space -> ../dm-8 lrwxrwxrwx 1 root root 7 28. Feb 13:52 raid-raid -> ../dm-4 lrwxrwxrwx 1 root root 7 28. Feb 13:52 system-home -> ../dm-0 lrwxrwxrwx 1 root root 7 28. Feb 13:52 system-root -> ../dm-1 lrwxrwxrwx 1 root root 7 28. Feb 13:52 system-space -> ../dm-2 lrwxrwxrwx 1 root root 7 28. Feb 13:52 system-swap -> ../dm-3 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 45

[Bug 891168] New: Device names are changing dynamically, making the system disappear.
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=891168 https://bugzilla.novell.com/show_bug.cgi?id=891168#c0 Summary: Device names are changing dynamically, making the system disappear. Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nrickert(a)ameritech.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Today, I installed snapshot 20140807 using live media. My install was to an external drive. If I have booted from the internal drive, then the devices are: /dev/sda internal drive /dev/sdb through /dev/sde - memory card reader slots (usually no memory installed) /dev/sdf first USB drive /dev/sdf second USB drive. During install, booted from live media (live KDE 20140807, and the live Gnome described in factory mailing list message "http://lists.opensuse.org/opensuse-factory/2014-08/msg00048.html" the install media was on a USB. /dev/sda internal hard drive /dev/sdb installation USB live media /dev/sdc through /dev/sdf memory card reader slots /dev/sdg the 80G external drive, to which I was installing. On two install attempts - first with that Gnome media, second with KDE, the install seemed to hang at about the time that it have finished copying the root file system. With the Gnome install, I saw popups about an inserted drive. And the system was in a hard hang. With the KDE install, there was eventually a message about copy failure. Whenn I checked "/dev/sdg" no longer existed. The device now appeared to be "/dev/sdh". The system still showed "/dev/sdg1" and "/dev/sdg3" as mounted, but the device files did not exist. Power off was the only way I could shutdown. A third try got me installed with the live KDE. After reboot, the devices were: /dev/sda internal hard drive /dev/sdb external drive to which I had installed /dev/sdc through /dev/sdf - memory card slots. After the final stages of install (which had errors), I started having "command not found" errors. It was very difficult to investigate, since the basic shell commands were not available. I did: cd /dev echo sd? And that showed: sda sdc sdd sde sdf sdg So it looks as if what was "/dev/sdb" at boot had become "/dev/sdg" I powered off, rebooted. This happened twice more. --------- My previous install on this external drive was 20140721, installed with 64bit DVD. I did not have any problems with that. It is possible that my external drive is suddenly failing. I don't see any other symptoms of disk failure. I guess I could install 13.1 or 20140721 and see if the problem still occurs. 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 11

[Bug 822338] New: USB3.0 chip VL800 driver hangs and crashes
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=822338 https://bugzilla.novell.com/show_bug.cgi?id=822338#c0 Summary: USB3.0 chip VL800 driver hangs and crashes Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: volker3204(a)paradise.net.nz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=541851) --> (http://bugzilla.novell.com/attachment.cgi?id=541851) kernel oops screen photo User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.7.2 Safari/534.34 The VIA VL800 chip for USB3.0 with PCIe connection is not functional. syslog contains a huge number of 2013-05-21T06:08:06.622511+00:00 linux kernel: [ 257.484036] xhci_hcd 0000:04:00.0: Timeout while waiting for a slot 2013-05-21T06:08:06.622540+00:00 linux kernel: [ 257.484051] hub 4-0:1.0: couldn't allocate port 4 usb_device 2013-05-21T06:10:04.206514+00:00 linux kernel: [ 375.068037] xhci_hcd 0000:04:00.0: Do not support expand command ring 2013-05-21T06:10:04.206543+00:00 linux kernel: [ 375.068048] xhci_hcd 0000:04:00.0: ERR: No room for command on command ring 2013-05-21T06:10:04.206548+00:00 linux kernel: [ 375.068056] hub 4-0:1.0: couldn't allocate port 4 usb_device and on a system with oS 12.1: May 29 21:53:42 tui udevd[5701]: timeout: killing '/sbin/blkid -o udev -p /dev/sdd' [5924] May 29 21:53:42 tui udevd[5704]: timeout: killing '/sbin/blkid -o udev -p /dev/sde' [5930] May 29 21:53:42 tui udevd[5624]: timeout: killing '/sbin/blkid -o udev -p /dev/sdf' [5931] May 29 21:53:42 tui udevd[5641]: timeout: killing '/sbin/blkid -o udev -p /dev/sdg' [5932] With this USB3.0 hardware connected the system goes effectively dead and the hardware has to be removed. Reproducible: Always Steps to Reproduce: 1. Plug in some hardware with a PCIe bus and a Via VL800 chip. 2. Boot. 3. Gets here only if you're lucky. Actual Results: Many hangs while booting, depending on the moon, the system may not finish booting. It may work better with a CF card inserted into the reader when booting. Where I could get connection to the flash card or USB3.0 stick, it soon turned into an IO error with the flash device being disconnected by the driver. Once on oS 12.3 I has a solid oops, see screen shot attached. It seems that Linux support for VL800 is very flaky. http://askubuntu.com/questions/163227/why-doesnt-my-usb-3-0-pci-e-card-work… http://ubuntuforums.org/showthread.php?t=1875917 My test device is PCIe x1 connected USB3.0 hub with card reader in 2.5" form factor. Like this: http://www.aliexpress.com/snapshot/231863288.html But I doubt that matters. -- 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