[Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=209137

--- Comment #5 from Philipp (philipp.shah@gmx.de) ---
If I connect a wired mouse the mouse is working, so USB is not the problem.
The new kernel just does not accept the logitech wireless mouse and keyboard
(K520 and M310) but the old does. Hopefully the bug can be fixed soon.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=209137

--- Comment #6 from Alan Stern (stern@rowland.harvard.edu) ---
You should be more careful about what you write.  In the original bug
description you said that USB isn't working, but in comment #5 you said that
USB isn't the problem.  Try to be more consistent.

Your dmesg log from the 5.4 kernel does show some errors from the HID driver. 
You should collect a similar dmesg log under a 5.0 kernel for comparison.

Another thing that would help is the output from running as superuser "lsusb
-v" for the Logitech receiver.  Under either 5.0 or 5.4, the output should be
the same.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=209137

--- Comment #7 from Philipp (philipp.shah@gmx.de) ---
I didn't had a wired mouse as I wrote report the bug first (see date and
conversation). Therefor as time went on knowledge changes. On 28th of Sept I
connected a wired mouse the first time, because I didn't had a wired mouse
before. Thus there is no problem with consistency. I'm happy of any help that I
can get with this problem but I'm not a child which should be monished and you
should be a bit more careful with your conclusions about "consistency".

..I will do dmesg log soon. Thx!

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=209137

--- Comment #8 from Philipp (philipp.shah@gmx.de) ---
Created attachment 292879
  --> https://bugzilla.kernel.org/attachment.cgi?id=292879&action=edit
'dmesg' for 5.0 for comparison

I just uploeded 'dmesg' for 5.0.
'dmesg' for 5.0 doesn't not show the HID driver error as 5.4 did.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=209137

--- Comment #9 from Alan Stern (stern@rowland.harvard.edu) ---
As mentioned in comment #6, can you also provide the output from "lsusb -v"
(run as root) for the Logitech receiver?  It should be the same for 5.0 and
5.4, so only one of them is needed.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=209137

--- Comment #10 from Philipp (philipp.shah@gmx.de) ---
Created attachment 292897
  --> https://bugzilla.kernel.org/attachment.cgi?id=292897&action=edit
lsusb -v

Oh, sorry for that. Just forgot it. Here is the 'lsusb -v'.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

Re: [Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[Alan Stern]

Jiri and Benjamin:

Please look at Bugzilla # 209137:

	https://bugzilla.kernel.org/show_bug.cgi?id=209137

Somewhere between 5.0 and 5.4, the logitech-djreceiver driver stopped 
binding to the user's Logitech wireless device.  Here are relevant parts 
of the kernel logs.  From 5.0 (working):

[    2.857770] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4/input2
[    2.985339] input: Logitech Unifying Device. Wireless PID:1024 Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0003/0003:046D:1024.0004/input/input13
[    2.985410] hid-generic 0003:046D:1024.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1024] on usb-0000:00:14.0-4:1
[    2.995266] input: Logitech K520 as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0003/0003:046D:2011.0005/input/input17
[    3.026985] logitech-hidpp-device 0003:046D:2011.0005: input,hidraw1: USB HID v1.11 Keyboard [Logitech K520] on usb-0000:00:14.0-4:2
[    3.033173] input: Logitech M310 as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0003/0003:046D:1024.0004/input/input18
[    3.033358] logitech-hidpp-device 0003:046D:1024.0004: input,hidraw2: USB HID v1.11 Mouse [Logitech M310] on usb-0000:00:14.0-4:1

From 5.4 (non-working):

[    2.908901] hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-4/input0
[    2.909003] hid-generic 0003:046D:C52B.0002: unknown main item tag 0x0
[    2.909016] hid-generic 0003:046D:C52B.0002: unknown main item tag 0x0
[    2.909019] hid-generic 0003:046D:C52B.0002: unknown main item tag 0x0
[    2.909023] hid-generic 0003:046D:C52B.0002: unknown main item tag 0x0
[    2.909030] hid-generic 0003:046D:C52B.0002: unexpected long global item
[    2.909038] hid-generic: probe of 0003:046D:C52B.0002 failed with error -22
[    2.909196] hid-generic 0003:046D:C52B.0003: hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4/input2
[    2.910586] logitech-djreceiver 0003:046D:C52B.0002: unknown main item tag 0x0
[    2.910601] logitech-djreceiver 0003:046D:C52B.0002: unknown main item tag 0x0
[    2.910605] logitech-djreceiver 0003:046D:C52B.0002: unknown main item tag 0x0
[    2.910609] logitech-djreceiver 0003:046D:C52B.0002: unknown main item tag 0x0
[    2.910616] logitech-djreceiver 0003:046D:C52B.0002: unexpected long global item
[    2.910620] logitech-djreceiver 0003:046D:C52B.0002: logi_dj_probe: parse failed
[    2.910623] logitech-djreceiver: probe of 0003:046D:C52B.0002 failed with error -22

FYI, intf 0 is a boot-interface keyboard, intf 1 is a boot-interface 
mouse, and intf 2 is the wireless HID interface.

It's not immediately obvious to me where the problem lies.

Thanks,

Alan Stern

[Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=209137

--- Comment #11 from Alan Stern (stern@rowland.harvard.edu) ---
Did you run lsusb as root?  I ask because the report descriptors are missing
from the output, and this is typically what happens when lsusb is run as a
normal user, not root.

Also, the dmesg logs indicate that you weren't running the -stable kernel
versions.  It's possible that this problem has already been fixed in those
versions.  For the same reason, you might try running a 5.8 kernel.

If none of those work, you can always try running git-bisect to find the
particular commit which caused the problem to appear somewhere between 5.0 and
5.4.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=209137

--- Comment #12 from Philipp (philipp.shah@gmx.de) ---
Yes. I run lsusb as root. I run ´sudo lsusb -v > lsusb.txt´ and uploaded
lsusb.txt

I`m using Ubuntu and kernel 5.8 was not indicated via automatical update. Never
installed an other kernel by myself especially because my pc is my working pc
and therefor I`m usually not doing experiments. Just tested other live CDs like
the newest fedora or the latest debian, to see, if there is the same problem.

I ordered a wired keyboard and will bypass this bug.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

Re: [Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[Benjamin Tissoires]

Hi Alan,

On Thu, Oct 8, 2020 at 4:42 PM Alan Stern <stern@rowland.harvard.edu> wrote:
>
> Jiri and Benjamin:
>
> Please look at Bugzilla # 209137:
>
>         https://bugzilla.kernel.org/show_bug.cgi?id=209137
>
> Somewhere between 5.0 and 5.4, the logitech-djreceiver driver stopped
> binding to the user's Logitech wireless device.  Here are relevant parts
> of the kernel logs.  From 5.0 (working):
>
> [    2.857770] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4/input2
> [    2.985339] input: Logitech Unifying Device. Wireless PID:1024 Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0003/0003:046D:1024.0004/input/input13
> [    2.985410] hid-generic 0003:046D:1024.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1024] on usb-0000:00:14.0-4:1
> [    2.995266] input: Logitech K520 as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0003/0003:046D:2011.0005/input/input17
> [    3.026985] logitech-hidpp-device 0003:046D:2011.0005: input,hidraw1: USB HID v1.11 Keyboard [Logitech K520] on usb-0000:00:14.0-4:2
> [    3.033173] input: Logitech M310 as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0003/0003:046D:1024.0004/input/input18
> [    3.033358] logitech-hidpp-device 0003:046D:1024.0004: input,hidraw2: USB HID v1.11 Mouse [Logitech M310] on usb-0000:00:14.0-4:1
>
> From 5.4 (non-working):
>
> [    2.908901] hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-4/input0
> [    2.909003] hid-generic 0003:046D:C52B.0002: unknown main item tag 0x0
> [    2.909016] hid-generic 0003:046D:C52B.0002: unknown main item tag 0x0
> [    2.909019] hid-generic 0003:046D:C52B.0002: unknown main item tag 0x0
> [    2.909023] hid-generic 0003:046D:C52B.0002: unknown main item tag 0x0
> [    2.909030] hid-generic 0003:046D:C52B.0002: unexpected long global item
> [    2.909038] hid-generic: probe of 0003:046D:C52B.0002 failed with error -22
> [    2.909196] hid-generic 0003:046D:C52B.0003: hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4/input2
> [    2.910586] logitech-djreceiver 0003:046D:C52B.0002: unknown main item tag 0x0
> [    2.910601] logitech-djreceiver 0003:046D:C52B.0002: unknown main item tag 0x0
> [    2.910605] logitech-djreceiver 0003:046D:C52B.0002: unknown main item tag 0x0
> [    2.910609] logitech-djreceiver 0003:046D:C52B.0002: unknown main item tag 0x0
> [    2.910616] logitech-djreceiver 0003:046D:C52B.0002: unexpected long global item
> [    2.910620] logitech-djreceiver 0003:046D:C52B.0002: logi_dj_probe: parse failed
> [    2.910623] logitech-djreceiver: probe of 0003:046D:C52B.0002 failed with error -22
>
> FYI, intf 0 is a boot-interface keyboard, intf 1 is a boot-interface
> mouse, and intf 2 is the wireless HID interface.

That is weird. I also have (several) C52B devices here, and I don't
see the problem (though arguably there are several firmware versions
out in the open).

The first part of failures show that even hid-generic can not parse
the report descriptor. This means that the provided report descriptor
is incorrect, which is weird because the one I just tested works fine.
The second part (with logitech-dj) is showing the same errors, so
that's expected given the previous problem.

To actually get the report descriptors, `lsub -v` works fine if the
HID subsystem is not bounded. So there we need to ask the reporter to
run the command with the HID subsystem not handling the device, or
simply in the working case use hid-recorder from
https://gitlab.freedesktop.org/libevdev/hid-tools/.

Another solution if the report descriptor is identical to what I have
here (in the working case), would be to write a BPF kprobe to dump
what hid_parse sees. It should be straightforward to write one, I got
everything in place for i2c-hid at
https://gitlab.freedesktop.org/bentiss/hid-bpf (though for using the
CO-RE BPF program, I am not sure 5.4 is recent enough).

>
> It's not immediately obvious to me where the problem lies.

Not obvious to me either...

Cheers,
Benjamin

>
> Thanks,
>
> Alan Stern
>

[Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=209137

Benjamin Tissoires (benjamin.tissoires@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |benjamin.tissoires@gmail.co
                   |                            |m

--- Comment #13 from Benjamin Tissoires (benjamin.tissoires@gmail.com) ---
Created attachment 292905
  --> https://bugzilla.kernel.org/attachment.cgi?id=292905&action=edit
report descriptor of a working C52B receiver

Regarding the `lsub -v` not working, could you:
- boot on the working kernel
- use hid-recorder (as root) from
https://gitlab.freedesktop.org/libevdev/hid-tools/ to record all the "Logitech
USB Receiver" that shows up in the list

For a point of comparison, I attached the report descriptors of the working
C52B I have here (only the wireless interface).

If there is no differences between your dumps and mine, then there is something
wrong happening in the usbhid driver or lower, and we will need more logs at
that point.

FTR, this Logitech receiver I have here works fine with 5.8.4 on Fedora 32...

-- 
You are receiving this mail because:
You are watching the assignee of the bug.