-current digest..."
Today's Topics:
1. Re: Kernel-Crash when working with ubt0, (Lizbeth Mutterhunt,
Ph.D.) (Miranda van den Breukelingen)
I'm having 353388 and it isn't for me, even with patches not, trying
DragonFlyBSD on the other machine - daily .iso hung up when se
M> >freebsd-current-requ...@freebsd.org
M> >
M> > You can reach the person managing the list at
M> >freebsd-current-ow...@freebsd.org
M> >
M> > When replying, please edit your Subject line so it is more specific
M> > than "Re: Contents of freebsd-cur
nt-ow...@freebsd.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of freebsd-current digest..."
>
> Today's Topics:
>
>1. Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one
> DP found (
On Friday, 30 August 2019 21:50:28 CEST Maksim Yevmenkin wrote:
> [trimming the list of recipients]
>
good like this, so many mails gonna unsubscribe the list - many problems and
bugs as far as eye reaches...
> On Fri, Aug 30, 2019 at 12:08 PM Miranda Maria Sophie Van den
>
> Breukelingen wrot
On Monday, 26 August 2019 23:35:25 CEST maksim yevmenkin wrote:
> > On Aug 26, 2019, at 9:14 AM, Warner Losh wrote:
> >
> > Is it from read_connection_list? If so I have a 'patch' that I'm using but
> > haven't committed because it's just too gross: drop the lock before the
> > copyout and pick i
On Monday, 26 August 2019 09:21:53 CEST Hans Petter Selasky wrote:
> Do you have a backtrace?
>
> --HPS
Yup! Have a look at this sniplet:
https://pastebin.com/bkNkThAd
MvB
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailma
[trimming the list of recipients]
On Fri, Aug 30, 2019 at 12:08 PM Miranda Maria Sophie Van den
Breukelingen 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 t
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:
>> > 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).
>
> S
On Thu, Aug 29, 2019 at 2:56 PM Maksim Yevmenkin
wrote:
> On Wed, Aug 28, 2019 at 6:48 PM Warner Losh 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 (mor
On Wed, Aug 28, 2019 at 6:48 PM Warner Losh 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
On Thu, 29 Aug 2019 at 6:04, Warner Losh
wrote:
On Wed, Aug 28, 2019, 8:57 PM Miranda Maria Sophie Van den Breukelingen
wrote:
On Thu, 29 Aug 2019 at 03:48, Warner Losh wrote:
On Wed, Aug 28, 2019, 4:34 PM mms.vanbreukelin...@gmail.com
wrote:
@Maksim, I first did a "git apply -R b
On Wed, Aug 28, 2019, 8:57 PM Miranda Maria Sophie Van den Breukelingen <
mms.vanbreukelin...@gmail.com> wrote:
>
>
> On Thu, 29 Aug 2019 at 03:48, Warner Losh wrote:
>
>>
>>
>> On Wed, Aug 28, 2019, 4:34 PM mms.vanbreukelin...@gmail.com <
>> mms.vanbreukelin...@gmail.com> wrote:
>>
>>> @Maksim,
On Thu, 29 Aug 2019 at 03:48, Warner Losh wrote:
>
>
> On Wed, Aug 28, 2019, 4:34 PM mms.vanbreukelin...@gmail.com <
> mms.vanbreukelin...@gmail.com> wrote:
>
>> @Maksim, I first did a "git apply -R bt.diff" and then
>>
>> root@freeBSD13:/usr/src # git apply --stat --check --ignore-whitespace
>>
On Wed, Aug 28, 2019, 4:34 PM mms.vanbreukelin...@gmail.com <
mms.vanbreukelin...@gmail.com> wrote:
> @Maksim, I first did a "git apply -R bt.diff" and then
>
> root@freeBSD13:/usr/src # git apply --stat --check --ignore-whitespace
> ng_btsocket_hci_raw.c.diff.txt
> error: patch failed:
> head/sys
@Maksim, I first did a "git apply -R bt.diff" and then
root@freeBSD13:/usr/src # git apply --stat --check --ignore-whitespace
ng_btsocket_hci_raw.c.diff.txt
error: patch failed:
head/sys/netgraph/bluetooth/socket/ng_btsocket_hci_raw.c:1156
error: head/sys/netgraph/bluetooth/socket/ng_btsocket_hci
> > > Hmm... interesting
> > >
> > > I only took a brief look at it. I suppose I can ensure user space address
> > > is wired and then copyout() can be called with mutex held
> >
> > >No, you cannot do this, at least without making the kernel to panic.
> > User might unmap the wired mapping at
I recompiled the kernel with the patch enabled and now we get at 'service
bluetooth start ubt0 (ubt1...)' :
*/etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device
ubt0root@freeBSD13:/usr/home/miranda # service bluetooth start
ubt1/etc/rc.d/bluetooth: ERROR: Unable to setup Bluet
On Tue, Aug 27, 2019 at 06:03:46AM -0700, Maksim Yevmenkin wrote:
> > > Hmm... interesting
> > >
> > > I only took a brief look at it. I suppose I can ensure user space address
> > > is wired and then copyout() can be called with mutex held
> >
> > >No, you cannot do this, at least without mak
> > Hmm... interesting
> >
> > I only took a brief look at it. I suppose I can ensure user space address
> > is wired and then copyout() can be called with mutex held
>
> >No, you cannot do this, at least without making the kernel to panic.
> User might unmap the wired mapping at any time stil
On Tue, 27 Aug 2019 at 9:11, Konstantin Belousov wrote:
On Mon, Aug 26, 2019 at 02:35:25PM -0700, maksim yevmenkin wrote:
>
>
> > On Aug 26, 2019, at 9:14 AM, Warner Losh wrote:
> >
> > Is it from read_connection_list? If so I have a 'patch' that I'm using but
> > haven't committed bec
On Mon, Aug 26, 2019 at 02:35:25PM -0700, maksim yevmenkin wrote:
>
>
> > On Aug 26, 2019, at 9:14 AM, Warner Losh wrote:
> >
> > Is it from read_connection_list? If so I have a 'patch' that I'm using but
> > haven't committed because it's just too gross: drop the lock before the
> > copyout an
On Mon, Aug 26, 2019 at 6:13 PM Lizbeth Mutterhunt, Ph.D. <
mutterhunt_ge...@yahoo.com> wrote:
> On Monday, 26 August 2019 23:35:25 CEST maksim yevmenkin wrote:
>
> > > On Aug 26, 2019, at 9:14 AM, Warner Losh wrote:
>
> > >
>
> > > Is it from read_connection_list? If so I have a 'patch' that I'm
Warner Losh wrote:
> Is it from read_connection_list? If so I have a 'patch' that I'm using but
> haven't committed because it's just too gross: drop the lock before the
> copyout and pick it up again after...
>
> Warner
>
> On Mon, Aug 26, 2019 at 1:23 AM Hans Petter Selasky wrote:
>
>> Do you
> On Aug 26, 2019, at 9:14 AM, Warner Losh wrote:
>
> Is it from read_connection_list? If so I have a 'patch' that I'm using but
> haven't committed because it's just too gross: drop the lock before the
> copyout and pick it up again after...
>
Hmm... interesting
I only took a brief loo
Is it from read_connection_list? If so I have a 'patch' that I'm using but
haven't committed because it's just too gross: drop the lock before the
copyout and pick it up again after...
Warner
On Mon, Aug 26, 2019 at 1:23 AM Hans Petter Selasky wrote:
> Do you have a backtrace?
>
> --HPS
> _
Do you have a backtrace?
--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
I'm not repeating myself here:
kernel-crash with ubt0
|
|
|
| ||
|
|
|
| |
kernel-crash with ubt0
I'm trying to setup a bluetooth-box with freeBSD 13. uname -a: FreeBSD
freeBSD13 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r351273M: Wed Aug 21 06:50:26
CEST 2019 root@free
28 matches
Mail list logo
