Kernel-Crash when working with ubt0

[Maksim Yevmenkin]

[trimming the list of recipients]

On Fri, Aug 30, 2019 at 12:08 PM Miranda Maria Sophie Van den
Breukelingen <mms.vanbreukelingen at gmail.com> wrote:
>
> works for me as far as pairing concernes (with patch -C > .diff.txt
>
> option         LOCK_PROFILING
> option         WITNESS
>
> is on in kern.config. My problem presists in the following form:
>
> l2control -a c0:7a:a5:00:c7:11 read_channel_list
> l2control: Could not bind socket, bdaddr=c0:7a:a5:00:c7:11: Network is down

can you please tell what 'c0:7a:a5:00:c7:11' is? is this a remove address?

looking at your previous emails, i *think*, 'c0:7a:a5:00:c7:11' is a
remote address. if this is the case, then, l2control is not going to
work. from the l2control(8) man page

==
     -a local
             Connect to the local device with the specified BD_ADDR or name.
             Example: -a 00:01:02:03:04:05 or -a bt_device.
==

 more specifically, the read_channel_list command will list l2cap
channels open on the local device.

i'm not exactly sure what are you trying to do here.

> l2ping is ok;

ok. this tells me that hci and l2cap communication works

> So, what to do with the "network down" - problem?

you have asked l2control to bind to the *local* bd_addr
(c0:7a:a5:00:c7:11). and since there is no *local* bluetooth device
with this bd_addr, l2control returns "network down". l2control will
only work for *local* bd_addr's

thanks
max