Automated report: NetBSD-current/i386 build success

2021-12-29 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2021.12.30.02.14.55 rillig src/usr.bin/make/cond.c,v 1.321 2021.12.30.02.14.55 rillig src/usr.bin/make/unit-tests/cond-token-plain.exp,v 1.14 2021.1

daily CVS update output

2021-12-29 Thread NetBSD source update
Updating src tree: P src/build.sh P src/distrib/sets/sets.subr P src/distrib/sets/lists/debug/mi P src/etc/Makefile P src/external/bsd/openldap/sbin/slapd/Makefile P src/sys/conf/Makefile.kern.inc P src/sys/external/bsd/drm2/dist/drm/drm_print.c P src/sys/uvm/pmap/pmap_tlb.c P src/usr.bin/make/co

Automated report: NetBSD-current/i386 build failure

2021-12-29 Thread NetBSD Test Fixture
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 2021.12.29.22.22.13. An extract from the build.sh output follows: ./usr/share/man/man3/SQLITE_SESSION_MONOLITHIC_STR

Re: mpii panic on 9.99.92

2021-12-29 Thread Jan-Hinrich Fessel
Hej, > Am 29.12.2021 um 19:36 schrieb Michael van Elst : > > os...@fessel.org ("os...@fessel.org") writes: > >> Hej there, > >> does anyone have a clue why this is happening more frequently on = >> 9.99.92? > >> If not, i probably should send-pr that. > > > You should definitely. OK. Will

Re: Filesystem corruption in current 9.99.92 (posix1eacl & log enabled FFSv2)

2021-12-29 Thread Chuck Silvers
On Wed, Dec 29, 2021 at 08:01:53PM +0100, Matthias Petermann wrote: > Hello, > > On 27.12.21 06:20, Matthias Petermann wrote: > > I did not try to move the file around as you recommended because I would > > like to ask if there is anything I can do at this point to gather more > > diagnostic data

Re: Filesystem corruption in current 9.99.92 (posix1eacl & log enabled FFSv2)

2021-12-29 Thread Matthias Petermann
Hello, On 27.12.21 06:20, Matthias Petermann wrote: I did not try to move the file around as you recommended because I would like to ask if there is anything I can do at this point to gather more diagnostic data to help understand the root cause? in the meantime I migrated all files to a fres

Re: mpii panic on 9.99.92

2021-12-29 Thread Michael van Elst
os...@fessel.org ("os...@fessel.org") writes: >Hej there, >does anyone have a clue why this is happening more frequently on = >9.99.92? >If not, i probably should send-pr that. You should definitely. N.B. I'd rather suspect a Xen issue.

Re: HEADS UP: Merging drm update

2021-12-29 Thread Ryo ONODERA
Hi, Taylor R Campbell writes: >> Date: Tue, 28 Dec 2021 11:34:43 +0900 >> From: Ryo ONODERA >> >> intel_gt_pm_fini() at netbsd:intel_gt_pm_fini+0x18 >> intel_gt_init() at netbsd:intel_gt_init+0x6ad >> i915_gem_init() at netbsd:i915_gem_init+0x14d >> i915_driver_probe() at netbsd:i915_driver_pr

mpii panic on 9.99.92

2021-12-29 Thread os...@fessel.org
Hej there, does anyone have a clue why this is happening more frequently on 9.99.92? If not, i probably should send-pr that. Any advice on an alternative rock-solid SATA controller for the DL380 G8 that does not rev up the fans? Cheers Oskar [ 184523.7505073] panic: kernel diagnostic