September 2014 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 894296] New: supertux and supertux2 conflict
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=894296 https://bugzilla.novell.com/show_bug.cgi?id=894296#c0 Summary: supertux and supertux2 conflict Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: Other OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: joop.boonen(a)boonen.org ReportedBy: bwiedemann(a)suse.com QAContact: qa-bugs(a)suse.de CC: prusnak(a)opensuse.org Found By: Development Blocker: --- When installing supertux and supertux2 from games repo on openSUSE Factory, zypper complained File /usr/share/pixmaps/supertux.png from install of supertux2-0.3.4-1.88.x86_64(games) conflicts with file from install of supertux-0.1.3-49.38.x86_64(games) IMHO, supertux2 should ship a supertux2.png 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 2

[Bug 893999] New: Virtualization/libvirt: Bug
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=893999 https://bugzilla.novell.com/show_bug.cgi?id=893999#c0 Summary: Virtualization/libvirt: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: jfehlig(a)suse.com ReportedBy: bjoernv(a)arcor.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- The latest version of libvirtd-daemon (libvirt-daemon-1.2.7-420.1.x86_64) contains syntax errors in the Apparmor configuration file /etc/apparmor.d/abstractions/libvirt-lxc. I use apparmor from openSUSE 13.1 main repositories including updates: apparmor-docs-2.8.2-4.13.1.noarch apparmor-parser-2.8.2-4.13.1.x86_64 apparmor-profiles-2.8.2-4.13.1.noarch apparmor-utils-2.8.2-4.13.1.noarch libapparmor1-2.8.2-4.13.1.x86_64 libapparmor1-32bit-2.8.2-4.13.1.x86_64 pam_apparmor-2.8.2-4.13.1.x86_64 pam_apparmor-32bit-2.8.2-4.13.1.x86_64 patterns-openSUSE-apparmor-13.1-13.6.1.x86_64 patterns-openSUSE-apparmor_opt-13.1-13.6.1.x86_64 perl-apparmor-2.8.2-4.13.1.x86_64 yast2-apparmor-3.0.1-2.1.4.noarch Testing command: $ aa-logprof abstractions/libvirt-lxc contains syntax errors. Line [ umount,] If I comment out this line additional errors follow. -- 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 855537] New: USB2.0 port doesn't work in openSUSE
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=855537 https://bugzilla.novell.com/show_bug.cgi?id=855537#c0 Summary: USB2.0 port doesn't work in openSUSE Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: 64bit OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: lym418(a)Hotmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 The situation is that my computer has two USB ports.One is USB 2.0 and one is USB3.0 When I run openSUSE,the USB3.0 works properly,but USB2.0doesn't work(it looks that it cannot detect any devices inserted). But in windows both ports work properly. PS.No usb devices can be detected but the phone can be charged though USB2.0 port. Reproducible: Always Steps to Reproduce: 1.disconnected my mouse from USB3.0 port 2.Connect my mouse into USB2.0 port 3.disconnect mouse from USB2.0 and connect it to USB3.0 Actual Results: After step 1: mouse disconnected After step 2: Mouse doesn't have any change(not detected,the light of mouse doesn't flash) After step 3: mouse work properly Expected Results: No matter which port is used the mouse should be working properly. I use command lsusb the result is shown as following: lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 002: ID 1532:0037 Razer USA, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0018 Elan Microelectronics Corp. Bus 001 Device 004: ID 8087:07da Intel Corp. Bus 001 Device 005: ID 04f2:b328 Chicony Electronics Co., Ltd it shows USB2.0 exist. dmesg | grep USB [ 0.190016] ACPI: bus type USB registered [ 0.576972] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 0.577171] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1 [ 0.587016] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00 [ 0.587038] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 0.587040] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.587172] hub 1-0:1.0: USB hub found [ 0.587465] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2 [ 0.597019] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00 [ 0.597039] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 0.597041] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.597156] hub 2-0:1.0: USB hub found [ 0.597304] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 0.597306] uhci_hcd: USB Universal Host Controller Interface driver [ 0.609385] usbhid: USB HID core driver [ 0.889212] usb 1-1: new high-speed USB device number 2 using ehci-pci [ 1.003690] usb 1-1: New USB device found, idVendor=8087, idProduct=0024 [ 1.003695] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.003945] hub 1-1:1.0: USB hub found [ 1.107301] usb 2-1: new high-speed USB device number 2 using ehci-pci [ 1.221795] usb 2-1: New USB device found, idVendor=8087, idProduct=0024 [ 1.221802] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.222222] hub 2-1:1.0: USB hub found [ 1.297573] usb 1-1.1: new full-speed USB device number 3 using ehci-pci [ 1.385590] usb 1-1.1: New USB device found, idVendor=04f3, idProduct=0018 [ 1.385598] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.467587] usb 1-1.2: new full-speed USB device number 4 using ehci-pci [ 1.488936] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3 [ 1.489131] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.489134] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.492795] hub 3-0:1.0: USB hub found [ 1.493336] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4 [ 1.493360] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003 [ 1.493362] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.493491] hub 4-0:1.0: USB hub found [ 1.557334] usb 1-1.2: New USB device found, idVendor=8087, idProduct=07da [ 1.557339] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.630685] usb 1-1.3: new high-speed USB device number 5 using ehci-pci [ 1.813000] usb 1-1.3: New USB device found, idVendor=04f2, idProduct=b328 [ 1.813004] usb 1-1.3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 1.813007] usb 1-1.3: Product: USB 2.0 Camera [ 1.969722] usb 3-1: new full-speed USB device number 2 using xhci_hcd [ 1.983005] usb 3-1: New USB device found, idVendor=1532, idProduct=0037 [ 1.983008] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1.984694] hid-generic 0003:1532:0037.0002: input,hidraw0: USB HID v1.11 Mouse [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input0 [ 1.986820] hid-generic 0003:1532:0037.0003: input,hidraw1: USB HID v1.11 Keyboard [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input1 [ 1.987548] hid-generic 0003:1532:0037.0004: input,hidraw2: USB HID v1.11 Keyboard [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input2 [ 9.169171] hid-multitouch 0003:04F3:0018.0001: input,hiddev0,hidraw3: USB HID v1.11 Device [ELAN Touchscreen] on usb-0000:00:1a.0-1.1/input0 [ 9.686122] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (04f2:b328) [ 9.697297] input: USB 2.0 Camera as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input13 [ 9.697359] USB Video Class driver (1.1.1) [ 7953.606626] usb 3-1: USB disconnect, device number 2 [ 7961.134882] usb 3-1: new full-speed USB device number 3 using xhci_hcd [ 7961.148478] usb 3-1: New USB device found, idVendor=1532, idProduct=0037 [ 7961.148481] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 7961.150352] hid-generic 0003:1532:0037.0005: input,hidraw0: USB HID v1.11 Mouse [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input0 [ 7961.152357] hid-generic 0003:1532:0037.0006: input,hidraw1: USB HID v1.11 Keyboard [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input1 [ 7961.153070] hid-generic 0003:1532:0037.0007: input,hidraw2: USB HID v1.11 Keyboard [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input2 USB device found in the situation when mouse is inserted into USB3.0 I used vi /proc/bus/input/devices to see the devices connected to the computer(at this time I connect my mouse to USB2.0) I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input0 U: Uniq= H: Handlers=sysrq kbd event0 B: PROP=0 B: EV=120013 B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe B: MSC=10 B: LED=7 I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input1 U: Uniq= H: Handlers=mouse0 event1 B: PROP=5 B: EV=b B: KEY=e520 10000 0 0 0 0 B: ABS=660800011000003 I: Bus=0019 Vendor=0000 Product=0005 Version=0000 N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2 U: Uniq= H: Handlers=event2 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10000000000000 0 I: Bus=0019 Vendor=0000 Product=0006 Version=0000 N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b00000000 0 0 0 I: Bus=0010 Vendor=104d Product=0000 Version=0000 N: Name="Sony Vaio Keys" P: Phys= S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/SNY5001:00/input/input8 U: Uniq= H: Handlers=kbd event8 rfkill B: PROP=0 B: EV=13 B: KEY=1f160f0000 c00000000 10010000000000 200000000 600f00102c00 380000240300400 e000000000000 0 B: MSC=10 I: Bus=0010 Vendor=104d Product=0000 Version=0000 N: Name="Sony Vaio Jogdial" P: Phys= S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/SNY5001:00/input/input9 U: Uniq= H: Handlers=mouse2 event9 B: PROP=0 B: EV=7 B: KEY=40000 0 0 0 0 B: REL=100 I: Bus=0003 Vendor=04f2 Product=b328 Version=2917 N: Name="USB 2.0 Camera" P: Phys=usb-0000:00:1a.0-1.3/button S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input10 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=100000 0 0 0 I: Bus=0010 Vendor=001f Product=0001 Version=0100 N: Name="PC Speaker" P: Phys=isa0061/input0 S: Sysfs=/devices/platform/pcspkr/input/input11 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=40001 B: SND=6 I: Bus=0003 Vendor=04f3 Product=0018 Version=0111 N: Name="ELAN Touchscreen" P: Phys=usb-0000:00:1a.0-1.1/input0 S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input12 U: Uniq= H: Handlers=mouse3 event12 B: PROP=2 B: EV=b B: KEY=400 0 0 0 0 0 B: ABS=3273800000000003 I: Bus=0019 Vendor=0000 Product=0000 Version=0000 N: Name="Acer BMA150 accelerometer" P: Phys=wmi/input1 S: Sysfs=/devices/virtual/input/input13 U: Uniq= H: Handlers=event13 js0 B: PROP=0 B: EV=9 B: ABS=7 I: Bus=0001 Vendor=10ec Product=0269 Version=0001 N: Name="HDA Digital PCBeep" P: Phys=card0/codec#0/beep0 S: Sysfs=/devices/pci0000:00/0000:00:1b.0/input/input14 U: Uniq= H: Handlers=kbd event14 B: PROP=0 B: EV=40001 B: SND=6 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input15 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input16 U: Uniq= H: Handlers=event16 B: PROP=0 B: EV=21 B: SW=4 So this thing is that I cannot found the mouse I inserted. when I use command sudo demsg | tail Those result is in the situation when the mouse is in USB2.0 port sudo dmesg | tail root's password: [ 2091.493842] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:3c:07:54:54:be:c4:86:dd SRC=fe80:0000:0000:0000:3e07:54ff:fe54:bec4 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=1356 TC=0 HOPLIMIT=255 FLOWLBL=600290 PROTO=UDP SPT=5353 DPT=5353 LEN=1316 [ 2145.622163] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:c8:bc:c8:94:46:1f:86:dd SRC=fe80:0000:0000:0000:cabc:c8ff:fe94:461f DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=202 TC=0 HOPLIMIT=255 FLOWLBL=936031 PROTO=UDP SPT=5353 DPT=5353 LEN=162 [ 2146.632739] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:c8:bc:c8:94:46:1f:86:dd SRC=fe80:0000:0000:0000:cabc:c8ff:fe94:461f DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=202 TC=0 HOPLIMIT=255 FLOWLBL=936031 PROTO=UDP SPT=5353 DPT=5353 LEN=162 [ 2158.723799] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:c8:bc:c8:94:46:1f:86:dd SRC=fe80:0000:0000:0000:cabc:c8ff:fe94:461f DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=202 TC=0 HOPLIMIT=255 FLOWLBL=936031 PROTO=UDP SPT=5353 DPT=5353 LEN=162 [ 2185.816563] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:28:37:37:42:d2:8d:86:dd SRC=fe80:0000:0000:0000:2a37:37ff:fe42:d28d DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=269 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=229 [ 2207.235648] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:c8:bc:c8:94:46:1f:86:dd SRC=fe80:0000:0000:0000:cabc:c8ff:fe94:461f DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=285 TC=0 HOPLIMIT=255 FLOWLBL=936031 PROTO=UDP SPT=5353 DPT=5353 LEN=245 [ 2211.370625] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:c8:bc:c8:94:46:1f:86:dd SRC=fe80:0000:0000:0000:cabc:c8ff:fe94:461f DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=285 TC=0 HOPLIMIT=255 FLOWLBL=936031 PROTO=UDP SPT=5353 DPT=5353 LEN=245 [ 2211.691327] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:70:cd:60:87:be:92:86:dd SRC=fe80:0000:0000:0000:72cd:60ff:fe87:be92 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 OPT ( ) PROTO=ICMPv6 TYPE=131 CODE=0 [ 2215.348428] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:70:cd:60:87:be:92:86:dd SRC=fe80:0000:0000:0000:72cd:60ff:fe87:be92 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0 OPT ( ) PROTO=ICMPv6 TYPE=131 CODE=0 [ 2231.710295] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:c8:bc:c8:94:46:1f:86:dd SRC=fe80:0000:0000:0000:cabc:c8ff:fe94:461f DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=750 TC=0 HOPLIMIT=255 FLOWLBL=936031 PROTO=UDP SPT=5353 DPT=5353 LEN=710 The result following is got when the mouse is disconnected from USB2.0 and connect to USB3.0 li@linux-ednq:~> sudo dmesg | tail [ 2284.294718] usb 3-1: New USB device found, idVendor=1532, idProduct=0037 [ 2284.294725] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2284.294728] usb 3-1: Product: Razer DeathAdder 2013 [ 2284.294731] usb 3-1: Manufacturer: Razer [ 2284.296235] input: Razer Razer DeathAdder 2013 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/input/input22 [ 2284.296449] hid-generic 0003:1532:0037.000A: input,hidraw0: USB HID v1.11 Mouse [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input0 [ 2284.298359] input: Razer Razer DeathAdder 2013 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.1/input/input23 [ 2284.298525] hid-generic 0003:1532:0037.000B: input,hidraw1: USB HID v1.11 Keyboard [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input1 [ 2284.299162] input: Razer Razer DeathAdder 2013 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.2/input/input24 [ 2284.299244] hid-generic 0003:1532:0037.000C: input,hidraw2: USB HID v1.11 Keyboard [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input2 After that disconnect the mouse from USB3.0 then connect it to USB2.0 sudo dmesg | tail [ 2284.296449] hid-generic 0003:1532:0037.000A: input,hidraw0: USB HID v1.11 Mouse [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input0 [ 2284.298359] input: Razer Razer DeathAdder 2013 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.1/input/input23 [ 2284.298525] hid-generic 0003:1532:0037.000B: input,hidraw1: USB HID v1.11 Keyboard [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input1 [ 2284.299162] input: Razer Razer DeathAdder 2013 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.2/input/input24 [ 2284.299244] hid-generic 0003:1532:0037.000C: input,hidraw2: USB HID v1.11 Keyboard [Razer Razer DeathAdder 2013] on usb-0000:00:14.0-1/input2 [ 2293.186455] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:a8:20:66:30:52:ea:86:dd SRC=fe80:0000:0000:0000:aa20:66ff:fe30:52ea DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=158 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=118 [ 2313.204435] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:3c:07:54:54:be:c4:86:dd SRC=fe80:0000:0000:0000:3e07:54ff:fe54:bec4 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=1356 TC=0 HOPLIMIT=255 FLOWLBL=600290 PROTO=UDP SPT=5353 DPT=5353 LEN=1316 [ 2333.146682] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:70:cd:60:87:be:92:86:dd SRC=fe80:0000:0000:0000:72cd:60ff:fe87:be92 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=549 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=509 [ 2361.510882] usb 3-1: USB disconnect, device number 6 [ 2364.586477] SFW2-INext-DROP-DEFLT IN=enp14s0 OUT= MAC=33:33:00:00:00:fb:3c:07:54:30:f3:e3:86:dd SRC=fe80:0000:0000:0000:3e07:54ff:fe30:f3e3 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=123 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=83 Then I found the same problem on the Internet: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172908 PS.My computer is Sony SVT13126CG,so it shows that all Sony T series computers have the same problem. After that I found https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210858 The solution he proposed is rewrite the kernel of Linux. << changed pci-quirks.c in v3.11 with --- pci-quirks.c~ 2013-08-06 07:25:47.000000000 -0400 +++ pci-quirks.c 2013-08-30 14:23:47.597891192 -0400 @@ -921,9 +921,10 @@ writel(val, base + ext_cap_offset + XHCI_LEGACY_CONTROL_OFFSET); hc_init: + /* if (usb_is_intel_switchable_xhci(pdev)) usb_enable_xhci_ports(pdev); - + */ op_reg_base = base + XHCI_HC_LENGTH(readl(base)); /* Wait for the host controller to be ready before writing any rebuilt the kernel and the USB 2.0 ports now work! >> So I updated my kernel li@linux-ednq:~> uname -r 3.13.0-rc3-2.g44df1ce-desktop It doesn't work. -- 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 559697] New: Brother USB-scanners stop with errors, related to libusb compatibility library
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

