Linux-Bluetooth Archive on lore.kernel.org
 help / color / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable
Date: Sat, 15 Feb 2020 20:59:09 +0000
Message-ID: <bug-60824-62941-UY3sKyusEz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60824-62941@https.bugzilla.kernel.org/>

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

Alex (alex.kr.job@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alex.kr.job@gmail.com

--- Comment #55 from Alex (alex.kr.job@gmail.com) ---
Hi,
My issue with this device looks a little different, and after applying the
latest patch from the thread I still have the issue.

btmon shows the following (last lines, see Set Event Filter error):

#20 [hci0] 9.289041
      Read Number of Supported IAC (0x03|0x0038) ncmd 1
        Status: Success (0x00)
        Number of IAC: 2
< HCI Command: Read Current IAC LAP (0x03|0x0039) plen 0                       
                                                         #21 [hci0] 9.289050
> HCI Event: Command Complete (0x0e) plen 8                                    
>                                                          #22 [hci0] 9.291043
      Read Current IAC LAP (0x03|0x0039) ncmd 1
        Status: Success (0x00)
        Number of IAC: 1
        Access code: 0x9e8b33 (General Inquiry)
< HCI Command: Set Event Filter (0x03|0x0005) plen 1                           
                                                         #23 [hci0] 9.291049
        Type: Clear All Filters (0x00)
> HCI Event: Command Complete (0x0e) plen 4                                    
>                                                          #24 [hci0] 9.293040
      Set Event Filter (0x03|0x0005) ncmd 1
        Status: Invalid HCI Command Parameters (0x12)
= Close Index: 00:1A:7D:DA:71:12                                               
                                                             [hci0] 9.293052


and the device stays down and inaccessible
Here is data from my system:

hciconfig -a 
hci0:   Type: Primary  Bus: USB
        BD Address: 00:1A:7D:DA:71:12  ACL MTU: 679:8  SCO MTU: 48:16
        DOWN 
        RX bytes:706 acl:0 sco:0 events:22 errors:0
        TX bytes:68 acl:0 sco:0 commands:22 errors:0
        Features: 0xbf 0x2e 0x4d 0xfa 0xd8 0x3d 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV3 
        Link policy: 
        Link mode: SLAVE ACCEPT 

hciconfig  hci0 up
Can't init device hci0: Invalid argument (22)

[bluetooth]# list
[bluetooth]# 

lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 14cd:125c Super Top SD card reader
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 018: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
Bus 001 Device 002: ID 0bda:b812 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg (extract)
[ 5284.357208] usbcore: deregistering interface driver btusb
[ 5287.608129] usb 1-7: new full-speed USB device number 18 using xhci_hcd
[ 5287.758895] usb 1-7: config 1 interface 1 altsetting 0 endpoint 0x3 has
wMaxPacketSize 0, skipping
[ 5287.758904] usb 1-7: config 1 interface 1 altsetting 0 endpoint 0x83 has
wMaxPacketSize 0, skipping
[ 5287.759639] usb 1-7: New USB device found, idVendor=0a12, idProduct=0001,
bcdDevice=88.91
[ 5287.759647] usb 1-7: New USB device strings: Mfr=0, Product=2,
SerialNumber=0
[ 5287.759651] usb 1-7: Product: BT DONGLE10
[ 5287.785780] btusb: New fixups. Device: 0x0a12:0x0001/0x8891. Rule 1/1 (5
terms): 0x0a12:0x0001/0x8891
[ 5287.785781] btusb: driver flags: initial => 0x0000000000000004
[ 5287.785783] btusb: driver flags: masked  => 0x0000000000800000
[ 5287.785902] usbcore: registered new interface driver btusb
[ 5395.553658] debugfs: File 'dut_mode' in directory 'hci0' already present!

hcidump -X is attached
Any suggestions/fixes are really appreciated.
Please let me know if some info is missing.

Thanks,
Alex.

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

  parent reply index

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-60824-62941@https.bugzilla.kernel.org/>
2019-06-24 14:43 ` bugzilla-daemon
2019-06-24 17:12 ` bugzilla-daemon
2019-06-25 16:15 ` bugzilla-daemon
2019-08-01  1:56 ` bugzilla-daemon
2019-08-15  5:54 ` bugzilla-daemon
2019-08-17  4:52 ` bugzilla-daemon
2019-08-17 22:42 ` bugzilla-daemon
2019-08-18  1:45 ` bugzilla-daemon
2019-08-20  4:49 ` bugzilla-daemon
2019-09-11 18:20 ` bugzilla-daemon
2019-09-16  7:30 ` bugzilla-daemon
2019-09-16 11:12 ` bugzilla-daemon
2019-10-13 17:25 ` bugzilla-daemon
2019-10-15 21:00 ` bugzilla-daemon
2019-11-03  9:12 ` bugzilla-daemon
2019-12-06 19:36 ` bugzilla-daemon
2019-12-10  4:54 ` bugzilla-daemon
2020-01-17  6:29 ` bugzilla-daemon
2020-01-17  6:50 ` bugzilla-daemon
2020-01-25 14:52 ` bugzilla-daemon
2020-02-07 15:31 ` bugzilla-daemon
2020-02-07 16:50 ` bugzilla-daemon
2020-02-07 17:00 ` bugzilla-daemon
2020-02-07 17:24 ` bugzilla-daemon
2020-02-13 19:59 ` bugzilla-daemon
2020-02-15 20:59 ` bugzilla-daemon [this message]
2020-02-15 21:01 ` bugzilla-daemon
2020-04-06 19:43 ` bugzilla-daemon
2020-04-23 17:17 ` bugzilla-daemon
2020-04-24 13:14 ` bugzilla-daemon
2020-05-02 21:54 ` bugzilla-daemon
2020-05-03  0:52 ` bugzilla-daemon
2020-05-09  6:15 ` bugzilla-daemon
2020-05-10 14:50 ` bugzilla-daemon
2020-05-10 15:15 ` bugzilla-daemon
2020-05-10 16:14 ` bugzilla-daemon
2020-05-10 18:53 ` bugzilla-daemon
2020-06-21 20:30 ` bugzilla-daemon
2020-06-24  2:44 ` bugzilla-daemon
2020-06-24 14:03 ` bugzilla-daemon
2020-06-24 16:48 ` bugzilla-daemon
2020-06-24 17:23 ` bugzilla-daemon
2020-06-24 18:42 ` bugzilla-daemon
2020-06-24 21:37 ` bugzilla-daemon
2020-06-24 21:44 ` bugzilla-daemon
2020-06-25  0:04 ` bugzilla-daemon
2020-06-25  7:34 ` bugzilla-daemon
2020-06-25 11:16 ` bugzilla-daemon
2020-07-18 19:16 ` bugzilla-daemon
2020-07-18 21:39 ` bugzilla-daemon
2020-07-19  1:50 ` bugzilla-daemon
2020-07-20 21:13 ` bugzilla-daemon
2020-07-24 15:43 ` bugzilla-daemon
2020-07-24 15:46 ` bugzilla-daemon
2020-07-26 21:26 ` bugzilla-daemon
2020-07-27  4:16 ` bugzilla-daemon
2020-07-27  5:53 ` bugzilla-daemon
2020-08-03  8:05 ` bugzilla-daemon
2020-08-03  8:18 ` bugzilla-daemon
2020-08-03  8:27 ` bugzilla-daemon
2020-08-03  8:28 ` bugzilla-daemon
2020-08-03  8:29 ` bugzilla-daemon
2020-08-03  8:47 ` bugzilla-daemon
2020-08-03  9:03 ` bugzilla-daemon
2020-08-03  9:08 ` bugzilla-daemon
2020-08-03  9:08 ` bugzilla-daemon
2020-08-03 14:54 ` bugzilla-daemon
2020-08-10 22:35 ` bugzilla-daemon
2020-08-13 19:32 ` bugzilla-daemon
2020-08-15  0:16 ` bugzilla-daemon
2020-08-18 22:53 ` bugzilla-daemon
2020-08-20  5:43 ` bugzilla-daemon
2020-08-22 14:39 ` bugzilla-daemon
2020-08-23  6:58 ` bugzilla-daemon
2020-08-25 15:17 ` bugzilla-daemon
2020-08-26 17:08 ` bugzilla-daemon
2020-09-01 19:39 ` bugzilla-daemon
2020-09-02  2:28 ` bugzilla-daemon
2020-09-09 14:12 ` bugzilla-daemon
2020-09-12 15:54 ` bugzilla-daemon
2020-09-23 14:06 ` bugzilla-daemon
2020-09-27 12:45 ` bugzilla-daemon
2020-10-16 21:46 ` bugzilla-daemon
2020-10-29  0:26 ` bugzilla-daemon
2020-11-10 14:06 ` bugzilla-daemon
2020-11-18  2:21 ` bugzilla-daemon
2020-11-26 20:03 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-60824-62941-UY3sKyusEz@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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
	public-inbox-index linux-bluetooth

Example config snippet for mirrors

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.git