Automated report: NetBSD-current/i386 build failure

2018-11-14 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 2018.11.15.05.14.20. An extract from the build.sh output follows: #define NULL ((void *)0) ^

daily CVS update output

2018-11-14 Thread NetBSD source update
Updating src tree: U src/distrib/sets/lists/xdebug/md.iyonix P src/external/cddl/osnet/sys/sys/isa_defs.h P src/sbin/fdisk/fdisk.c P src/sys/arch/aarch64/include/param.h P src/sys/arch/arm/cortex/gicv3.c P src/sys/arch/evbarm/conf/std.generic P src/sys/arch/hppa/hppa/fpu.c P

ThinkPad - suspend-to-RAM intel-x86 issues and tests

2018-11-14 Thread Riccardo Mottola
HI all, I take the discussion started on a similar thread on netbsd-users over here, since it is still a "current" issue and to debug it I am using netbsd-GENERIV kernels from RelEng. I am narrowing tests on two machines, a ThinkPad R51 (intel graphics) and a Thinkpad T30 (ATI graphics).

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

2018-11-14 Thread Andreas Gustafsson
Robert Elz wrote: > | The newly failing test case is: > | > | sbin/gpt/t_gpt:migrate_disklabel [...] > That leaves mrg's gcc changes, and if gcc has started generating bad code for > (the fairly simple source that is) fdisk (or for dd, which makes a filesys > image via a copy from