Date:Wed, 13 Mar 2019 11:09:09 +0700
From:Robert Elz
Message-ID: <27829.1552450...@jinx.noi.kre.to>
A few corrections/additions to my message:
| "page" is the page size.(4KB, 8KB or 16KB or ...)
Looks to be 4K. Is that correct?
| From the number of kernel
Apologies for the multi-list posting, but I think this needs a wide
audience - please respect the Reply-To and send replies only to
current-users@
I have been looking into this, a little.
First, while the t_mlock() test is most likely broken, it
should never cause a kernel panic (or even a
Updating src tree:
cvs update: `src/crypto/external/bsd/openssl/dist/.gitattributes' is no longer
in the repository
cvs update: `src/crypto/external/bsd/openssl/dist/.gitignore' is no longer in
the repository
cvs update: `src/crypto/external/bsd/openssl/dist/.gitmodules' is no longer in
the
/etc/ttys ?
On Tue, 12 Mar 2019 at 16:32, Patrick Welche wrote:
> Had a go with the shiny new X (thanks!) on the sandy bridge laptop
> which no longer likes SNA but works with UX, and xdm seems to sit
> at the prompt waiting for something:
>
> #0 0x7f7ff344285a in poll () from
On Tue, Mar 12, 2019 at 03:33:26PM +, Chavdar Ivanov wrote:
> On amd64 -curent from yesterday (and a couple of days earlier) I
> started to get zsh crashes when tab-completing (files, directories,
> packages), similar to
I see lots of crashes with zsh too.
Some happen in completion,
Patrick Welche writes:
> Had a go with the shiny new X (thanks!) on the sandy bridge laptop
> which no longer likes SNA but works with UX, and xdm seems to sit
> at the prompt waiting for something:
>
> #0 0x7f7ff344285a in poll () from /usr/lib/libc.so.12
> #1 0x7f7ff6031f3d in IoWait
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2019.03.12.16.44.12 christos
src/crypto/external/bsd/openssl/dist/test/bio_memleak_test.c,v 1.1
2019.03.12.16.44.16 christos
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2019.03.12.15.14.02.
An extract from the build.sh output follows:
obsolete_stand fix:
postinstall fixes passed:
Had a go with the shiny new X (thanks!) on the sandy bridge laptop
which no longer likes SNA but works with UX, and xdm seems to sit
at the prompt waiting for something:
#0 0x7f7ff344285a in poll () from /usr/lib/libc.so.12
#1 0x7f7ff6031f3d in IoWait (wt=0x7f7fcec0, wf=,
wf=)
On Tue, Mar 12, 2019 at 03:33:26PM +, Chavdar Ivanov wrote:
> Hi,
>
> On amd64 -curent from yesterday (and a couple of days earlier) I
> started to get zsh crashes when tab-completing (files, directories,
> packages), similar to
> .
> Core was generated by `zsh'.
> Program terminated
In article ,
Chavdar Ivanov wrote:
>Hi,
>
>On amd64 -curent from yesterday (and a couple of days earlier) I
>started to get zsh crashes when tab-completing (files, directories,
>packages), similar to
>.
>Core was generated by `zsh'.
>Program terminated with signal SIGSEGV, Segmentation
Hi,
On amd64 -curent from yesterday (and a couple of days earlier) I
started to get zsh crashes when tab-completing (files, directories,
packages), similar to
.
Core was generated by `zsh'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7cf050211540 in permmatches ()
12 matches
Mail list logo
