;> 404), a file with explanation and redirection to pipermail has
>>>>> been installed there.
>>>>>
>>>>> Some work is still needed for the mailing lists which has been
>>>>> transformed as readonly, this will be done in the next couple o
;>
> > >> Some work is still needed for the mailing lists which has been
> > >> transformed as readonly, this will be done in the next couple of
> > >> days
> > >
> > > It is too bad that a reference to a "no examples yet"
> &
;> readonly, this will be done in the next couple of days
> >
> > It is too bad that a reference to a "no examples yet"
> > month, such as, (at the time I write this):
> >
> > https://lists.freebsd.org/archives/freebsd-toolchain/2021-June/date.html
> >
has been transformed as
>> readonly, this will be done in the next couple of days
>
> It is too bad that a reference to a "no examples yet"
> month, such as, (at the time I write this):
>
> https://lists.freebsd.org/archives/freebsd-toolchain/2021-June/date.html
>
> does no
this):
https://lists.freebsd.org/archives/freebsd-toolchain/2021-June/date.html
does not show at least (Date view specific example):
• Other periods:[ Previous, Date view ] [ List of Folders ]
• Other: [ Actives mailing lists ] [ Archives from mailman's time ]
when there are prior
Hi Steve,
Am 06.06.21 um 01:13 schrieb Steve Kargl:
> On Sun, Jun 06, 2021 at 01:00:40AM +0200, Michael Gmelin wrote:
>>
>>
>>> On 6. Jun 2021, at 00:53, Steve Kargl
>>> wrote:
>>>
>>> It seems someone has tried to migrate the mailing lis
o, click
> > FreeBSD-net and then "Archives from mailman’s time", you get to a list that
> > brings you to https://lists.freebsd.org/pipermail/freebsd-net/. So the
> > old archives are still reachable that way. (I still find the
> > docs.FreeBSD.org/mail page to be confusing
On 06/06/2021 00:28, Steve Kargl wrote:
Hundreds of emails from me are now gone or sufficiently hidden that
I cannot find them. More importantly, Bruce Evans often replied
with reviews of libm patch's I sent the list. Those reviews and
his detailed analysis of the libm code are now go
There is also this useful and efficient form of archive/mirror to include
in the update so that it does not remain broken for too long...
https://lists.freebsd.org/pipermail/freebsd-questions/2021-June/294104.html
https://lists.freebsd.org/archives/freebsd-hubs/2021-June/00.html
/mailman/listinfo, click
>> > FreeBSD-net and then "Archives from mailman’s time", you get to a list
>> > that brings you to https://lists.freebsd.org/pipermail/freebsd-net/. So
>> > the old archives are still reachable that way. (I still find the
>> &
On Sat, Jun 5, 2021, 5:29 PM Steve Kargl
wrote:
> On Sun, Jun 06, 2021 at 01:04:46AM +0200, Michael Gmelin wrote:
> >
> > p.s. If you go to https://lists.freebsd.org/mailman/listinfo, click
> FreeBSD-net and then "Archives from mailman’s time", you get to a lis
On Sun, Jun 06, 2021 at 01:04:46AM +0200, Michael Gmelin wrote:
>
> p.s. If you go to https://lists.freebsd.org/mailman/listinfo, click
> FreeBSD-net and then "Archives from mailman’s time", you get to a list that
> brings you to https://lists.freebsd.org/pipermail/fr
On Sun, Jun 06, 2021 at 01:00:40AM +0200, Michael Gmelin wrote:
>
>
> > On 6. Jun 2021, at 00:53, Steve Kargl
> > wrote:
> >
> > It seems someone has tried to migrate the mailing list archives
> > from mailman to some new fangle code. This has broken t
> On 6. Jun 2021, at 01:00, Michael Gmelin wrote:
>
>
>
>
>>> On 6. Jun 2021, at 00:53, Steve Kargl
>>> wrote:
>>>
>> It seems someone has tried to migrate the mailing list archives
>> from mailman to some new fangle code. This ha
> On 6. Jun 2021, at 00:53, Steve Kargl
> wrote:
>
> It seems someone has tried to migrate the mailing list archives
> from mailman to some new fangle code. This has broken the archives
> for at least freebsd-numerics@, freebsd-office@, freebsd-net@
>
> As a
It seems someone has tried to migrate the mailing list archives
from mailman to some new fangle code. This has broken the archives
for at least freebsd-numerics@, freebsd-office@, freebsd-net@
As a comparison, simply go to
https://lists.freebsd.org/mailman/listinfo
and follow the links to
008 - free - (1.0M)
>> 534528 25165824 da0p2 swp12a (12G)
>> 25700352 25165824 da0p4 swp12b (12G)
>> 50866176 417994752 da0p3 zfs0 (199G)
>> 468860928 1160 - free - (580K)
>>
>> There is just one pool: zroot and i
>25700352 25165824 da0p4 swp12b (12G)
>50866176 417994752 da0p3 zfs0 (199G)
> 468860928 1160 - free - (580K)
>
> There is just one pool: zroot and it is on zfs0 above.
>
> # zpool list -p
> NAME SIZEALLOC FREE CKP
fs0 (199G)
468860928 1160 - free - (580K)
There is just one pool: zroot and it is on zfs0 above.
# zpool list -p
NAME SIZEALLOC FREE CKPOINT EXPANDSZ FRAGCAP
DEDUPHEALTH ALTROOT
zroot 213674622976 71075655680 142598967
nts/keme3b/-/ggs61in/?context=1> there's an
example command that shows a FreeBSD-CURRENT Git revision number of 11
following an update.
The phrase 'revision number' might be not technically accurate, but the
numbers _are_ sequential.
The command uses the '--count' op
On Thu, Sep 10, 2020 at 12:46:45PM -0400, Ryan Moeller wrote:
>
> On 9/10/20 12:33 PM, Shawn Webb wrote:
> > I used to be able to run `zfs list` as an unprivileged user. Now I
> > can't, even when my user is in the operator group.
> >
> > BEGIN LOG ==
On 9/10/20 12:33 PM, Shawn Webb wrote:
I used to be able to run `zfs list` as an unprivileged user. Now I
can't, even when my user is in the operator group.
BEGIN LOG
hbsd-current-01[shawn]:/home/shawn $ zfs list
Operation not permitted
hbsd-current-01[shawn]:/home/shawn (1)
I used to be able to run `zfs list` as an unprivileged user. Now I
can't, even when my user is in the operator group.
BEGIN LOG
hbsd-current-01[shawn]:/home/shawn $ zfs list
Operation not permitted
hbsd-current-01[shawn]:/home/shawn (1) $ id
uid=1001(shawn) gid=1001(shawn) groups
up in December
I cannot tell how long this has been broken.
Florian
___
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"
The list is shorter than it was for an old PowerMac G4
(32-bit powerpc).
For a G5 powerpc64 example running head -r356187 (so
ELFv2):
# dmesg -a | grep Giant
WARNING: Device "openfirm" is Giant locked and may be deleted before FreeBSD
13.0.
WARNING: Device "kbd" is Gia
ed with kern.vty=sc , mostly
because on some other hardware kern.vty=vt
historically did not handle the 2560x1440
screen [crashing during boot] but sc worked
fine. )
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
____
ng to the space
available after the other columns at any stage that I found.
In essence I'm trying to ask based on where it looks like
the issue might have started.)
Was some other part of the code supposed to prevent lines
that can not fit the space from overwriting other text
from other proc
Hi,
I just put a patch for mountd.c in phabricator as D20270, which replaces the
single linked list of structures for exported file systems with a hash table of
lists.
This is part of what I hope will fix the performance of mountd when reloading
the exports file(s) for a server with a lot of
I suspect this is a side-effect of r340742 ("proc: implement pid hash
locks and an iterator").
Prior to the change exporting code would just iterate allproc, which
will appear sorted for
*most* processes and most importantly kernel ones. Note the allproc
list is most definitely
not
ntr]
>>>> 412 root 1 20010M72K select 2 0:00 0.00%
>>>> /sbin/devd
>>>> 796 root 1 52020M 672K select 0 0:00 0.00%
>>>> /usr/sbin/sshd
>>>> 13 root 3 -8- 048K
.00%
>>> /sbin/devd
>>> 796 root 1 52020M 672K select 0 0:00 0.00%
>>> /usr/sbin/sshd
>>> 13 root 3 -8- 048K -1 0:11 0.00% [geom]
>>> 14 root 20 -68- 0 320K -0 0:02
.00%
>> dhclient: awg0 [priv] (dhclient)
>> 15 root 1 -16- 016K -0 0:00 0.00%
>> [soaiod1]
>> 239 _dhcp 1 20012M 484K select 1 0:00 0.00%
>> dhclient: awg0 (dhclient)
>>
>> (Basically the Pine6
> No wonder, it doesn't seem to have worked ever (?) as the compare_pid is
> simply not defined in compares list. Try attached patch.
It works on 11-stable without that line being added.
cheers
___
freebsd-current@freebsd.org mailing
nt: awg0 [priv] (dhclient)
>15 root 1 -16- 016K -0 0:00 0.00%
> [soaiod1]
> 239 _dhcp 1 20012M 484K select 1 0:00 0.00%
> dhclient: awg0 (dhclient)
>
> (Basically the Pine64+ 2GB [aarch64] above was idle after boot oth
at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
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"
nt
>
> I tested on zfs, perhaps there is something extra going on on other
> filesystems.
>
> --
> Mateusz Guzik
>
___
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"
zfs, perhaps there is something extra going on on other filesystems.
--
Mateusz Guzik
___
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"
, maybe better to
> use the occasion to switch these fields to dev_t and ino_t?
>
> --
> Ed Schouten
>
___
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"
se fields to dev_t and ino_t?
--
Ed Schouten
___
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"
name;
STAILQ_HEAD(, consumer) consumers;
--
Mateusz Guzik
___
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"
Hello,
On FreeBSD 12 ALPHA9
> less .vimrc
> fuser .vimrc
.vimrc:
gives no pid, on FreeBSD 11.2 the above works as expected.
Regards,
Ali
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-curr
reebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 24.09.2018 11:31, Harry Schmalzbauer wrote:
> Hello,
>
> unfortunately this is far beyond my scope and I forgot to report in time.
> If this is begnin, feel free to ignore, but in any case I'd appreciate
> any comments.
Hi,
I posted a review targeted to fix this problem:
htt
Psec transforms list) r = 0
(0x815385e0) locked @
/usr/local/share/deploy-tools/HEAD/src/sys/netipsec/key.c:8676
stack backtrace:
#0 0x8084c1a3 at witness_debugger+0x73
#1 0x8084d118 at witness_warn+0x448
#2 0x80ad4f48 at uma_zalloc_arg+0x38
#3 0x807bd12a at
switch (cmd) {
> case MOD_LOAD:
> -sdev = make_dev(&foo_devsw, 0, UID_ROOT, GID_WHEEL, 0600, "foo");
> -break; /* Success*/
> + make_dev_args_init(&mda);
> + mda.mda_devsw = &foo_devsw;
> + mda.mda_uid = UID_ROOT;
>
mda.mda_uid = UID_ROOT;
+ mda.mda_gid = GID_WHEEL;
+ mda.mda_mode = 0600;
+ err = make_dev_s(&mda, &sdev, "foo");
+ break;
case MOD_UNLOAD:
case MOD_SHUTDOWN:
___
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"
Never!
On Tue, Apr 11, 2017 at 3:18 PM Sean Bruno wrote:
> ignore
>
>
___
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"
ignore
signature.asc
Description: OpenPGP digital signature
w Z
> It's not show the correct list, this commant MUST BE SHOW like a C
> locale
Must not, according to CLDR linguists.
>Note, I know that Unicode have some differents, but when tha basic
> list replacement
> and other basic default behavior must be
this [aA-zZ]*
No, last "Z" is not included.
Look this, it's a great error
I see no error. You do not include Z into [a-z] expression above, so
why
you expect it is unknown.
I lower- equal a upper-case why Z not show in this list?
No, it is not case-equal sortin
>>
>>>> show all files beginning with a and A like this [aA-zZ]*
>>>
>>> No, last "Z" is not included.
>
>
>Look this, it's a great error
I see no error. You do not include Z into [a-z] expression above, so why
you expect it is unkno
Z
% setenv LANG pt_BR.UTF-8
% ls [A-Z]
A C E i l o s w Z
b d f j m p t x
B D g k M q u y
c e h K n r v z
%
I lower- e
pt_BR.UTF-8"
LC_ALL=
$ ls
D E F a b c
$ ls [[:lower:]]*
a b c
The same applies to character class ranges in regular expressions, not
just glob(3) patterns.
-GAWollman
___
freebs
-zZ]*
>>
>> No, last "Z" is not included.
>>
>
> This is to define set of chars: { a, A-z, Z } ? A-z of course does not make
> any sense;) Of course note that in few locales z is sorted after s, meaning
> that list like that can be rather short;)
No, [A-z]
define set of chars: { a, A-z, Z } ? A-z of course does not make any
sense;) Of course note that in few locales z is sorted after s, meaning that
list like that can be rather short;)
rgds,
toomas
___
freebsd-current@freebsd.org mailing list
https:
> Hi Allan, the ls show all files without case match
>
> ls [a-z]*
>
> show all files beginning with a and A like this [aA-zZ]*
No, last "Z" is not included.
___
freebsd-current@freebsd.org mailing list
https://lists.fre
**
* Nilton José Rizzo Sistema de InformaçãoUFRRJ *
* http://cursos.ufrrj.br/grad/sistemas/*
* lattes:http://lattes.cnpq.br/0079460703536198*
___
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"
> On Apr 6, 2017, at 22:15, Ngie Cooper (yaneurabeya)
> wrote:
>
>
>> On Apr 6, 2017, at 21:28, Nilton José Rizzo wrote:
>
> …
>
>> [966] root@valfenda rizzo #locale
>> LANG=pt_BR.UTF-8
>> LC_CTYPE="pt_BR.UTF-8"
>> LC_COLLATE="pt_BR.UTF-8"
>> LC_TIME="pt_BR.UTF-8"
>> LC_NUMERIC="pt_BR.UTF-8
> On Apr 6, 2017, at 21:28, Nilton José Rizzo wrote:
…
> [966] root@valfenda rizzo #locale
> LANG=pt_BR.UTF-8
> LC_CTYPE="pt_BR.UTF-8"
> LC_COLLATE="pt_BR.UTF-8"
> LC_TIME="pt_BR.UTF-8"
> LC_NUMERIC="pt_BR.UTF-8"
> LC_MONETARY="pt_BR.UTF-8"
> LC_MESSAGES="pt_BR.UTF-8"
> LC_ALL=
I bet t
UFRRJ *
* http://cursos.ufrrj.br/grad/sistemas/*
* lattes:http://lattes.cnpq.br/0079460703536198*
___
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"
03536198*
___
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"
URRENT #2 r313684: Sun Feb
> 12 20:52:19 BRST 2017 rizzo@valfenda:/usr/obj/usr/src/sys/VALFENDA amd64
> %
>
Maybe I am missing something. What is the problem with the output?
ls just appears to be doing columns.
--
Allan Jude
___
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"
urrent@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
"freebsd-current-unsubscr...@freebsd.org"
[966] root@valfenda rizzo #locale
LANG=pt_BR.UTF-8
LC_CTYPE="pt_BR.UTF-8"
LC_COLLATE="pt_BR.UTF-8&quo
T FreeBSD 12.0-CURRENT #2 r313684: Sun Feb
> 12 20:52:19 BRST 2017 rizzo@valfenda:/usr/obj/usr/src/sys/VALFENDA amd64
> %
Hi Nilton,
What's your locale set to and what's your filesystem?
Thanks!
-Ngie
___
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"
03536198*
___
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"
p?
>>
>> This has caused a considerable amount of excitement on the freebsd.org
>> cluster. Having kernel+world out of sync causes zfs(8) to abort rather
>> ungracefully.
>>
>>> On 03/09/2016 21:50, Subbsd wrote:
>>>> Hi.
>>>>
>>>
s has caused a considerable amount of excitement on the freebsd.org
> cluster. Having kernel+world out of sync causes zfs(8) to abort rather
> ungracefully.
>
>> On 03/09/2016 21:50, Subbsd wrote:
>> > Hi.
>> >
>> > Can anybody test of output for:
>>
> On 03/09/2016 21:50, Subbsd wrote:
> > Hi.
> >
> > Can anybody test of output for:
> >
> > zfs list
> >
> > command on FreeBSD current after r305211 ? On my hosts his leads to
> > zfs segfault.
--
Peter Wemm - pe...@wemm.org; pe...@fre
Out of sync kernel / world?
Do you have a crash dump?
On 03/09/2016 21:50, Subbsd wrote:
Hi.
Can anybody test of output for:
zfs list
command on FreeBSD current after r305211 ? On my hosts his leads to
zfs segfault.
___
freebsd-current@freebsd.org
Hi.
On 03.09.2016 23:50, Subbsd wrote:
> Can anybody test of output for:
>
> zfs list
>
> command on FreeBSD current after r305211 ? On my hosts his leads to
> zfs segfault.
Works normally for me at r305342. Any more information?
-
Hi.
Can anybody test of output for:
zfs list
command on FreeBSD current after r305211 ? On my hosts his leads to
zfs segfault.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
of a different issue when
WITH_META_MODE was attempted.
===
Mark Millard
markmi at dsl-only.net
___
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"
bobu...@somesillydomainname.com'
>>> so I have to build a custom kernel with longer usernames patched for
>>> the systems that need to deal with system logins like that.
>>>
>>
>> While I don't have that issue, it does sound like an old time
>> limita
ve to build a custom kernel with longer usernames patched for
>> the systems that need to deal with system logins like that.
>>
>
> While I don't have that issue, it does sound like an old time
> limitation that should be considered for rework. Maybe it could be
> made into an
ins like that.
While I don't have that issue, it does sound like an old time
limitation that should be considered for rework. Maybe it could be
made into an adjustable sysctl.
--
FreeBSD - the place to B...Software Developing
Shane Ambler
___
nit() for process-shared
mutex, from different processes. This situation is declared as undefined
by Posix and really is quite severe bug for unchecked implementations.
I committed the workaround as r297185.
___
freebsd-current@freebsd.org mailing l
0x000805617d3b in __raise (s=6) at /usr/src/lib/libc/gen/raise.c:52
#2 0x000805617ca9 in abort () at /usr/src/lib/libc/stdlib/abort.c:65
#3 0x00080533d484 in _thread_exit (
fname=0x80533eb66 "/usr/src/lib/libthr/thread/thr_mutex.c", lineno=150,
msg=0x7fffd300 &quo
fic setting is
> CPUTYPE?=nehalem
> in make.conf
In other words, there is no virtualization involved.
I think that the problem at hands is not related to clang update. You
recently rebuilt kde libs, which probably triggered detection of the new
feature, process-shared locks in our libthr. Befo
On Monday 21 March 2016 09:07:10 you wrote:
> On Mon, Mar 21, 2016 at 07:21:02AM +0200, Konstantin Belousov wrote:
> > On Sun, Mar 20, 2016 at 09:28:13AM +0200, Oleg V. Nauman wrote:
> > > Fatal error 'mutex 0x800632000 own 0x1885c 0x1885c is on list 0x0
> > > 0x80d
On Mon, Mar 21, 2016 at 07:21:02AM +0200, Konstantin Belousov wrote:
> On Sun, Mar 20, 2016 at 09:28:13AM +0200, Oleg V. Nauman wrote:
> > Fatal error 'mutex 0x800632000 own 0x1885c 0x1885c is on list 0x0
> > 0x80d46ebc0'
> > at line 155 in file /usr/src/lib/libth
On Sun, Mar 20, 2016 at 09:28:13AM +0200, Oleg V. Nauman wrote:
> Fatal error 'mutex 0x800632000 own 0x1885c 0x1885c is on list 0x0
> 0x80d46ebc0'
> at line 155 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 2 )
>
> What I have got after app
t; > >
> > > applications ) after recent CURRENT update. Attempt to start application
> > > cause Abort trap (6) with "Fatal error 'mutex is on list' at line 139 in
> > > file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)" output on
> &
t; #3 0x0008053564b4 in _thread_exit (
> >
> > fname=0x805357b70 "/usr/src/lib/libthr/thread/thr_mutex.c",
> > lineno=139,
> > msg=0x805357b97 "mutex is on list") at
> >
> > /usr/src/lib/libthr/thread/thr_exit.c:182
> >
curthread);
}
+
+void
+__thr_pshared_atfork_pre(void)
+{
+
+ _thr_rwl_rdlock(&pshared_lock);
+}
+
+void
+__thr_pshared_atfork_post(void)
+{
+
+ _thr_rwl_unlock(&pshared_lock);
+}
___
freebsd-current@freebsd.org mailing list
https://lists.fr
On Thu, Mar 17, 2016 at 09:40:11PM +0200, Oleg V. Nauman wrote:
>
> I'm experiencing issue with threaded applications ( including many KDE
> applications ) after recent CURRENT update. Attempt to start application
> cause
> Abort trap (6) with "Fatal error 'mu
t; #3 0x0008053564b4 in _thread_exit (
> >
> > fname=0x805357b70 "/usr/src/lib/libthr/thread/thr_mutex.c",
> > lineno=139,
> > msg=0x805357b97 "mutex is on list") at
> >
> > /usr/src/lib/libthr/thread/thr_exit.c:182
> >
, lineno=139,
> msg=0x805357b97 "mutex is on list") at
> /usr/src/lib/libthr/thread/thr_exit.c:182
> #4 0x00080534cddc in mutex_assert_not_owned (m=0x80064d000)
> at /usr/src/lib/libthr/thread/thr_mutex.c:139
> #5 0x00080534cfb9 in enqueue_mutex (curthr
; +++ b/lib/libthr/thread/thr_pshared.c
> @@ -252,3 +252,17 @@ __thr_pshared_destroy(void *key)
> pshared_clean(key, val);
> pshared_gc(curthread);
> }
> +
> +void
> +__thr_pshared_atfork_pre(void)
> +{
> +
> + _thr_rwl_rdlock(&pshared_lock);
> +}
&g
imedlock (mutex=0x81828,
> >
> > abstime=0x7fffc468) at /usr/src/lib/libthr/thread/thr_mutex.c:566
> >
> > 566 ret = mutex_lock_common(m, abstime, 0);
> > Current language: auto; currently minimal
> > (gdb) p *mu
tart application
> > cause Abort trap (6) with "Fatal error 'mutex is on list' at line 139 in
> > file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 35)" output on
> > console.
> >
> > FreeBSD 11.0-CURRENT amd64 r296887
> >
> > Bac
/lib/libthr/thread/thr_exit.c:182
> > >
> > > #4 0x000803ed56fc in mutex_lock_common (m=,
> > >
> > > abstime=, cvattach=)
> > > at /usr/src/lib/libthr/thread/thr_mutex.c:139
> > >
> > > #5 0x000803ed4c20 in __pthre
gdb) f 5
> #5 0x000803ed4c20 in __pthread_mutex_timedlock (mutex=0x81828,
> abstime=0x7fffc468) at /usr/src/lib/libthr/thread/thr_mutex.c:566
> 566 ret = mutex_lock_common(m, abstime, 0);
> Current language: auto; currently minimal
> (gdb) p *mutex
> $1 = 0x8001
> (gdb) p m
> $2 =
> (gdb) p *m
> Cannot access memory at address 0x130049
> (gdb)
Try devel/gdb. Also, you could recompile libthr with DEBUG_FLAGS="-O0 -g"
to get rid of optimizations.
___
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"
in __pthread_mutex_timedlock (mutex=0x81828,
abstime=0x7fffc468) at /usr/src/lib/libthr/thread/thr_mutex.c:566
566 ret = mutex_lock_common(m, abstime, 0);
Current language: auto; currently minimal
(gdb) p *mutex
$1 = 0x8001
(gdb) p m
$2 =
(gdb) p *m
Cannot access memory at address 0x130049
(gdb)
Thank you!
___
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"
; > #4 0x000803ed56fc in mutex_lock_common (m=,
> > abstime=, cvattach=)
> > at /usr/src/lib/libthr/thread/thr_mutex.c:139
> > #5 0x000803ed4c20 in __pthread_mutex_timedlock (mutex=0x81828,
> > abstime=0x7fffc468) at /usr/src/lib/libthr/threa
x81828,
> abstime=0x7fffc468) at /usr/src/lib/libthr/thread/thr_mutex.c:566
>
Again, please show me
p *mutex
p m
p *m
from the frame 5.
___
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 experiencing issue with threaded applications ( including many KDE
applications ) after recent CURRENT update. Attempt to start application cause
Abort trap (6) with "Fatal error 'mutex is on list' at line 139 in file
/usr/src/lib/libthr/thread/thr_mutex.c (errno = 35
_mutex_timedlock (mutex=0x81828,
abstime=0x7fffc468) at /usr/src/lib/libthr/thread/thr_mutex.c:566
___
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"
GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...
Unread portion of the kernel message buffer:
panic: worklist_remove: 0xca327d00 allocdirect(0x20005) not on list
cpuid = 2
KDB: enter: panic
Reading symbols from
/usr/local/lib/vmware-too
e:
>
> http://www.univie.ac.at
>
The Laptop Compability list was first created by Lukas and hosts at the
University of Vienna. When it wasn't maintained any longer some people
of bsdgroup.de were allowed to host and maintain the page on their
domain.
Unfortunately, bsdgroup.de isn
Hi,
On Thu, 2 Oct 2014 01:48:39 -0700
Craig Rodrigues wrote:
> Hi,
>
> I e-mailed Lukas Ertl about
I think that you to the wrong URL. The university of vienna is here:
http://www.univie.ac.at
Erich
___
freebsd-current@freebsd.org mai
1 - 100 of 356 matches
Mail list logo
