[Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 - bugzilla-daemon

From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
Date: Sun, 18 Jul 2021 10:47:54 +0000	[thread overview]
Message-ID: <bug-86931-62941-s5LKjCDiQJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-86931-62941@https.bugzilla.kernel.org/>

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

Roman Evstifeev (someuniquename@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |someuniquename@gmail.com

--- Comment #9 from Roman Evstifeev (someuniquename@gmail.com) ---
The bug is still here in 5.12.13 with asaus m-rbb93 logitech b370 mouse. After
some time (unpredictable, can be few hours or few minutes) mouse pointer stops
responding, though mouse appears conneceted in the bluetoothctl.

> bluetoothctl 
Agent registered
[Bluetooth Travel Mouse]# info
Device 00:07:61:68:D2:9E (public)
        Name: Bluetooth Travel Mouse
        Alias: Bluetooth Travel Mouse
        Class: 0x00002580
        Icon: input-mouse
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        WakeAllowed: yes
        LegacyPairing: no
        UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v046DpB002d4809

journalctl and dmesg is silent when the mouse stops responding. Is there any
other way to debug this?

When mouse is first connected, dmesg has the message mentioned as the topic of
this bug:
[185307.429898] hid-generic 0005:046D:B002.002C: input,hidraw1: BLUETOOTH HID
v48.09 Mouse [Bluetooth Travel Mouse] on dc:e9:94:7e:5f:86
[187430.340610] hid-generic 0005:046D:B002.002D: unknown main item tag 0x0
[187430.340668] input: Bluetooth Travel Mouse as
/devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-3/3-3:1.0/bluetooth/hci0/hci0:1/0005:046D:B002.002D/input/input104

 (In reply to jbMacAZ from comment #5)
> The issue was fixed for the Asus T100 (baytrail) 2-in-1 family.  See this
> commit.
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/
> commit/?id=c4c285da1ee18582ace366f07e56e355c20ebc49 which is in kernel 4.15. 

Is there a way to enable this system-wide without patching a kernel, for a
quick test?

I tried to add btusb.enable_autosuspend=n kernel paremeter:

# cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-5.12.13-1-default
root=UUID=ece1a448-6944-4f34-a61c-1742fde2ac3c splash=silent psi=1
nvidia-drm.modeset=1 btusb.enable_autosuspend=n quiet mitigations=auto

# systool -v -m btusb            
Module = "btusb"

  Attributes:
    coresize            = "69632"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "0"
    srcversion          = "8EADE2557C147180496F74C"
    taint               = ""
    uevent              = <store method only>
    version             = "0.8"

  Parameters:
    disable_scofix      = "N"
    enable_autosuspend  = "N"
    force_scofix        = "N"
    reset               = "Y"

But this does not resolve the bug

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.