daily CVS update output
Updating src tree: P src/sbin/fsck_lfs/bufcache.c P src/sbin/ping/ping.c P src/sbin/sysctl/sysctl.c P src/sys/arch/ia64/ia64/db_trace.c P src/sys/arch/ia64/unwind/stackframe.c P src/sys/arch/ia64/unwind/stackframe.h P src/sys/arch/mips/mips/syscall.c P src/sys/arch/mips/mips/vm_machdep.c P src/sys/dev/fss.c P src/sys/kern/vfs_bio.c P src/sys/kern/vfs_syscalls.c P src/sys/net/if.h P src/sys/sys/termios.h P src/tests/lib/libpthread/t_mutex.c P src/usr.bin/xlint/lint1/cgram.y P src/usr.bin/xlint/lint1/decl.c Updating xsrc tree: Killing core files: Running the SUP scanner: SUP Scan for current starting at Mon Aug 1 03:01:43 2016 SUP Scan for current completed at Mon Aug 1 03:02:00 2016 SUP Scan for mirror starting at Mon Aug 1 03:02:00 2016 SUP Scan for mirror completed at Mon Aug 1 03:04:22 2016 Updating release-6 src tree (netbsd-6): Updating release-6 xsrc tree (netbsd-6): Running the SUP scanner: SUP Scan for release-6 starting at Mon Aug 1 03:06:41 2016 SUP Scan for release-6 completed at Mon Aug 1 03:06:50 2016 Updating release-7 src tree (netbsd-7): Updating release-7 xsrc tree (netbsd-7): Running the SUP scanner: SUP Scan for release-7 starting at Mon Aug 1 03:09:18 2016 SUP Scan for release-7 completed at Mon Aug 1 03:09:24 2016 Updating file list: -rw-rw-r-- 1 srcmastr netbsd 54633205 Aug 1 03:11 ls-lRA.gz
drmkms panic
Hello, when i try to start graphics/blender from pkgsrc my system panics. I use a radeon hd 7650 and modular xorg. the crash dumps are available here: www.alarum.de/netbsd/netbsd.0.gz www.alarum.de/netbsd/netbsd.0.core.gz i am not subscribed to the mailing list, please cc me. bsd64$ uname -a NetBSD bsd64 7.99.34 NetBSD 7.99.34 (GENERIC.201607310950Z) amd64 bsd64$ dmesg|grep radeon radeon0 at pci1 dev 0 function 0: vendor 1002 product 679a (rev. 0x00) radeon0: info: VRAM: 3072M 0x - 0xBFFF (3072M used) radeon0: info: GTT: 1024M 0xC000 - 0x drm: radeon: 3072M of VRAM memory ready drm: radeon: 1024M of GTT memory ready. drm: radeon/TAHITI_mc2.bin: 31232 bytes drm: radeon: dpm initialized radeon0: info: WB enabled radeon0: info: fence driver on ring 0 use gpu addr 0xcc00 and cpu addr 0x0x80004a216c00 radeon0: info: fence driver on ring 1 use gpu addr 0xcc04 and cpu addr 0x0x80004a216c04 radeon0: info: fence driver on ring 2 use gpu addr 0xcc08 and cpu addr 0x0x80004a216c08 radeon0: info: fence driver on ring 3 use gpu addr 0xcc0c and cpu addr 0x0x80004a216c0c radeon0: info: fence driver on ring 4 use gpu addr 0xcc10 and cpu addr 0x0x80004a216c10 radeon0: info: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x0x800049e15a18 radeon0: interrupting at ioapic0 pin 16 (radeon) drm: radeon: irq initialized. radeondrmkmsfb0 at radeon0 radeon0: info: registered panic notifier radeondrmkmsfb0: framebuffer at 0x80004a648000, size 1280x1024, depth 32, stride 5120 wsdisplay0 at radeondrmkmsfb0 kbdmux 1: console (default, vt100 emulation)
Re: current build failure automated messages
On Sun, Jul 31, 2016 at 12:26:58PM +0300, Andreas Gustafsson wrote: > As you may have noticed, the build server now sends email to > current-users not only when the i386 build breaks, but also > when it has been fixed, with the subject line > > Automated report: NetBSD-current/i386 build success Please make it thread properly to the original failure... Joerg
Re: current build failure automated messages
As you may have noticed, the build server now sends email to current-users not only when the i386 build breaks, but also when it has been fixed, with the subject line Automated report: NetBSD-current/i386 build success -- Andreas Gustafsson, g...@gson.org
