USB devices (trackball and PS2-to-usb keyboard) stop responding in Ubuntu Mate 16.04.4

Kleber Souza kleber.souza at canonical.com
Fri May 11 15:29:17 UTC 2018


On 05/10/18 20:15, Kyprianos Papadimitriou wrote:
> Hello again, see below please what the output of "dmesg" command is when
> the trackball works.
> 

Hello Kyprianos,

The main purpose of this mailing-list is to have discussions about
Ubuntu kernel updates, submit patches for known bugs, etc. Before a
patch to fix a issue is found, the best place to discuss about the issue
and report new information that can help is on the Launchpad bug. People
who are responsible for bug triage will respond and try to solve the
problem as soon as they can.


Thank you,
Kleber

> 
> On 10/05/2018 07:17 μμ, Kyprianos Papadimitriou wrote:
>>
>>
>>
>> On 07/05/2018 12:31 πμ, Kyprianos Papadimitriou wrote:
>>>
>>> Hi again, below is a relevant thread
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575872
>>>
>>> Regards,
>>>
>>> On 06/05/2018 01:51 πμ, Kyprianos Papadimitriou wrote:
>>>> Hello,
>>>>
>>>> See below please
>>>>
>>>>
>>>> On 02/05/2018 06:44 πμ, Kai Heng Feng wrote:
>>>>> Hi,
>>>>>
>>>>>> On Apr 29, 2018, at 8:20 PM, Kyprianos Papadimitriou
>>>>>> <kpapadim at mhl.tuc.gr> wrote:
>>>>>>
>>>>>> see below
>>>>>>
>>>>>>
>>>>>> On 26/04/2018 08:18 μμ, Kai-Heng Feng wrote:
>>>>>>> Hi Kyprianos,
>>>>>>>
>>>>>>> at 21:22, Kyprianos Papadimitriou <kpapadim at mhl.tuc.gr> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> The following might be a problem related to unsupported devices
>>>>>>>> by the Kernel.
>>>>>>>> I am facing the problem described in the thread:
>>>>>>>> https://ubuntuforums.org/showthread.php?t=2342985
>>>>>>>
>>>>>>> If this is what you are facing, the HID quirk won't do anything.
>>>>>>> The USB host controller failed to work in this case.
>>>>>>>
>>>>>>>> And my problem is that I don't know how to do the : quirk
>>>>>>>> HID_QUIRK_ALWAYS_POLL (0x00000400), which is mentioned in the
>>>>>>>> above link.
>>>>>>>
>>>>>>> Please file a bug at https://launchpad.net.
>>>>>>>
>>>>>>> Kai-Heng
>>>>>>
>>>>>> I should first create an account, then file the bug?
>>>>>
>>>>> Yes, that will be great.
>>>>>
>>>>> Kai-Heng
>>>>>
>>>>
>>>> I 've just reported it as bug at https://launchpad.net, it got the
>>>> ID#1769403, with subject : "USB devices (trackball and PS2-to-usb
>>>> keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude"
>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Kyprianos
>>>>>>
>>>>>>>> lsusb command for the 2 devices gives:
>>>>>>>>
>>>>>>>> Bus 002 Device 009: ID 046d:c404 Logitech, Inc. TrackMan Wheel
>>>>>>>>
>>>>>>>> Bus 002 Device 010: ID 0a81:0205 Chesen Electronics Corp. PS/2
>>>>>>>> Keyboard+Mouse Adapter
>>>>>>>>
>>>>>>>> tlp-stat -u command for the 2 devices gives:
>>>>>>>>
>>>>>>>> Bus 002 Device 009 ID 046d:c404 control = on,
>>>>>>>> autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel
>>>>>>>> (usbhid)
>>>>>>>>
>>>>>>>> Bus 002 Device 010 ID 0a81:0205 control = on,
>>>>>>>> autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2
>>>>>>>> Keyboard+Mouse Adapter (usbhid)
>>>>>>>>
>>>>>>>> uname -ra gives:
>>>>>>>>
>>>>>>>> Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5
>>>>>>>> 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>>>>>>>>
>>>>>>>> I think the problem is not related with autosuspend, but rather
>>>>>>>> with buffer overflow for the specific devices due to that they
>>>>>>>> are not supported in the kernel code.
>>>>>>>>
>>>>>>>> Best Regards,
>>>>>>>> Kyprianos
>>>>>>>>
>>>>>>>> -- 
>>>>>>>> kernel-team mailing list
>>>>>>>> kernel-team at lists.ubuntu.com
>>>>>>>> https://lists.ubuntu.com/mailman/listinfo/kernel-team
>>>>>>>
>>>>>>>
>>>>>>> . 
>>
>> IMHO this is interesting and it can help. Unfortunately it is not an
>> answer; it rather points to start looking to a different direction,
>> i.e. BIOS. Even though the USB trackball is detected within Ubuntu
>> Mate when executing the |lsusb| command, the trackball misbehaves
>> probably due to an issue with BIOS. Please check the output of the
>> following command, especially the lines at the end.
>>
>> (note: info related to Logitech trackball is on
>> /sys/bus/usb/devices/2-1.2 path)
>>
>> |$ dmesg | grep 2-1.2|
>>
>> |[    1.900039] usb 2-1.2: new low-speed USB device number 4 using
>> ehci-pci
>> [    2.020547] usb 2-1.2: New USB device found, idVendor=046d,
>> idProduct=c404
>> [    2.020554] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [    2.020559] usb 2-1.2: Product: Trackball
>> [    2.020564] usb 2-1.2: Manufacturer: Logitech
>> [    2.033380] input: Logitech Trackball as
>> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:046D:C404.0001/input/input8
>> [    3.488019] usb 2-1.2: reset low-speed USB device number 4 using
>> ehci-pci
>> [    3.789745] usb 2-1.2: device firmware changed
>> [    3.790112] usb 2-1.2: USB disconnect, device number 4
>> [    3.924089] usb 2-1.2: new low-speed USB device number 6 using ehci-pci
>> [    4.040117] usb 2-1.2: New USB device found, idVendor=046d,
>> idProduct=c404
>> [    4.040124] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [    4.040129] usb 2-1.2: Product: Trackball
>> [    4.040133] usb 2-1.2: Manufacturer: Logitech
>> [    4.044948] input: Logitech Trackball as
>> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:046D:C404.0002/input/input10
>> [    5.800078] usb 2-1.2: reset low-speed USB device number 6 using
>> ehci-pci
>> [    7.844136] usb 2-1.2: reset low-speed USB device number 6 using
>> ehci-pci
>> [    8.145979] usb 2-1.2: device firmware changed
>> [    8.146222] usb 2-1.2: USB disconnect, device number 6
>> [    8.264032] usb 2-1.2: new low-speed USB device number 7 using ehci-pci
>> [    8.381466] usb 2-1.2: New USB device found, idVendor=046d,
>> idProduct=c404
>> [    8.381473] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [    8.381478] usb 2-1.2: Product: Trackball
>> [    8.381483] usb 2-1.2: Manufacturer: Logitech
>> [    8.388461] usbhid 2-1.2:1.0: can't add hid device: -32
>> [    8.388469] usbhid: probe of 2-1.2:1.0 failed with error -32
>> |
>>
>>
>>
> 
> 
> for some reason the Trackball is alive - for at least 30' so far - so, I
> executed the command `dmesg | grep 2-1.2` again to check what it gives
> on the output when the trackball functions properly:
> 
>> [    1.896048] usb 2-1.2: new low-speed USB device number 4 using ehci-pci
>> [    2.010037] usb 2-1.2: New USB device found, idVendor=046d,
> idProduct=c404
>> [    2.010039] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
>> [    2.010040] usb 2-1.2: Product: Trackball
>> [    2.010042] usb 2-1.2: Manufacturer: Logitech
>> [    2.021341] input: Logitech Trackball as
> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:046D:C404.0001/input/input8
> 
> 
> 
> 




More information about the kernel-team mailing list