Date: Fri, 30 Aug 2019 21:08:39 +0200 From: Miranda Maria Sophie Van den Breukelingen <mms.vanbreukelingen@gmail.com> To: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> Cc: Warner Losh <imp@bsdimp.com>, Konstantin Belousov <kostikbel@gmail.com>, Hans Petter Selasky <hps@selasky.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: Kernel-Crash when working with ubt0 Message-ID: <CAM94aeoXEdi_x3_%2BKSFRdTAbaxwuOQVkh=dyBt3=HHyQdDAZ0A@mail.gmail.com> In-Reply-To: <CAFPOs6qt7-L97wy1YQWUmoCzXAvetxmrKPK4guEmLvjm-Ov67A@mail.gmail.com> References: <1115053193.64543.1567031661382.ref@mail.yahoo.com> <1115053193.64543.1567031661382@mail.yahoo.com> <CANCZdfr%2B21-L8C61ThW2CQi8bjVGcvBPxxDCNoXyZXN0Bv44pA@mail.gmail.com> <CAFPOs6r140WzpSM_fEhCdhQ7OGMHq1xhkacWzv6EDVZph097UQ@mail.gmail.com> <CANCZdfph%2BckxQ6f%2BJAN=vYVkXa4%2BUGbsFzEf7RHvdAx=wNCX5A@mail.gmail.com> <CAFPOs6qt7-L97wy1YQWUmoCzXAvetxmrKPK4guEmLvjm-Ov67A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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_listl2control: Could not bind socket, bdaddr=c0:7a:a5:00:c7:11: Network is down* l2ping is ok; tried with different BT-headsets and "buttons", did *'patch -C < ng_btsocket.diff.txt'* in /usr/src/head; success with the chunks 1-19, removing a previous patch and looked satisfied after gitt --diff - 'ing it. Interferences are a big problem with that kinda technology as on 2.4Ghz like the "old" WLAN wave has been - and where I live it is still the same - even when we're getting IPv6 the download speed won't relatively be faster - it always took half an hour to download an .iSO at a distribution server and without VPN it is fast and effordable for about 10MB/s with .torrents - 5G we are coming, I think, the VR is gonna need lots and lots of data-transfers around the globe. So, what to do with the "network down" - problem? The 'bluetooth-config scan' command is practical but is just pairing, not connecting. Any ideas? MvB On Fri, 30 Aug 2019 at 18:41, Maksim Yevmenkin <maksim.yevmenkin@gmail.com> wrote: > >> > patch -p1 worked for me to apply it. > >> > > >> > And it worked just fine for everything once I rebooted. The patch > looked fine to my eye. > >> > >> thanks Warner > >> > >> please find attached (more complete) patch that should address issue > >> of holding lock over copyin/out (or so i claim). > > > > Seems to be working fine now... > > committed. thanks! > > max >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM94aeoXEdi_x3_%2BKSFRdTAbaxwuOQVkh=dyBt3=HHyQdDAZ0A>