[opensuse-factory] USB mouse not working after boot beginning from kernel 4.4.0
Hardware: HP ZBook 15 G2, Logitech M-UAS 144 After the big drawback beginning from kernel 3.19, when nouveau began to be broken for the above hardware (until now), there is another one, introduced with kernel 4.4.0 in Tumbleweed: After boot/reboot, the connected USB mouse does not initially work in both cases, connected to the docking station and connected directly to the notebook. After disconnecting and reconnecting it physically the mouse works immediately. Sometimes I have been noticing the same behavior for the USB keyboard, but not everytime. I hadn't have this behavior before 4.4.0. Still not solved for 4.4.1. I cannot guarantee that this happens along with another update that came beside to kernel 4.4.0, usually I do a 'zypper dup'. Using sddm as display manager. In /var/log/messages I haven't found anything suspect, the USB devices are initialized and the mouse is actually recognized but does not work after this one: 2016-02-24T14:01:22.775406+01:00 rkrell kernel: [ 5.821627] usb 3-2: New USB device found, idVendor=046d, idProduct=c062 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821642] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821643] usb 3-2: Product: USB Laser Mouse 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821645] usb 3-2: Manufacturer: Logitech 2016-02-24T14:01:22.775409+01:00 rkrell kernel: [ 5.821850] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes The USB keyboard works already in this state. After disconnecting and connecting I get: 2016-02-24T14:02:14.951655+01:00 rkrell kernel: [ 60.981778] usb 3-2: USB disconnect, device number 3 2016-02-24T14:02:20.943684+01:00 rkrell kernel: [ 66.972056] usb 3-2: new low-speed USB device number 9 using xhci_hcd 2016-02-24T14:02:21.131609+01:00 rkrell kernel: [ 67.161892] usb 3-2: New USB device found, idVendor=046d, idProduct=c062 2016-02-24T14:02:21.131628+01:00 rkrell kernel: [ 67.161900] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 2016-02-24T14:02:21.131630+01:00 rkrell kernel: [ 67.161904] usb 3-2: Product: USB Laser Mouse 2016-02-24T14:02:21.131632+01:00 rkrell kernel: [ 67.161906] usb 3-2: Manufacturer: Logitech 2016-02-24T14:02:21.131633+01:00 rkrell kernel: [ 67.162262] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes 2016-02-24T14:02:21.135598+01:00 rkrell kernel: [ 67.167613] input: Logitech USB Laser Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:046D:C 062.0003/input/input28 2016-02-24T14:02:21.135620+01:00 rkrell kernel: [ 67.167989] hid-generic 0003:046D:C062.0003: input,hidraw0: USB HID v1.10 Mouse [Logitech USB Laser Mouse] o n usb-0000:00:14.0-2/input0 and the mouse is functional immediately. Any further victim of this bug, hint, is this a known problem or is there a workaround? René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2016-02-24 at 14:09 +0100, René Krell wrote:
In /var/log/messages I haven't found anything suspect, the USB devices are initialized and the mouse is actually recognized but does not work after this one:
2016-02-24T14:01:22.775406+01:00 rkrell kernel: [ 5.821627] usb 3-2: New USB device found, idVendor=046d, idProduct=c062 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821642] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821643] usb 3-2: Product: USB Laser Mouse 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821645] usb 3-2: Manufacturer: Logitech 2016-02-24T14:01:22.775409+01:00 rkrell kernel: [ 5.821850] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
It should resume your device, not find a new one. More context. Regards Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2016-02-24 14:13 GMT+01:00 Oliver Neukum:
On Wed, 2016-02-24 at 14:09 +0100, René Krell wrote:
In /var/log/messages I haven't found anything suspect, the USB devices are initialized and the mouse is actually recognized but does not work after this one:
2016-02-24T14:01:22.775406+01:00 rkrell kernel: [ 5.821627] usb 3-2: New USB device found, idVendor=046d, idProduct=c062 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821642] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821643] usb 3-2: Product: USB Laser Mouse 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821645] usb 3-2: Manufacturer: Logitech 2016-02-24T14:01:22.775409+01:00 rkrell kernel: [ 5.821850] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
It should resume your device, not find a new one. More context.
Regards Oliver
I can send you the full log to your private mail, if you'd be able to find anything more. I would be glad if I'd know at least the reason. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2016-02-24 at 14:22 +0100, René Krell wrote:
2016-02-24 14:13 GMT+01:00 Oliver Neukum:
It should resume your device, not find a new one. More context.
Regards Oliver
I can send you the full log to your private mail, if you'd be able to find anything more. I would be glad if I'd know at least the reason.
Please make a bugzilla against TW Regards Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
This seems to be for kernel experts, after a look into https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.2 I found: commit bfa2ee5ddf3dd102f2ffc9842225591461a08f16 Author: Lu Baolu <baolu.lu@linux.intel.com> Date: Tue Jan 26 17:50:05 2016 +0200 usb: xhci: handle both SSIC ports in PME stuck quirk commit fa89537783cb442263fa5a14df6c7693eaf32f11 upstream. Commit abce329c27b3 ("xhci: Workaround to get D3 working in Intel xHCI") adds a workaround for a limitation of PME storm caused by SSIC port in some Intel SoCs. This commit only handled one SSIC port, while there are actually two SSIC ports in the chips. This patch handles both SSIC ports. Without this fix, users still see PME storm. Signed-off-by: Zhuang Jin Can <jin.can.zhuang@intel.com> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com> Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> In /var/log/messages I see: 2016-02-24T14:01:22.774950+01:00 rkrell kernel: [ 2.454294] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold 2016-02-24T14:01:22.774950+01:00 rkrell kernel: [ 2.454495] pci 0000:00:14.0: [8086:8c31] type 00 class 0x0c0330 2016-02-24T14:01:22.774951+01:00 rkrell kernel: [ 2.454520] pci 0000:00:14.0: reg 0x10: [mem 0xd0320000-0xd032ffff 64bit] 2016-02-24T14:01:22.774951+01:00 rkrell kernel: [ 2.454568] pci 0000:00:14.0: PME# supported from D3hot D3cold 2016-02-24T14:01:22.774951+01:00 rkrell kernel: [ 2.454659] pci 0000:00:14.0: System wakeup disabled by ACPI 2016-02-24T14:01:22.774952+01:00 rkrell kernel: [ 2.454700] pci 0000:00:16.0: [8086:8c3a] type 00 class 0x078000 2016-02-24T14:01:22.774952+01:00 rkrell kernel: [ 2.454726] pci 0000:00:16.0: reg 0x10: [mem 0xd0335000-0xd033500f 64bit] 2016-02-24T14:01:22.774953+01:00 rkrell kernel: [ 2.454783] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold 2016-02-24T14:01:22.774954+01:00 rkrell kernel: [ 2.454911] pci 0000:00:19.0: [8086:153a] type 00 class 0x020000 2016-02-24T14:01:22.774954+01:00 rkrell kernel: [ 2.454935] pci 0000:00:19.0: reg 0x10: [mem 0xd0300000-0xd031ffff] 2016-02-24T14:01:22.774954+01:00 rkrell kernel: [ 2.454942] pci 0000:00:19.0: reg 0x14: [mem 0xd033b000-0xd033bfff] 2016-02-24T14:01:22.774955+01:00 rkrell kernel: [ 2.454950] pci 0000:00:19.0: reg 0x18: [io 0x6040-0x605f] 2016-02-24T14:01:22.774955+01:00 rkrell kernel: [ 2.455004] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold 2016-02-24T14:01:22.774956+01:00 rkrell kernel: [ 2.455092] pci 0000:00:19.0: System wakeup disabled by ACPI 2016-02-24T14:01:22.774957+01:00 rkrell kernel: [ 2.455133] pci 0000:00:1a.0: [8086:8c2d] type 00 class 0x0c0320 2016-02-24T14:01:22.774957+01:00 rkrell kernel: [ 2.455157] pci 0000:00:1a.0: reg 0x10: [mem 0xd033a000-0xd033a3ff] 2016-02-24T14:01:22.774957+01:00 rkrell kernel: [ 2.455221] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold 2016-02-24T14:01:22.774958+01:00 rkrell kernel: [ 2.455312] pci 0000:00:1a.0: System wakeup disabled by ACPI 2016-02-24T14:01:22.774958+01:00 rkrell kernel: [ 2.455353] pci 0000:00:1b.0: [8086:8c20] type 00 class 0x040300 2016-02-24T14:01:22.774959+01:00 rkrell kernel: [ 2.455378] pci 0000:00:1b.0: reg 0x10: [mem 0xd0330000-0xd0333fff 64bit] 2016-02-24T14:01:22.774959+01:00 rkrell kernel: [ 2.455440] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold 2016-02-24T14:01:22.774960+01:00 rkrell kernel: [ 2.455568] pci 0000:00:1c.0: [8086:8c10] type 01 class 0x060400 2016-02-24T14:01:22.774961+01:00 rkrell kernel: [ 2.455644] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold 2016-02-24T14:01:22.774961+01:00 rkrell kernel: [ 2.455828] pci 0000:00:1c.4: [8086:8c18] type 01 class 0x060400 2016-02-24T14:01:22.774961+01:00 rkrell kernel: [ 2.455898] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold 2016-02-24T14:01:22.774962+01:00 rkrell kernel: [ 2.456040] pci 0000:00:1c.4: System wakeup disabled by ACPI 2016-02-24T14:01:22.774962+01:00 rkrell kernel: [ 2.456081] pci 0000:00:1c.6: [8086:8c1c] type 01 class 0x060400 2016-02-24T14:01:22.774963+01:00 rkrell kernel: [ 2.456152] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold 2016-02-24T14:01:22.774964+01:00 rkrell kernel: [ 2.456293] pci 0000:00:1c.6: System wakeup disabled by ACPI 2016-02-24T14:01:22.774964+01:00 rkrell kernel: [ 2.456333] pci 0000:00:1c.7: [8086:8c1e] type 01 class 0x060400 2016-02-24T14:01:22.774964+01:00 rkrell kernel: [ 2.456403] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold 2016-02-24T14:01:22.774965+01:00 rkrell kernel: [ 2.456551] pci 0000:00:1c.7: System wakeup disabled by ACPI 2016-02-24T14:01:22.774965+01:00 rkrell kernel: [ 2.456592] pci 0000:00:1d.0: [8086:8c26] type 00 class 0x0c0320 2016-02-24T14:01:22.774965+01:00 rkrell kernel: [ 2.456617] pci 0000:00:1d.0: reg 0x10: [mem 0xd0339000-0xd03393ff] 2016-02-24T14:01:22.774967+01:00 rkrell kernel: [ 2.456682] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold 2016-02-24T14:01:22.774967+01:00 rkrell kernel: [ 2.456773] pci 0000:00:1d.0: System wakeup disabled by ACPI 2016-02-24T14:01:22.774967+01:00 rkrell kernel: [ 2.456815] pci 0000:00:1f.0: [8086:8c4f] type 00 class 0x060100 2016-02-24T14:01:22.774968+01:00 rkrell kernel: [ 2.457035] pci 0000:00:1f.2: [8086:8c03] type 00 class 0x010601 2016-02-24T14:01:22.774968+01:00 rkrell kernel: [ 2.457056] pci 0000:00:1f.2: reg 0x10: [io 0x6068-0x606f] 2016-02-24T14:01:22.774968+01:00 rkrell kernel: [ 2.457063] pci 0000:00:1f.2: reg 0x14: [io 0x6074-0x6077] 2016-02-24T14:01:22.774969+01:00 rkrell kernel: [ 2.457070] pci 0000:00:1f.2: reg 0x18: [io 0x6060-0x6067] 2016-02-24T14:01:22.774970+01:00 rkrell kernel: [ 2.457078] pci 0000:00:1f.2: reg 0x1c: [io 0x6070-0x6073] 2016-02-24T14:01:22.774970+01:00 rkrell kernel: [ 2.457085] pci 0000:00:1f.2: reg 0x20: [io 0x6020-0x603f] 2016-02-24T14:01:22.774971+01:00 rkrell kernel: [ 2.457092] pci 0000:00:1f.2: reg 0x24: [mem 0xd0338000-0xd03387ff] 2016-02-24T14:01:22.774971+01:00 rkrell kernel: [ 2.457126] pci 0000:00:1f.2: PME# supported from D3hot 2016-02-24T14:01:22.774971+01:00 rkrell kernel: [ 2.457247] pci 0000:00:1f.3: [8086:8c22] type 00 class 0x0c0500 2016-02-24T14:01:22.774972+01:00 rkrell kernel: [ 2.457263] pci 0000:00:1f.3: reg 0x10: [mem 0xd0334000-0xd03340ff 64bit] 2016-02-24T14:01:22.774972+01:00 rkrell kernel: [ 2.457282] pci 0000:00:1f.3: reg 0x20: [io 0xef80-0xef9f] 2016-02-24T14:01:22.774974+01:00 rkrell kernel: [ 2.457466] pci 0000:01:00.0: [10de:12b9] type 00 class 0x030000 2016-02-24T14:01:22.774974+01:00 rkrell kernel: [ 2.457490] pci 0000:01:00.0: reg 0x10: [mem 0xcf000000-0xcfffffff] 2016-02-24T14:01:22.774975+01:00 rkrell kernel: [ 2.457504] pci 0000:01:00.0: reg 0x14: [mem 0x70000000-0x7fffffff 64bit pref] 2016-02-24T14:01:22.774975+01:00 rkrell kernel: [ 2.457517] pci 0000:01:00.0: reg 0x1c: [mem 0x80000000-0x81ffffff 64bit pref] 2016-02-24T14:01:22.774975+01:00 rkrell kernel: [ 2.457527] pci 0000:01:00.0: reg 0x24: [io 0x5000-0x507f] 2016-02-24T14:01:22.774976+01:00 rkrell kernel: [ 2.457537] pci 0000:01:00.0: reg 0x30: [mem 0xfff80000-0xffffffff pref] 2016-02-24T14:01:22.775012+01:00 rkrell kernel: [ 2.457904] pci 0000:01:00.1: [10de:0e0f] type 00 class 0x040300 2016-02-24T14:01:22.775012+01:00 rkrell kernel: [ 2.457927] pci 0000:01:00.1: reg 0x10: [mem 0xd0000000-0xd0003fff] 2016-02-24T14:01:22.775012+01:00 rkrell kernel: [ 2.464437] pci 0000:00:01.0: PCI bridge to [bus 01] 2016-02-24T14:01:22.775013+01:00 rkrell kernel: [ 2.464440] pci 0000:00:01.0: bridge window [io 0x5000-0x5fff] 2016-02-24T14:01:22.775013+01:00 rkrell kernel: [ 2.464442] pci 0000:00:01.0: bridge window [mem 0xcf000000-0xd00fffff] 2016-02-24T14:01:22.775013+01:00 rkrell kernel: [ 2.464445] pci 0000:00:01.0: bridge window [mem 0x70000000-0x81ffffff 64bit pref] 2016-02-24T14:01:22.775014+01:00 rkrell kernel: [ 2.464516] acpiphp: Slot [1] registered 2016-02-24T14:01:22.775015+01:00 rkrell kernel: [ 2.464522] pci 0000:00:1c.0: PCI bridge to [bus 02-3a] 2016-02-24T14:01:22.775015+01:00 rkrell kernel: [ 2.464527] pci 0000:00:1c.0: bridge window [mem 0xb8000000-0xce0fffff] 2016-02-24T14:01:22.775016+01:00 rkrell kernel: [ 2.464533] pci 0000:00:1c.0: bridge window [mem 0x90000000-0xb1ffffff 64bit pref] 2016-02-24T14:01:22.775016+01:00 rkrell kernel: [ 2.464614] acpiphp: Slot [1-1] registered 2016-02-24T14:01:22.775016+01:00 rkrell kernel: [ 2.464648] pci 0000:00:1c.4: PCI bridge to [bus 3b-5b] 2016-02-24T14:01:22.775017+01:00 rkrell kernel: [ 2.464652] pci 0000:00:1c.4: bridge window [io 0x3000-0x4fff] 2016-02-24T14:01:22.775017+01:00 rkrell kernel: [ 2.464656] pci 0000:00:1c.4: bridge window [mem 0xb4000000-0xb7ffffff] 2016-02-24T14:01:22.775018+01:00 rkrell kernel: [ 2.464776] pci 0000:5c:00.0: [8086:088e] type 00 class 0x028000 2016-02-24T14:01:22.775019+01:00 rkrell kernel: [ 2.464876] pci 0000:5c:00.0: reg 0x10: [mem 0xd0200000-0xd0201fff 64bit] 2016-02-24T14:01:22.775019+01:00 rkrell kernel: [ 2.465132] pci 0000:5c:00.0: PME# supported from D0 D3hot D3cold 2016-02-24T14:01:22.775019+01:00 rkrell kernel: [ 2.472469] pci 0000:00:1c.6: PCI bridge to [bus 5c] 2016-02-24T14:01:22.775020+01:00 rkrell kernel: [ 2.472474] pci 0000:00:1c.6: bridge window [mem 0xd0200000-0xd02fffff] 2016-02-24T14:01:22.775020+01:00 rkrell kernel: [ 2.472582] pci 0000:5d:00.0: [10ec:5249] type 00 class 0xff0000 2016-02-24T14:01:22.775020+01:00 rkrell kernel: [ 2.472627] pci 0000:5d:00.0: reg 0x10: [mem 0xd0100000-0xd0100fff] 2016-02-24T14:01:22.775022+01:00 rkrell kernel: [ 2.472927] pci 0000:5d:00.0: supports D1 D2 2016-02-24T14:01:22.775022+01:00 rkrell kernel: [ 2.472928] pci 0000:5d:00.0: PME# supported from D1 D2 D3hot D3cold 2016-02-24T14:01:22.775022+01:00 rkrell kernel: [ 2.480465] pci 0000:00:1c.7: PCI bridge to [bus 5d] 2016-02-24T14:01:22.775023+01:00 rkrell kernel: [ 2.480471] pci 0000:00:1c.7: bridge window [mem 0xd0100000-0xd01fffff]
From this context, is it possible I'm infected by this sickness? Any expert?
2016-02-24 14:09 GMT+01:00 René Krell <renda.krell@gmail.com>:
Hardware: HP ZBook 15 G2, Logitech M-UAS 144
After the big drawback beginning from kernel 3.19, when nouveau began to be broken for the above hardware (until now), there is another one, introduced with kernel 4.4.0 in Tumbleweed: After boot/reboot, the connected USB mouse does not initially work in both cases, connected to the docking station and connected directly to the notebook. After disconnecting and reconnecting it physically the mouse works immediately. Sometimes I have been noticing the same behavior for the USB keyboard, but not everytime. I hadn't have this behavior before 4.4.0. Still not solved for 4.4.1. I cannot guarantee that this happens along with another update that came beside to kernel 4.4.0, usually I do a 'zypper dup'. Using sddm as display manager.
In /var/log/messages I haven't found anything suspect, the USB devices are initialized and the mouse is actually recognized but does not work after this one:
2016-02-24T14:01:22.775406+01:00 rkrell kernel: [ 5.821627] usb 3-2: New USB device found, idVendor=046d, idProduct=c062 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821642] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821643] usb 3-2: Product: USB Laser Mouse 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821645] usb 3-2: Manufacturer: Logitech 2016-02-24T14:01:22.775409+01:00 rkrell kernel: [ 5.821850] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
The USB keyboard works already in this state. After disconnecting and connecting I get:
2016-02-24T14:02:14.951655+01:00 rkrell kernel: [ 60.981778] usb 3-2: USB disconnect, device number 3 2016-02-24T14:02:20.943684+01:00 rkrell kernel: [ 66.972056] usb 3-2: new low-speed USB device number 9 using xhci_hcd 2016-02-24T14:02:21.131609+01:00 rkrell kernel: [ 67.161892] usb 3-2: New USB device found, idVendor=046d, idProduct=c062 2016-02-24T14:02:21.131628+01:00 rkrell kernel: [ 67.161900] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 2016-02-24T14:02:21.131630+01:00 rkrell kernel: [ 67.161904] usb 3-2: Product: USB Laser Mouse 2016-02-24T14:02:21.131632+01:00 rkrell kernel: [ 67.161906] usb 3-2: Manufacturer: Logitech 2016-02-24T14:02:21.131633+01:00 rkrell kernel: [ 67.162262] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes 2016-02-24T14:02:21.135598+01:00 rkrell kernel: [ 67.167613] input: Logitech USB Laser Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:046D:C 062.0003/input/input28 2016-02-24T14:02:21.135620+01:00 rkrell kernel: [ 67.167989] hid-generic 0003:046D:C062.0003: input,hidraw0: USB HID v1.10 Mouse [Logitech USB Laser Mouse] o n usb-0000:00:14.0-2/input0
and the mouse is functional immediately.
Any further victim of this bug, hint, is this a known problem or is there a workaround?
René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Just for the record, still the same in Tumbleweed 20160303 using kernel 4.4.3. After system start, I got to reconnect the USB mouse manually to get it working. The problem appears already in the sddm displaymanager. The problem appeared after introducing kernel 4.4.0. 2016-02-24 14:09 GMT+01:00 René Krell <renda.krell@gmail.com>:
Hardware: HP ZBook 15 G2, Logitech M-UAS 144
After the big drawback beginning from kernel 3.19, when nouveau began to be broken for the above hardware (until now), there is another one, introduced with kernel 4.4.0 in Tumbleweed: After boot/reboot, the connected USB mouse does not initially work in both cases, connected to the docking station and connected directly to the notebook. After disconnecting and reconnecting it physically the mouse works immediately. Sometimes I have been noticing the same behavior for the USB keyboard, but not everytime. I hadn't have this behavior before 4.4.0. Still not solved for 4.4.1. I cannot guarantee that this happens along with another update that came beside to kernel 4.4.0, usually I do a 'zypper dup'. Using sddm as display manager. ... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
lørdag den 5. marts 2016 00.17.52 CET skrev René Krell:
Just for the record, still the same in Tumbleweed 20160303 using kernel 4.4.3. After system start, I got to reconnect the USB mouse manually to get it working. The problem appears already in the sddm displaymanager. The problem appeared after introducing kernel 4.4.0.
For me the touchpad is insanely fast when scrolling. Seems to be regression from Plasma 5.5.4 to 5.5.5, anybody else facing this? Bo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Not here. The touchpad scrolling is working fine for me in Plasma 5.5.5 on a HP ZBook 15. This thread of discussion is different, the USB mouse device does not work after booting without manually reconnecting it, appears already in SDDM before logging on to any other window manager and seems to be more a kernel problem. 2016-03-05 0:25 GMT+01:00 Bo Simonsen <bo@geekworld.dk>:
lørdag den 5. marts 2016 00.17.52 CET skrev René Krell:
Just for the record, still the same in Tumbleweed 20160303 using kernel 4.4.3. After system start, I got to reconnect the USB mouse manually to get it working. The problem appears already in the sddm displaymanager. The problem appeared after introducing kernel 4.4.0.
For me the touchpad is insanely fast when scrolling. Seems to be regression from Plasma 5.5.4 to 5.5.5, anybody else facing this?
Bo
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op zaterdag 5 maart 2016 00:37:46 CET schreef René Krell:
Not here. The touchpad scrolling is working fine for me in Plasma 5.5.5 on a HP ZBook 15. This thread of discussion is different, the USB mouse device does not work after booting without manually reconnecting it, appears already in SDDM before logging on to any other window manager and seems to be more a kernel problem.
2016-03-05 0:25 GMT+01:00 Bo Simonsen <bo@geekworld.dk>:
lørdag den 5. marts 2016 00.17.52 CET skrev René Krell:
Just for the record, still the same in Tumbleweed 20160303 using kernel 4.4.3. After system start, I got to reconnect the USB mouse manually to get it working. The problem appears already in the sddm displaymanager. The problem appeared after introducing kernel 4.4.0.
For me the touchpad is insanely fast when scrolling. Seems to be regression from Plasma 5.5.4 to 5.5.5, anybody else facing this?
Seeing this too.
Bo
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Samstag, 5. März 2016, 00:25:34 CET schrieb Bo Simonsen:
lørdag den 5. marts 2016 00.17.52 CET skrev René Krell:
Just for the record, still the same in Tumbleweed 20160303 using kernel 4.4.3. After system start, I got to reconnect the USB mouse manually to get it working. The problem appears already in the sddm displaymanager. The problem appeared after introducing kernel 4.4.0.
For me the touchpad is insanely fast when scrolling. Seems to be regression from Plasma 5.5.4 to 5.5.5, anybody else facing this?
Yes, I am facing this, too, on a machine with a HiDPI display. Another machine with a lowres display 1366x900 does not have this problem. This is with kernel 4.4.3. Herbert -- “Only two things are infinite, the universe and human stupidity, and I’m not sure about the former.” Albert Einstein -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Samstag, 5. März 2016, 00:25:34 CET schrieb Bo Simonsen:
lørdag den 5. marts 2016 00.17.52 CET skrev René Krell:
Just for the record, still the same in Tumbleweed 20160303 using kernel 4.4.3. After system start, I got to reconnect the USB mouse manually to get it working. The problem appears already in the sddm displaymanager. The problem appeared after introducing kernel 4.4.0.
For me the touchpad is insanely fast when scrolling. Seems to be regression from Plasma 5.5.4 to 5.5.5, anybody else facing this?
I don't think this has something to do with the kernel, as I see the same with Plasma 5.5.5 on Leap. There is already the following upstream bug https://bugs.kde.org/show_bug.cgi? id=359945 which also contains a workaround. Regards Christian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
lørdag den 5. marts 2016 18.53.59 CET skrev Christian Trippe:
Am Samstag, 5. März 2016, 00:25:34 CET schrieb Bo Simonsen:
lørdag den 5. marts 2016 00.17.52 CET skrev René Krell:
Just for the record, still the same in Tumbleweed 20160303 using kernel 4.4.3. After system start, I got to reconnect the USB mouse manually to get it working. The problem appears already in the sddm displaymanager. The problem appeared after introducing kernel 4.4.0.
For me the touchpad is insanely fast when scrolling. Seems to be regression from Plasma 5.5.4 to 5.5.5, anybody else facing this?
I don't think this has something to do with the kernel, as I see the same with Plasma 5.5.5 on Leap.
Nothing to do with the kernel, I did unfortunately just respond to the thread after noticing my fast touchpad. Should have started a new one, my apologies.
There is already the following upstream bug https://bugs.kde.org/show_bug.cgi? id=359945 which also contains a workaround.
Great, thanks! Bo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On zaterdag 5 maart 2016 00:25:34 CET Bo Simonsen wrote:
lørdag den 5. marts 2016 00.17.52 CET skrev René Krell:
Just for the record, still the same in Tumbleweed 20160303 using kernel 4.4.3. After system start, I got to reconnect the USB mouse manually to get it working. The problem appears already in the sddm displaymanager. The problem appeared after introducing kernel 4.4.0.
For me the touchpad is insanely fast when scrolling. Seems to be regression from Plasma 5.5.4 to 5.5.5, anybody else facing this?
Bo Yep, same to me. Settings do not seem to have an effect on this behaviour. My laptop has an ALPS-touchpad, what type does yours have?
I'm not sure whether it's got something to do with Plasma or with a driver update or so. Have you already found a solution? -- Met vriendelijke groet, Timo Diedering -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, 2016-03-05 at 00:17 +0100, René Krell wrote:
Just for the record, still the same in Tumbleweed 20160303 using kernel 4.4.3. After system start, I got to reconnect the USB mouse manually to get it working. The problem appears already in the sddm displaymanager. The problem appeared after introducing kernel 4.4.0.
Can you confirm that your issue persists and is independent of the touchpad issue reported later in this thread? drivers/hid has no obvious change and drivers/usb too many to review? Can you bisect the kernel? Regards Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2016-03-07 12:03 GMT+01:00 Oliver Neukum <oneukum@suse.com>:
On Sat, 2016-03-05 at 00:17 +0100, René Krell wrote:
Just for the record, still the same in Tumbleweed 20160303 using kernel 4.4.3. After system start, I got to reconnect the USB mouse manually to get it working. The problem appears already in the sddm displaymanager. The problem appeared after introducing kernel 4.4.0.
Can you confirm that your issue persists and is independent of the touchpad issue reported later in this thread?
Yes, still the same for kernel-default 4.4.3 in TW 20160305. I cannot see anything in common with the touchpad issues described above. The touchpad works fine for me, this is obviously an USB issue. I have to reconnect the device manually to get it working. I still cannot exclude a hardware problem, although I can't see any from the log. And after reconnecting, the USB mouse works for days without a problem. Did I miss something which leads from the USB mouse to the touchpad?
drivers/hid has no obvious change and drivers/usb too many to review?
The USB device details can be seen in the log I sent. I can tell the modules loaded.
Can you bisect the kernel?
Unfortunately, I have no idea how to do this. Any documentation on bisect, for OpenSUSE with regards of patches? René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2016-03-07 at 13:48 +0100, René Krell wrote:
Can you bisect the kernel?
Unfortunately, I have no idea how to do this. Any documentation on bisect, for OpenSUSE with regards of patches?
That is a problem. Could you identify the last kernel that worked? Regards Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello René, On 07.03.2016 13:48, René Krell wrote:
2016-03-07 12:03 GMT+01:00 Oliver Neukum <oneukum@suse.com>:
Can you bisect the kernel?
Unfortunately, I have no idea how to do this. Any documentation on bisect, for OpenSUSE with regards of patches?
I usually go this way for kernel bugs: * install kernel-vanilla * verify the bug is still there -> if not, blame openSUSE patches; exit 0 * now clone linux kernel git tree * build suse-kernel-vanilla config, boot, verify bug is still there * reset to kernel version $CURRENT-1, build, verify bug is gone * start bisecting as can be found in git bisect tutorials on the web. Note that this will take a long time, since you are always building an "all inclusive" kernel config. I usually trim the config down to what is needed on my machine and use ccache to speed up things a little bit, but I somewhat know what I'm doing there and I'm fully aware that I might not find the same bug the SUSE kernel is exhibiting by changing the configuration. Executive summary: I'm usually searching the bug in the upstream kernel, not in the suse kernel. Good luck. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Bo Simonsen -
Christian Trippe -
Herbert Graeber -
Knurpht - Gertjan Lettink -
Oliver Neukum -
René Krell -
Stefan Seyfried -
Timo Diedering