Re: Entropy problem [was Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]]

2020-12-05 Thread Taylor R Campbell
> Date: Sat, 5 Dec 2020 15:19:15 -0800 > From: Germain Le Chapelain > > It's building firefox again, > > I haven't yet tried any work-around mentioned in the email > introducing the change But I am confused about the issue, why this > arises. > > I thought the way randomness was implemented is

Re: Entropy problem [was Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]]

2020-12-05 Thread Germain Le Chapelain
On Fri, 4 Dec 2020 06:42:20 - (UTC) mlel...@serpens.de (Michael van Elst) wrote: > germain.lechapel...@lanvaux.fr (Germain Le Chapelain) writes: > > >This time the crash was in pkg_add itself (=E2=80=98segmentation fault (core= > > dump)=E2=80=99) > > [...] Removing

Re: Entropy problem [was Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]]

2020-12-03 Thread Michael van Elst
germain.lechapel...@lanvaux.fr (Germain Le Chapelain) writes: >This time the crash was in pkg_add itself (=E2=80=98segmentation fault (core= > dump)=E2=80=99) Recently I also got a few segmentation faults from pkg_add, also when installing firefox. The coredump indicated that it failed in the

Re: Entropy problem [was Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]]

2020-12-03 Thread Germain Le Chapelain
I have gotten another crash, simply running ‘pkg_add firefox’ This was on a fresh , blank install of 9.1 This time the crash was in pkg_add itself (‘segmentation fault (core dump)’) However, I cannot find a pkg_add.core where it happened I got a message ‘the database in

Re: Entropy problem [was Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]]

2020-11-21 Thread Germain Le Chapelain
On Sat, 21 Nov 2020 00:45:26 -0800 Germain Le Chapelain wrote: > the moment I launched midori, > > Then, kernel panic I have fallen back to 8.2 for now. It holds! I did get the time out once more, I wonder if it is when the device goes inactive for a while, but I was ssh-ing to it. Aside

Re: Entropy problem [was Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]]

2020-11-21 Thread Germain Le Chapelain
On Sat, 21 Nov 2020 00:45:26 -0800 Germain Le Chapelain wrote: > I will keep this core on the side, I was dabbling again in X , while scp-ing the crash dump. It was very slow. In my message log: Nov 21 00:56:20 Nima /netbsd: [ 4249.1782296] 0001317c : Nov 21 00:56:20 Nima /netbsd: [

Re: Entropy problem [was Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]]

2020-11-21 Thread Germain Le Chapelain
On Fri, 20 Nov 2020 19:32:15 -0800 Germain Le Chapelain wrote: > So I will put on 9.1 for now, but I am happy doing more testing later, So I did, and I was having a blast installing binary package, until the moment I launched midori, Then, kernel panic: (gdb) bt #0 0x80222aaa in

Entropy problem [was Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]]

2020-11-20 Thread Germain Le Chapelain
On Fri, 20 Nov 2020 18:20:10 -0800 Germain Le Chapelain wrote: > From it, everything looks great at first glance: > only python is blocked on `entrop/2' in top, and I cannot ping google.fr It is the change https://mail-index.netbsd.org/current-users/2020/05/01/msg038495.html that seems to

Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]

2020-11-20 Thread Germain Le Chapelain
On Thu, 19 Nov 2020 01:59:28 -0800 Germain Le Chapelain wrote: > I will try soon w/ the code from when I sent the mail two weeks back, So that I got the time out again (I think ? Sorry I should have taken notes.) It was 9.99.68 > Then if it doesn't fix it with the latest (including change from

Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]

2020-11-19 Thread Germain Le Chapelain
On Thu, 19 Nov 2020 11:14:45 +0100 Martin Husemann wrote: > On Thu, Nov 19, 2020 at 01:59:28AM -0800, Germain Le Chapelain wrote: > > But I wonder if: > > > > 1) I should use netbsd-9 > > 2) Atheros works reliably, > > Both work very well for me, but: there are lots of atheros chip variants, >

Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]

2020-11-19 Thread Martin Husemann
On Thu, Nov 19, 2020 at 01:59:28AM -0800, Germain Le Chapelain wrote: > But I wonder if: > > 1) I should use netbsd-9 > 2) Atheros works reliably, Both work very well for me, but: there are lots of atheros chip variants, and bugs often are only triggered by certain wlan AP actions (so I may be

Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]

2020-11-19 Thread Germain Le Chapelain
On Wed, 18 Nov 2020 22:41:31 -0800 Germain Le Chapelain wrote: > > Hi ! > > In my attempt to debunk, I ran into another snag: > > While re-checking out pkgsrc, we got : > > client_loop: send disconnect: Broken pipe > cvs [checkout aborted]: end of file from server (conslut above messages if

Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]

2020-11-19 Thread Martin Husemann
On Wed, Nov 18, 2020 at 10:41:31PM -0800, Germain Le Chapelain wrote: > client_loop: send disconnect: Broken pipe > cvs [checkout aborted]: end of file from server (conslut above messages if > any) The second line refers to the ssh error in the first line, which is trying to tell you that

CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]

2020-11-18 Thread Germain Le Chapelain
Hi ! In my attempt to debunk, I ran into another snag: While re-checking out pkgsrc, we got : client_loop: send disconnect: Broken pipe cvs [checkout aborted]: end of file from server (conslut above messages if any) I've had it in the past! What's troubling now is that it is a completely