Automated report: NetBSD-current/i386 build success

2020-12-27 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: 2020.12.28.03.48.41 htodd src/usr.bin/Makefile,v 1.234 Logs can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2020.12.html#2020.12.28.0

daily CVS update output

2020-12-27 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/base/mi P src/distrib/sets/lists/man/mi P src/distrib/sets/lists/tests/mi P src/distrib/sets/lists/xbase/mi P src/doc/3RDPARTY P src/doc/CHANGES P src/external/bsd/openresolv/dist/resolvconf.8.in P src/external/bsd/openresolv/dist/resolvconf.conf.5.in P

Automated report: NetBSD-current/i386 build failure

2020-12-27 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 2020.12.27.21.25.02. An extract from the build.sh output follows: === checkflist

re: Audio subsystem versus unplugging uaudio

2020-12-27 Thread matthew green
nice. LGTM. .mrg.

Re: acpi panic on Dell Optiplex 760 (i82Q45 chip set)

2020-12-27 Thread John D. Baker
On Mon, 30 Nov 2020 08:01:41 +0100, Martin Husemann wrote: > Just netbsd.gdb would be enough to map the address from your backtrace, > the address did not match my local build, could have been either hid > or uid. Finally got a chance to test this again. Still panics with a very up-to-date -cur