Re: Starting intel driver fails on boot

On Sat, Nov 22, 2014 at 3:57 AM, Anders Bolt-Evensen wrote: > Hello. Try freebsd-x11@ or #freebsd-xorg on efnet. cheers, Hiren ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send an

Call for Help: openjdk8 tests under Continuous Integration

FYI, https://lists.freebsd.org/pipermail/freebsd-testing/2014-November/000668.html Please send followups to freebsd-test...@freebsd.org. -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To

[HEADSUP] man(1) now uses mandoc

Hi, The default renderer on HEAD has been switched to mandoc(1) by default The man(1) command has been instrumented to first test the manpage and fallback on groff if the man page cannot be rendered with mandoc(1). If base is built without groff then man(1) recommands to install groff from packag

Call for Help: Flame Graphs and Continuous Integration

FYI: https://lists.freebsd.org/pipermail/freebsd-testing/2014-November/000667.html Please send follow-ups to freebsd-test...@freebsd.org -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: zfs/vfs lockups, via poudriere

On 22/11/2014 21:20, Sean Bruno wrote: > bdrewery reported a vfs/zfs condition where operations will stall out > and block (rm, mv, file) during a poudriere build. I've hit this now > and it seems to be alleviated by setting vfs.lookup_shared=0 > > I seem to be able to trivially reproduce this on

Re: WITNESS observes 2 LORs on Boot of Release 10.1

On Fri, 21 Nov 2014, Ellis H. Wilson III wrote: > Before I start, and this is mainly geared to my responder Benjamin Kaduk, > based on your response, are you suggesting that the cnputc WITNESS panic you > expected to happen is now completely unavoidable in FreeBSD 10? I.E., is this > a spinlock t

zfs/vfs lockups, via poudriere

bdrewery reported a vfs/zfs condition where operations will stall out and block (rm, mv, file) during a poudriere build. I've hit this now and it seems to be alleviated by setting vfs.lookup_shared=0 I seem to be able to trivially reproduce this on my builders and want to know if anyone is lookin

Re: Problem with r274819? asr_timeout() not found

Fixed, sorry forgot asr wasn't in GENERIC, so missed it in testing. On 22/11/2014 14:34, David Wolfskill wrote: Running: FreeBSD g1-253.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1434 r274790M/274790:1100047: Fri Nov 21 06:07:24 PST 2014 r...@g1-253.catwhisker.org:/common/S4/obj/us

Re: How much memory do I need for buildworld?

On 22 Nov 2014, at 16:51, Rostislav Krasny wrote: > I've a fresh FreeBSD 10.1 installed on an old 32-bit machine. I've > checked out revision 274850 of the base sources and ran 'make > buildworld'. After some time it has failed: > > ===> lib/clang/libllvmx86disassembler (depend) > tblgen -gen-dis

How much memory do I need for buildworld?

Hi, I've a fresh FreeBSD 10.1 installed on an old 32-bit machine. I've checked out revision 274850 of the base sources and ran 'make buildworld'. After some time it has failed: ===> lib/clang/libllvmx86disassembler (depend) tblgen -gen-disassembler -I /usr/src/lib/clang/libllvmx86disassembler/..

Jenkins build is back to stable : FreeBSD_HEAD-tests2 #294

See ___ 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"

Problem with r274819? asr_timeout() not found

Running: FreeBSD g1-253.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1434 r274790M/274790:1100047: Fri Nov 21 06:07:24 PST 2014 r...@g1-253.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i386 Updated sources to r274845; "make buildworld" is OK, but "make buildkernel": ... >>> stag

Starting intel driver fails on boot

Hello. A few months ago I sent an e-mail to this mailing list and reported about problems related to starting X on FreeBSD when using EFI mode. I "fixed" that problem by using the "scfb" driver from ports. Today I, using "Xorg -configure", was playing around with the intel driver, since my M

Jenkins build became unstable: FreeBSD_HEAD-tests2 #293

See ___ 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"

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

See ___ 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"