Hi All!
We got this build failure, when two release make release running in parallel:
10-STABLE:
-
--
stage 4.4: building everything
--
pwd_mkdb:
See https://jenkins.freebsd.org/job/Build-UFS-image/1922/changes
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
actually, the following are interesting further down:
#13 0x808af473 in sys_write (td=0xdeadc0dedeadc116,
uap=value optimized out) at /usr/src/sys/kern/sys_generic.c:398
#14 0x80b57a6d in amd64_syscall (td=0xf80736fda4c0,
traced=0)
at subr_syscall.c:133
the td
FreeBSD_HEAD-tests - Build #1162 - Still Failing:
Check console output at
https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1162/ to view the results.
___
freebsd-current@freebsd.org mailing list
On Sun, Jul 05, 2015 at 12:45:25PM -0700, Garrett Cooper wrote:
On Jul 5, 2015, at 8:16, Rink Springer r...@freebsd.org wrote:
Hi all,
On my FreeBSD/mips machine (it's a RouterStation Pro), I get the
following panic during boot:
?
This reproduces 100%. I'm at:
FreeBSD
Oliver Pinter oliver.pin...@hardenedbsd.org wrote:
We got this build failure, when two release make release running in parallel:
Can you elaborate what you mean by two release make release ?
Do you mean two separate builds running in the same tree at the same
time using the same DESTDIR?
On Mon, Jul 6, 2015 at 10:26 PM, Simon J. Gerraty s...@juniper.net wrote:
Oliver Pinter oliver.pin...@hardenedbsd.org wrote:
We got this build failure, when two release make release running in parallel:
Can you elaborate what you mean by two release make release ?
Two concurrent make release
Hi
ntpq/ntpd appear inconsistent since at least r284659, reporting my
refclocks as false tick and the other selected for PPS, but not
time source:
[brane] ~/graphing $ ntpq -c peers
remote refid st t when poll reach delay offset jitter
Am Sun, 05 Jul 2015 09:42:16 -0500
Larry Rosenman l...@lerctr.org schrieb:
On 2015-07-05 04:14, O. Hartmann wrote:
Am Sat, 04 Jul 2015 18:56:31 -0500
Larry Rosenman l...@lerctr.org schrieb:
--- kernel.debug ---
linking kernel.debug
I see the same here on most recen source
On 2015-07-06 16:12, O. Hartmann wrote:
Am Sun, 05 Jul 2015 09:42:16 -0500
Larry Rosenman l...@lerctr.org schrieb:
On 2015-07-05 04:14, O. Hartmann wrote:
Am Sat, 04 Jul 2015 18:56:31 -0500
Larry Rosenman l...@lerctr.org schrieb:
--- kernel.debug ---
linking kernel.debug
I see the same
It has been discovered that r275732[1] on HEAD introduced a bug in the
aesni(4) module where the initialization vector (IV) is not properly
generated when using AES-CBC, aka rijndael-cbc. This only happens
when both the CRD_F_IV_PRESENT and CRD_F_IV_EXPLICIT flags are not
set. This ONLY affects
I've enabled DEBUG_REDZONE, and have DEBUG_MEMGUARD in the system, but
have zero clue as to what to set for memguard :(
Could I get some guidance?
On 2015-07-06 17:43, K. Macy wrote:
That's really disturbing, but could be an artifact of limitations in debug
info fidelity. If curthread
That's really disturbing, but could be an artifact of limitations in debug
info fidelity. If curthread is corrupt I would expect things to blow up
almost instantly.
Try enabling memguard for the zone or mtype for the object that has the
corrupt mutex field.
-K
On Jul 6, 2015 5:48 AM, Larry
FreeBSD_HEAD-tests - Build #1163 - Still Failing:
Check console output at
https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1163/ to view the results.
___
freebsd-current@freebsd.org mailing list
As documented in the release notes and UPDATING, the following changes
accompanies the merge of sendmail 8.15.2 to HEAD:
sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
default, i.e., they
15 matches
Mail list logo