Linux-Bluetooth Archive on lore.kernel.org
 help / Atom feed
* [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
       [not found] <bug-86931-62941@https.bugzilla.kernel.org/>
@ 2016-03-30 17:53 ` bugzilla-daemon
  2018-01-12  9:21 ` bugzilla-daemon
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 4+ messages in thread
From: bugzilla-daemon @ 2016-03-30 17:53 UTC (permalink / raw)
  To: linux-bluetooth

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

jbMacAZ <jbmacbrodie@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jbmacbrodie@yahoo.com

--- Comment #3 from jbMacAZ <jbmacbrodie@yahoo.com> ---
Bluetooth behavior was good in ubuntu 15.10 - bluez5.35, blueman device manager
and kernel 4.3.6.  I use a bt mouse and OEM bt keydock (Asus T100-CHI)

Starting with 4.4 thru 4.6-rc1-next*, I have to open blueman's device manager
to search for devices after idle timeouts.  I also need to leave the device
manager dialogue open/minimized to prevent rapid loss of connection.  Device
pairing is remembered, but manually searching is difficult when the pointing
devices stop working.  My test setup has a usb mouse as a workaround.

dmesg has "unknown main item tag 0x0" after each idle timeout".  If I move
mouse during boot, it will auto-connect, but it then suffers a rapid timeout
soon after booting.  See dmesg posted at #114561.  It looks like something is
incrementing the bluetooth input assignment # when anything times out.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
       [not found] <bug-86931-62941@https.bugzilla.kernel.org/>
  2016-03-30 17:53 ` [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 bugzilla-daemon
@ 2018-01-12  9:21 ` bugzilla-daemon
  2018-01-12 17:26 ` bugzilla-daemon
  2019-01-30 18:27 ` bugzilla-daemon
  3 siblings, 0 replies; 4+ messages in thread
From: bugzilla-daemon @ 2018-01-12  9:21 UTC (permalink / raw)
  To: linux-bluetooth

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

robsmith11@yandex.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |robsmith11@yandex.com

--- Comment #4 from robsmith11@yandex.com ---
Has anyone solved this yet??

I have the same issue with a bluetooth keyboard and kernel 4.14.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
       [not found] <bug-86931-62941@https.bugzilla.kernel.org/>
  2016-03-30 17:53 ` [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 bugzilla-daemon
  2018-01-12  9:21 ` bugzilla-daemon
@ 2018-01-12 17:26 ` bugzilla-daemon
  2019-01-30 18:27 ` bugzilla-daemon
  3 siblings, 0 replies; 4+ messages in thread
From: bugzilla-daemon @ 2018-01-12 17:26 UTC (permalink / raw)
  To: linux-bluetooth

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

--- Comment #5 from jbMacAZ (jbmacbrodie@yahoo.com) ---
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. 

You could try adding the quirk for your device.  

(No kernel maintainer has acknowledged this bug report.)

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
       [not found] <bug-86931-62941@https.bugzilla.kernel.org/>
                   ` (2 preceding siblings ...)
  2018-01-12 17:26 ` bugzilla-daemon
@ 2019-01-30 18:27 ` bugzilla-daemon
  3 siblings, 0 replies; 4+ messages in thread
From: bugzilla-daemon @ 2019-01-30 18:27 UTC (permalink / raw)
  To: linux-bluetooth

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

--- Comment #6 from mybigspam@mail.ru ---
It's not clear from the description what is the problem exactly?
I have similar symptoms with "unknown main item tag 0x0" message after timeout.

But my problem is that bluetooth keyboard disconnects on timeout (which is
normal), but then, on the first key press it's just loss, while the keyboard
reconnects successfully.

It doesn't occurs on the same system with Windows 10 - the key doesn't lost on
reconnect.

I wonder if it can be the same problem.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-86931-62941@https.bugzilla.kernel.org/>
2016-03-30 17:53 ` [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 bugzilla-daemon
2018-01-12  9:21 ` bugzilla-daemon
2018-01-12 17:26 ` bugzilla-daemon
2019-01-30 18:27 ` bugzilla-daemon

Linux-Bluetooth Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \
		linux-bluetooth@vger.kernel.org linux-bluetooth@archiver.kernel.org
	public-inbox-index linux-bluetooth


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-bluetooth


AGPL code for this site: git clone https://public-inbox.org/ public-inbox