Jenkins build is unstable: FreeBSD_HEAD #94

2016-01-31 Thread jenkins-admin
See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Jenkins build is still unstable: FreeBSD_HEAD #96

2016-01-31 Thread jenkins-admin
See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Jenkins build is still unstable: FreeBSD_HEAD #95

2016-01-31 Thread jenkins-admin
See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Build failed in Jenkins: FreeBSD_HEAD #87

2016-01-31 Thread jenkins-admin
See -- [...truncated 58358 lines...] c++ -O2 -pipe -I/builds/workspace/FreeBSD_HEAD/src/lib/clang/libllvmanalysis/../../../contrib/llvm/include

Re: thread-unsafety problems as spl*() ones are NOP

2016-01-31 Thread Slawa Olhovchenkov
On Sun, Jan 31, 2016 at 10:00:51AM +0330, mokhi wrote: > @imp: > i exactly mean (Okay not so exact but very near ;D) what you said. > after analyzing kbd.c functions (eg, kbd_realloc_array()) i concluded > there are race conditions (and at result in some places there are > un-protected data too)

Re: ZFSROOT UEFI boot

2016-01-31 Thread Tomoaki AOKI
I found Diff6 you uploaded to PHABRICATOR. So my report below is based on it. The patched boot1.efi runs as expected (== as you wrote) for me. *boot1.efi without -DEFI_DEBUG isn't tested. Needed? As I mentioned in my previous post, I have no serial console environment. So I took movie of

FreeBSD_HEAD_amd64_gcc4.9 - Build #1046 - Fixed

2016-01-31 Thread jenkins-admin
FreeBSD_HEAD_amd64_gcc4.9 - Build #1046 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/1046/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/1046/changes Full build log:

Re: ZFSROOT UEFI boot

2016-01-31 Thread Tomoaki AOKI
Sorry. I just noticed this mail is not a duplicate of which I just responded to. :-( I built boot1.efi that is applied Diff6 with -DEFI_DEBUG, but not with -DDEBUG. Was it sufficient? Or does some info be missed with above option I set? On Sat, 30 Jan 2016 12:43:31 + Steven Hartland

Re: ZFSROOT UEFI boot

2016-01-31 Thread Steven Hartland
Thanks for doing that it was very helpful, and I know transcribing from video would have been quite a time consuming task. I noticed a few interesting facts: 1. It looks like when you boot from ada0 and ada1 its still picking the same device (according to device order). Its not 100% clear as