http://bugzilla.novell.com/show_bug.cgi?id=559697 http://bugzilla.novell.com/show_bug.cgi?id=559697#c0 Summary: Brother USB-scanners stop with errors, related to libusb compatibility library Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mueller(a)uni-trier.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.5) Gecko/20091103 SUSE/3.5.5-1.1.2 Firefox/3.5.5 Using OpenSuse 11.2 (both 32bit/64bit versions), several USB-scanners from Brother (at least: MFC-215C, MFC-590, MFC-8440, DCP-130C, DCP-135C) do not work. Starting a scan, they all stop after transmitting a small amount of data and give an error message (I/O error). So only scans with a small resolution or of a very small area are possible. Downgrading from libusb-0_1-4-0.1.13-2.2.x86_64 to libusb-0_1-4-0.1.12-139.1.1.x86_64 or fromlibusb-0_1-4 0.1.13-2.2-i586 to libusb-0_1-4-0.1.12-139.1.1.i586 solves the problem completely BTW: To get the scanners to work at all, third party drivers from Brother have to be installed (in my case brscan-0.2.4-0.x86_64.rpm) first. Reproducible: Always Steps to Reproduce: 1. Install brscan-0.2.4-0.x86_64 and a brother USB-scanner 2. Use xsane to make a scan with colour and a medium resolution. 3. The scanner stops after a few centimeters and xsane returns an I/O error Alternatively: Use "scanimage > /dev/null", leading to "scanimage: sane_read: Error during device I/O" -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 59

