Fw: (Not so) New Install

2019-08-26 Thread Germain Le Chapelain
Hi! So I have been running on a new install (8.99?) since a few weeks now. I tried UEFI first (because I am not sure what it is about) and that would stall on start-up. I have a T510. I forgot the error message sorry. Anyways the other version works great. I figured I would start a new thre

daily CVS update output

2019-08-26 Thread NetBSD source update
Updating src tree: P src/Makefile P src/distrib/sets/lists/base/md.amd64 P src/distrib/sets/lists/base/md.i386 P src/distrib/sets/lists/base/mi P src/distrib/sets/lists/comp/md.amd64 P src/distrib/sets/lists/comp/md.i386 P src/external/bsd/compiler_rt/lib/clang/lib/netbsd/sources.mk P src/externa

Re: netbsd-9 radeon GPU lockup, X stuck in "radfen/N"

2019-08-26 Thread Thomas Klausner
On Mon, Aug 26, 2019 at 10:44:37AM -0500, John D. Baker wrote: > [ 50615.096841] radeon0: autoconfiguration error: error: ring 0 stalled for > more than 6308000msec > [ 50615.096841] radeon0: autoconfiguration error: warn: GPU lockup (current > fence id 0x002505b3 last fence id 0x

netbsd-9 radeon GPU lockup, X stuck in "radfen/N"

2019-08-26 Thread John D. Baker
After updating a machine to 9.0_BETA, it ran fine for about a week and a half, but has now had to be rebooted twice in a 12-hour period (one by power-cycle) to regain control of the video console/graphics display. It seems to happen when the machine has been left idle and 'xscreensaver' activates.

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

2019-08-26 Thread Thomas Klausner
On Mon, Aug 26, 2019 at 02:57:56PM +0200, Kamil Rytarowski wrote: > On 25.08.2019 23:42, Thomas Klausner wrote: > > On Sun, Aug 25, 2019 at 05:32:32PM +0200, Kamil Rytarowski wrote: > >> On 25.08.2019 09:31, Thomas Klausner wrote: > >>> On Sun, Aug 25, 2019 at 08:09:06AM +0200, Kamil Rytarowski wro

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

2019-08-26 Thread Kamil Rytarowski
On 25.08.2019 23:42, Thomas Klausner wrote: > On Sun, Aug 25, 2019 at 05:32:32PM +0200, Kamil Rytarowski wrote: >> On 25.08.2019 09:31, Thomas Klausner wrote: >>> On Sun, Aug 25, 2019 at 08:09:06AM +0200, Kamil Rytarowski wrote: On 24.08.2019 14:51, Kamil Rytarowski wrote: > On 24.08.2019

re: amd64 build failed: constructor priorities from 0 to 100 are reserved

2019-08-26 Thread matthew green
Kamil, > ? > external/bsd/compiler_rt/lib/clang/lib/netbsd/asan-dynamic-m32/asan_activation.d i recommend building from a r/o source tree for a few days :-) this becomes a built-time failure in that case. i recommend it to everyone, really. it has been a very long time but i used to guess abou

Re: amd64 build failed: constructor priorities from 0 to 100 are reserved

2019-08-26 Thread Thomas Klausner
On Fri, Aug 23, 2019 at 04:19:25PM +0200, Kamil Rytarowski wrote: > I will try to reproduce and fix it. I saw you committed a fix, I'll test it now. A different issue: while I was updating for testing the fix, I saw lots of files where they shouldn't be. I run build.sh with '-O /somewhere', so a

Re: Automated report: NetBSD-current/i386 test failure

2019-08-26 Thread Martin Husemann
On Mon, Aug 26, 2019 at 11:03:06AM +0200, Martin Husemann wrote: > This also broke the build for aarch64, hppa and sun2. > > 10:49 i think the problem is that we'll have to make it -lnpf -lnv > 10:50 with the private library objdir added to the -L path or similar > > see: http://releng.netbsd.o

Re: Automated report: NetBSD-current/i386 test failure

2019-08-26 Thread Martin Husemann
On Mon, Aug 26, 2019 at 03:13:29AM +, NetBSD Test Fixture wrote: > This is an automatically generated notice of new failures of the > NetBSD test suite. > > The newly failing test cases are: > > net/if_ipsec/t_ipsec_pfil:ipsecif_pfil_esp_null > net/if_ipsec/t_ipsec_pfil:ipsecif_pfil_e