[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
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
From this context, is it possible I'm infected by this sickness? Any expert?
2016-02-24 14:09 GMT+01:00 René Krell
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
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
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
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
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
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
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
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
: 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
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 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
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
: 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