[Bug 877768] New: VUL-0: CVE-2014-1740: google-chrome: websocket UAF
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=877768 https://bugzilla.novell.com/show_bug.cgi?id=877768#c0 Summary: VUL-0: CVE-2014-1740: google-chrome: websocket UAF Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: tittiatcoke(a)gmail.com ReportedBy: krahmer(a)suse.com QAContact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2014-1740 Multiple use-after-free vulnerabilities in net/websockets/websocket_job.cc in the WebSockets implementation in Google Chrome before 34.0.1847.137 allow remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to WebSocketJob deletion. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-1740 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-1740 http://googlechromereleases.blogspot.com/2014/05/stable-channel-update.html https://code.google.com/p/chromium/issues/detail?id=358038 https://src.chromium.org/viewvc/chrome?revision=261707&view=revision -- 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 893142] New: Error message from systemd about ipmiseld.service
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=893142 https://bugzilla.novell.com/show_bug.cgi?id=893142#c0 Summary: Error message from systemd about ipmiseld.service Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: freek(a)opensuse.org 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 The error message shows: systemd[1]: Configuration file /usr/lib/systemd/system/ipmiseld.service is marked executable. Please remove executable permission bits. Proceeding anyway. 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 6

[Bug 894381] New: invisible underscores in OBS webui
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=894381 https://bugzilla.novell.com/show_bug.cgi?id=894381#c0 Summary: invisible underscores in OBS webui Classification: Internal Novell Products Product: openSUSE Build Service Version: master Platform: All OS/Version: All Status: NEW Severity: Major Priority: P5 - None Component: webui AssignedTo: hvogel(a)suse.com ReportedBy: bwiedemann(a)suse.com QAContact: adrian(a)suse.com Found By: Development Blocker: --- Created an attachment (id=604363) --> (http://bugzilla.novell.com/attachment.cgi?id=604363) screenshot of bug in firefox at default font size OBS webui CSS or something has an annoying bug that sometimes prevents underscores from being displayed e.g. see https://bugzilla.novell.com/show_bug.cgi?id=893142#c3 -- 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 893544] New: default /proc/sys/dev/raid/speed_limit_min too low for nowaday's disks
by bugzilla_noreply＠novell.com 01 Sep '14

01 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=893544 https://bugzilla.novell.com/show_bug.cgi?id=893544#c0 Summary: default /proc/sys/dev/raid/speed_limit_min too low for nowaday's disks Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- The default for /proc/sys/dev/raid/speed_limit_min is too low for nowaday's disk sizes: # cat /proc/sys/dev/raid/speed_limit_min 1000 This means it might take _days_ to recover the RAID if you have TB-size disks and some load on the system. Please change the default to a higher value - I'd recommend _at least_ 10000 (= 10 MB/s). -- 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