On Sat, 02 May 2020 16:28:46 -0700
Chris wrote:
> On Sun, 3 May 2020 00:15:48 +0100 Grzegorz Junka li...@gjunka.com said
>
> > On 02/05/2020 20:43, Chris wrote:
> > > On Sat, 2 May 2020 20:19:56 +0100 Grzegorz Junka li...@gjunka.com said
> > >
> > >> On 02/05/2020 14:56, Grzegorz Junka wrote
--- Original message ---
From: "Mark Millard"
Date: 3 May 2020, 04:47:14
> [I'm only claiming the new jemalloc is involved and that
> reverting avoids the problem.]
>
> I've been reporting to some lists problems with:
>
> dhclient
> sendmail
> rpcbind
> mountd
> nfsd
>
> getting SIG
On Sun, 29 Mar 2020 15:36:22 +0200
Willem Jan Withagen wrote:
> I keep getting errors in building my ports from portsbuilder.
> But it is with Current/Clang10.
>
> So I'm trying to get a server at that level, but building world
> keeps giving me:
> --- all_subdir_cddl ---
> ld:
> error: /usr/obj
On 03/05/2020 08:05, Gary Jennejohn wrote:
On Sat, 02 May 2020 16:28:46 -0700
Chris wrote:
Another thing is that I don't quite understand why the crash couldn't
be dumped.
root@crayon2:~ # swapinfo
Device__ 1K-blocks Used__ Avail Capacity
/dev/zvol/tank3/swap_
On 02/05/2020 10:08, Grzegorz Junka wrote:
I am compiling some packages with poudriere on 13-current kernel. I
noticed some strange messages printed into the terminal and dmesg:
lock order reversal:
1st 0xf8010ca78250 zfs (zfs) @ /usr/src-13/sys/kern/vfs_mount.c:1005
2nd 0xf8010cd372
On 2020-05-02 20:36, Kurt Jaeger wrote:
Hi!
I am compiling some packages with poudriere on 13-current kernel. I
noticed some strange messages printed into the terminal and dmesg:
lock order reversal:
[...]
Are those the debug messages that aren't visible on non-current kernel
and should they
On Sun, 3 May 2020 14:11:09 +0100
Grzegorz Junka wrote:
> On 03/05/2020 08:05, Gary Jennejohn wrote:
> > On Sat, 02 May 2020 16:28:46 -0700
> > Chris wrote:
> >
> >>
> >>>
> > Another thing is that I don't quite understand why the crash couldn't
> > be dumped.
> >
> > root@
On 03/05/2020 15:00, Niclas Zeising wrote:
On 2020-05-02 20:36, Kurt Jaeger wrote:
I don't know, either 8-} bz@ is in Cc:, so he'll probably know what
to do.
How do I know if I have got a backtrace?
Are those errors:
pid 43297 (conftest), jid 5, uid 0: exited on signal 11
related or it's
On 03/05/2020 15:13, Gary Jennejohn wrote:
On Sun, 3 May 2020 14:11:09 +0100
Grzegorz Junka wrote:
I don't have a partition that I could use for swap. I have two whole
disks added to ZFS. Maybe on the boot drive but that would require
repartitioning and I have Windows/FreeBSD there, so not s
--- Original message ---
From: "Mark Millard"
Date: 3 May 2020, 17:38:14
>
>
> On 2020-May-3, at 01:26, nonameless at
> ukr.net wrote:
>
>
>
>
> > --- Original message ---
> > From: "Mark Millard"
> > Date: 3 May 2020, 04:47:14
> >
> >
> >
> >> [I'm only claiming the new jem
On Sat, 2020-05-02 at 20:36 +0200, Kurt Jaeger wrote:
> Hi!
>
> > > > I am compiling some packages with poudriere on 13-current kernel. I
> > > > noticed some strange messages printed into the terminal and dmesg:
> > > >
> > > > lock order reversal:
> > >
> > > [...]
> > > > Are those the debug
On 03/05/2020 06:05, Graham Perrin wrote:
After reverting from OpenZFS to ZFS, I was able to destroy two of the
boot environments that previously (below, 1st May, OpenZFS) could not
be destroyed.
I'm left with at least one BE 'r360237c' that can not be destroyed. Is
it ever normal to find a s
On Sun, May 03, 2020 at 10:04:04AM -0600, Ian Lepore wrote:
> That LOR site hasn't been updated in years. Many many years.
If someone wants to help me set up a page on the wiki, let me know.
(I have too much on my plate to do it myself.)
mcl
___
freebs
On 2020-May-3, at 01:26, nonameless at ukr.net wrote:
> --- Original message ---
> From: "Mark Millard"
> Date: 3 May 2020, 04:47:14
>
>
>
>> [I'm only claiming the new jemalloc is involved and that
>> reverting avoids the problem.]
>>
>> I've been reporting to some lists problems with:
In message <20200430130449.cwsf3x42o6w67...@ivaldir.net>, Baptiste
Daroussin wr
ites:
>
>
> --mvhxgm4zl62unzlf
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Thu, Apr 30, 2020 at 05:56:54AM -0700, Cy Schubert wrote:
[At around 4AM local time dhcient got a signal 11,
despite the jemalloc revert. The other exmaples
have not happened.]
On 2020-May-2, at 18:46, Mark Millard wrote:
> [I'm only claiming the new jemalloc is involved and that
> reverting avoids the problem.]
>
> I've been reporting to some lists p
[The bit argument ot bitmap_unset seems to be way
too large.]
On 2020-May-3, at 11:08, Mark Millard wrote:
> [At around 4AM local time dhcient got a signal 11,
> despite the jemalloc revert. The other exmaples
> have not happened.]
>
> On 2020-May-2, at 18:46, Mark Millard wrote:
>
>> [I'm on
17 matches
Mail list logo