-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Labels
area: Bluetootharea: Bluetooth HostBluetooth Host (excluding BR/EDR)Bluetooth Host (excluding BR/EDR)bugThe issue is a bug, or the PR is fixing a bugThe issue is a bug, or the PR is fixing a bugpriority: mediumMedium impact/importance bugMedium impact/importance bug
Description
Zephyr build version: zephyr-v2.4.0-1367-g7d16ab50d738
Step to build and configuration:
-
- west build -b native_posix zephyr/samples/bluetooth/central
-
- west build -t menuconfig
- Goto --> Sub Systems and OS Services --> Blueooth-->Bluetooth HCI driver debug
- Goto --> Sub Systems and OS Services --> Blueooth-->Bluetooth debug type (Normal printf-style to console)
- Goto --> Sub Systems and OS Services --> Blueooth-->Bluetooth HCI core debug
-
- west build
Use Cambridge Silicon Radio CSR rck PTS Dongle as Controller
-
- sudo btmon
-
- sudo hciconfig hci1 down
Finally run command: sudo ./build/zephyr/zephyr.exe --bt-dev=hci1
In a short time, an exception will be triggered, see below:
ASSERTION FAIL [err == 0] @ /home/lingao/zephyrproject/zephyr/subsys/bluetooth/host/hci_core.c:374
k_sem_take failed with err -11
@ /home/lingao/zephyrproject/zephyr/subsys/bluetooth/host/hci_core.c:374
[00:00:10.910,000] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
[00:00:10.910,000] <err> os: Current thread: 0x56614fa0 (unknown)
[00:00:10.910,000] <err> os: Halting system
Metadata
Metadata
Assignees
Labels
area: Bluetootharea: Bluetooth HostBluetooth Host (excluding BR/EDR)Bluetooth Host (excluding BR/EDR)bugThe issue is a bug, or the PR is fixing a bugThe issue is a bug, or the PR is fixing a bugpriority: mediumMedium impact/importance bugMedium impact/importance bug