Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Aug 2015 22:55:14 +0000 (GMT)
From:      jenkins-admin@FreeBSD.org
To:        emaste@FreeBSD.org, ian@FreeBSD.org, jhb@FreeBSD.org, melifaro@FreeBSD.org, jilles@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-arm@FreeBSD.org
Subject:   FreeBSD_HEAD_arm64 - Build #912 - Fixed
Message-ID:  <160992852.30.1440024917722.JavaMail.jenkins@jenkins-9.freebsd.org>
In-Reply-To: <1631439283.22.1440014492896.JavaMail.jenkins@jenkins-9.freebsd.org>
References:  <1631439283.22.1440014492896.JavaMail.jenkins@jenkins-9.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
FreeBSD_HEAD_arm64 - Build #912 - Fixed:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/912/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/912/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/912/console

Change summaries:

286947 by ian:
Add a new exit-timeout option to watchdogd.

Watchdogd currently disables the watchdog when it exits, such as during
rc.shutdown processing.  That leaves the system vulnerable to getting hung
or deadlocked during the shutdown part of a reboot.  For embedded systems
it's especially important that the hardware watchdog always be active.  It
can also be useful for servers that are administered remotely.

The new -x <seconds> option tells watchdogd to program the watchdog with the
given timeout just before exiting.  The -x value can be longer or shorter
than the -t normal time value, to allow for various exceptional conditions
at shutdown such as allowing extra time for buffer flushing.

The exit value is also used internally in the "failsafe" handling (which
used to just disable the watchdog), on the theory that if you're using this
option, "safe" means having the watchdog always running, not disabled.

The default is still to disable the watchdog on exit if -x is not specified.

Differential Revision:	https://reviews.freebsd.org/D2556 (timed out)

286946 by emaste:
compiler-rt: update __multc3 to upstream style and variable names

I introduced a local copy of __multc3 in r281221, which has now been
committed upstream to compiler-rt in revision 245296. Update our version
to match the changes made there.

Sponsored by:	The FreeBSD Foundation

286945 by melifaro:
Check value return from lle_create() for NULL.
This bug sneaked unnoticed in r286722.

Reported by:	adrian

286944 by ian:
Enable the watchdog driver on imx6, now that it works.

286943 by ian:
Make the imx watchdog actually work, by setting WDOG_CR_WDE (enable bit).
Also, follow the rules from watchdog(9) about what values to return in
various situations (especially, don't touch *error when asked to set a
non-zero timeout that isn't achievable on the hardware).

286942 by ian:
Add compatible strings for all the hardware this driver works with.

Also, move the READ/WRITE bus space access macros from the header into the
source file, and rename them to RD2/WR2 to make it clear they're 16-bit
accessors.  (READ/WRITE just don't seem like good names to be in a public
header file.)

286941 by jilles:
wordexp(): Improve some error codes.

Distinguish between WRDE_BADVAL and WRDE_SYNTAX based on when the error
occurred (parsing or execution), not based on whether WRDE_UNDEF was passed.

Also, return WRDE_NOSPACE for a few more unexpected results from sh.

286940 by jhb:
ino_t is unsigned, so use uintmax_t instead of intmax_t when printing it.

Submitted by:	bde (sort of)

286939 by jhb:
Always use %j with an intmax_t cast to print time_t values.  time_t is
longer than long on 32-bit platforms with a 64-bit time_t.

Inspired by:	mail from bde

286938 by jhb:
Various style and whitespace fixes.

286937 by jhb:
Use nitems().




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?160992852.30.1440024917722.JavaMail.jenkins>