jenkins-admin | 3 Jul 22:18 2015
Picon

FreeBSD_HEAD-tests - Build #1159 - Unstable

FreeBSD_HEAD-tests - Build #1159 - Unstable:

Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1159/ to view the results.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

jenkins-admin | 2 Jul 20:15 2015
Picon

FreeBSD_HEAD-tests - Build #1155 - Unstable

FreeBSD_HEAD-tests - Build #1155 - Unstable:

Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1155/ to view the results.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

jenkins-admin | 2 Jul 18:17 2015
Picon

Jenkins build is back to normal : Build-UFS-image #1906

See <https://jenkins.freebsd.org/job/Build-UFS-image/1906/>

_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

Benjamin Kaduk | 2 Jul 04:44 2015
Picon

Call for FreeBSD 2015Q2 (April-June) Status Reports

Dear FreeBSD Community,

The deadline for the next FreeBSD Quarterly Status update is July 14,
2015, for work done in April through June.

Status report submissions do not have to be very long.  They may be
about anything happening in the FreeBSD project and community, and
provide a great way to inform FreeBSD users and developers about what
you're working on.  Submission of reports is not restricted to
committers.  Anyone doing anything interesting and FreeBSD-related
can -- and should -- write one!

The preferred and easiest submission method is to use the XML
generator [1] with the results emailed to the status report team at
monthly at freebsd.org .  There is also an XML template [2] which can be
filled out manually and attached if preferred.  For the expected
content and style, please study our guidelines on how to write a good
status report [3].  You can also review previous issues [4][5] for
ideas on the style and format.

We are looking forward to all of your 2015Q2 reports!

Thanks,
Ben (on behalf of monthly <at> )

[1] http://www.freebsd.org/cgi/monthly.cgi
[2] http://www.freebsd.org/news/status/report-sample.xml
[3] http://www.freebsd.org/news/status/howto.html
[4] http://www.freebsd.org/news/status/report-2014-10-2014-12.html
[5] http://www.freebsd.org/news/status/report-2015-01-2015-03.html
(Continue reading)

Ryan Stone | 1 Jul 21:44 2015
Picon

How should a driver shutdown a taskqueue on detach?

I'm trying to figure out how a driver is supposed to shut down its
interrupt-handling taskqueue when it detaches.  taskqueue(9) recommends
disabling interrupts, draining each task and then freeing the taskqueue.
The problem that I have is the interrupt-handling tasks will sometimes
re-enable interrupts on the device.  Is there a better way than using some
kind of flag internally in the driver to note that a detach is in progress
that the interrupt handlers will have to check before enabling interrupts?
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

jenkins-admin | 1 Jul 04:41 2015
Picon

FreeBSD_HEAD-tests - Build #1151 - Unstable

FreeBSD_HEAD-tests - Build #1151 - Unstable:

Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1151/ to view the results.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

jenkins-admin | 30 Jun 05:43 2015
Picon

FreeBSD_HEAD-tests - Build #1148 - Failure

FreeBSD_HEAD-tests - Build #1148 - Failure:

Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1148/ to view the results.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

Jeffrey Bouquet | 29 Jun 13:10 2015

"proper way" or "unworkable idea" ?

If I've a spare /mnt/usr/src , it seems buildworld quite
soon fails, where it otherwise may succeed in /usr/src. Any CLI parameters or 
the build system is hardcoded enough so that there will always be problems? 
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

Julian Elischer | 29 Jun 10:33 2015
Picon

libc compile failure with new syscall.

Hi all,

At $JOB we have a few extra syscalls that we have added to our kernel.

After generating the new sysent files in /sys/kern, libc fails to 
compile with:

===> lib/libc (obj,depend,all,install)
building shared library libc.so.7
[...]
/usr/bin/ld: rlk_check_offline.So: relocation R_X86_64_32 against 
`SYS_rlk_check_offline' can not be used when making a shared object; 
recompile with -fPIC
rlk_check_offline.So: could not read symbols: Bad value
*** [libc.so.7] Error code 1

this suggests that the code that generates the libc syscall stubs is 
generating something the linker doesn't like.

the definition of the syscall is:

588     AUE_NULL        NOSTD   { int rlk_check_offline(char *localfs, 
char *path, \
                                     int *is_offline, int rlk_flags, \
                                     int *cache_status); }
------
which generates (in various files):
         { AS(rlk_check_offline_args), (sy_call_t *)lkmressys, 
AUE_NULL, NULL, 0, 0, 0, SY_THR_ABSENT }, /* 588 = rlk_check_offline */
------
(Continue reading)

Justin Hibbits | 28 Jun 19:48 2015
Picon

powerpc and powerpc64 builds broken

Both powerpc and powerpc64 builds are broken in the same way, in
usr.bin/mkesdb.  It was working correctly as of just before BSDCan, I
successfully built world and kernel on June 6.

The error seen at this point is:

cc  -O2 -pipe   -I/home/chmeee/freebsd/head/usr.bin/mkesdb
-I/home/chmeee/freebsd/head/usr.bin/mkesdb/../mkesdb
-I/home/chmeee/freebsd/head/usr.bin/mkesdb/../../lib/libc/iconv
-std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall
-Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
-Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align
-Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
-Wold-style-definition -Wno-pointer-sign
-L/home/chmeee/world/zhabar/home/chmeee/freebsd/head/usr.bin/mkesdb/../../lib/libc
-o mkesdb lex.o yacc.o
/home/chmeee/world/zhabar/home/chmeee/freebsd/head/tmp/usr/bin/ld:
undefined reference to symbol `_end' (try adding -lc)
/home/chmeee/world/zhabar/home/chmeee/freebsd/head/tmp/lib/libc.so.7:
could not read symbols: Bad value

I've seen this both locally on my G5, and on the Power8 in the FreeBSD cluster.

- Justin
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

(Continue reading)

jenkins-admin | 28 Jun 17:11 2015
Picon

FreeBSD_HEAD-tests - Build #1141 - Unstable

FreeBSD_HEAD-tests - Build #1141 - Unstable:

Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1141/ to view the results.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"


Gmane