Build failed in Jenkins: FreeBSD_HEAD-tests2 #158

See -- Started by build flow Build_Image_and_Run_Tests_in_Bhyve_HEAD#153 Building remotely on havoc.ysv.freebsd.org (FreeBSD-10) in workspace

Re: VT: NOT giving extended console

On 31.10.2014 04:16, Larry Rosenman wrote: > Copyright (c) 1992-2014 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundatio

Re: VT: NOT giving extended console

On Fri, 31 Oct 2014 11:35:00 +0100 Jean-Sébastien Pédron wrote: > On 31.10.2014 04:16, Larry Rosenman wrote: >> Copyright (c) 1992-2014 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> The Regents of the University of California. All rights

Re: VT: NOT giving extended console

On 31.10.2014 11:46, Tijl Coosemans wrote: >> Hmm, sys/dev/drm2/ttm/ttm_agp_backend.c isn't connected to the build of >> the drm2 module. >> >> I'll connect it as soon as svn up is finished, except if Tijl beats me >> to it :) > > Done in r273902. Thanks :) And thank you very much for adding AGP

Build failed in Jenkins: FreeBSD_HEAD-tests2 #159

See -- Started by build flow Build_Image_and_Run_Tests_in_Bhyve_HEAD#154 Building remotely on havoc.ysv.freebsd.org (FreeBSD-10) in workspace

Re: VT: NOT giving extended console

On Fri, Oct 31, 2014 at 11:48:03AM +0100, Jean-S?bastien P?dron wrote: > On 31.10.2014 11:46, Tijl Coosemans wrote: > >> Hmm, sys/dev/drm2/ttm/ttm_agp_backend.c isn't connected to the build of > >> the drm2 module. > >> > >> I'll connect it as soon as svn up is finished, except if Tijl beats me > >

Unclean shutdown for r273852 -> r273899 transition

I thought it a bit odd when I rebooted after the "make installworld" completed and found that fsck(8) was checking teh file systems on my laptop. When it also happened for my build machine, I suspected it might not merely be a one-off oddity... and I was able to make use of the serial console on t

Build failed in Jenkins: FreeBSD_HEAD-tests2 #160

See -- Started by build flow Build_Image_and_Run_Tests_in_Bhyve_HEAD#155 Building remotely on havoc.ysv.freebsd.org (FreeBSD-10) in workspace

Re: VT: NOT giving extended console

On 31.10.2014 12:59, Larry Rosenman wrote: > Thanks, now I get a constant stream of: > > kernel: error: [drm:pid0:drm_do_get_edid] *ERROR* DVI-I-1: EDID block 0 > invalid. > kernel: error: [drm:pid0:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor > but no|invalid EDID Yeah, the driver repr

Jenkins build is unstable: FreeBSD_HEAD-tests2 #161

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"

Re: Jenkins build is unstable: FreeBSD_HEAD-tests2 #161

> On Oct 31, 2014, at 10:04, jenkins-ad...@freebsd.org wrote: > > See Hi Craig, I have a potential fix for this on my github branch (I ATFified the testcase and fixed some broken assumptions; I'll find the PR later). Now tha

NVidia Tesla K40

Hello! I want to use NVidia Tesla K40 GPU for parallel computing.Does FreeBSD support such a hardware? Thanks a lot! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "

Re: NVidia Tesla K40

Am Fri, 31 Oct 2014 16:46:15 + (UTC) John Dison schrieb: > Hello! > I want to use NVidia Tesla K40 GPU for parallel computing.Does FreeBSD > support such a > hardware? Thanks a lot! > ___ > freebsd-current@freebsd.org mailing list > http://lists.fr

r273910 build failure if is out-of-date

Hi! I have the following error when building HEAD: ---8<--- cc -O2 -pipe -I/mnt/home/dumbbell/Projects/freebsd/src/SVN/head/lib/libc/include -I/mnt/home/dumbbell/Projects/freebsd/src/SVN/head/lib/libc/../../include -I/mnt/home/dumbbell/Projects/freebsd/src/SVN/head/lib/libc/sparc64 -DNLS -fexc

CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

On all CURRENT systems I updated today (31.10.2014) I had massive filesystem corruption after reboot. The systems do have FreeBSD 11.0-CURRENT #1 r273914: Fri Oct 31 19:40:04 CET 2014 amd64 and suffer without exception from the same breakage, quitting services and/or reporting corrupted files

Re: VT: NOT giving extended console

On 2014-10-31 11:58, Jean-Sébastien Pédron wrote: On 31.10.2014 12:59, Larry Rosenman wrote: Thanks, now I get a constant stream of: kernel: error: [drm:pid0:drm_do_get_edid] *ERROR* DVI-I-1: EDID block 0 invalid. kernel: error: [drm:pid0:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor b

Re: Unclean shutdown for r273852 -> r273899 transition

Am Fri, 31 Oct 2014 06:59:12 -0700 David Wolfskill schrieb: > I thought it a bit odd when I rebooted after the "make installworld" > completed and found that fsck(8) was checking teh file systems on my > laptop. > > When it also happened for my build machine, I suspected it might not > merely be

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

At 12:20 PM 10/31/2014, O. Hartmann wrote: >On all CURRENT systems I updated today (31.10.2014) I had massive filesystem >corruption >after reboot. The systems do have > >FreeBSD 11.0-CURRENT #1 r273914: Fri Oct 31 19:40:04 CET 2014 amd64 > >and suffer without exception from the same breakage, q

r273918 buildworld broke at semaphore

First breakage in a long time. Error is: In file included from cancelpoints_sem_new.c:47: /usr/src/lib/libc/../../include/semaphore.h:41:16: error: field has incomplete type 'struct _usem2' struct _usem2 _kern; ^ /usr/src/lib/libc/../../include/semaphore.h:41:9: n

Jenkins build is still unstable: FreeBSD_HEAD-tests2 #162

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"

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

Le 31.10.2014 21:35, Martin MATO a écrit : > Le 31.10.2014 21:00, Manfred Antar a écrit : >> At 12:20 PM 10/31/2014, O. Hartmann wrote: >> >>> On all CURRENT systems I updated today (31.10.2014) I had massive >>> filesystem corruption >>> after reboot. The systems do have >>> >>> FreeBSD 11.0-CU

Re: r273910 build failure if is out-of-date

Hi dumbbell@! On Oct 31, 2014, at 11:55, Jean-Sébastien Pédron wrote: > Hi! > > I have the following error when building HEAD: … > The problem is that the installed version of is > out-of-date compared to the version in the source tree. I guess it's > supposed to pick the version in the sour

Re: r273910 build failure if is out-of-date

Hello > Beeblebrox should confirm whether or not he’s using gcc in the build > or clang. Thanks! Using clang I have some tighter settings in src.conf, but nothing clang/gcc related. -- FreeBSD_amd64_11-Current_RadeonKMS ___ freebsd-current@freebsd.org

Re: r273910 build failure if is out-of-date

On Oct 31, 2014, at 14:00, Beeblebrox wrote: > Hello > >> Beeblebrox should confirm whether or not he’s using gcc in the build >> or clang. Thanks! > > Using clang > I have some tighter settings in src.conf, but nothing clang/gcc related. Hi! Do you have WITHOUT_CLANG_BOOTSTRAP set? Th

Re: r273910 build failure if is out-of-date

> Hi! > Do you have WITHOUT_CLANG_BOOTSTRAP set? > Thanks! No. No clang/gcc settings. All src.conf WITHOUT entries are of the sort INET6, PORTSNAP, BLUETOOTH, etc I DO use ccache -- FreeBSD_amd64_11-Current_RadeonKMS ___ freebsd-current@freebsd

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

Can you all please tell me which revision(s) you were running before you upgraded? Something like "bzgrep 11.0-CURRENT /var/log/messages*" should do the trick. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-current@freebsd.org mailing list http:/

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

On 31.10.14 22:23, Dag-Erling Smørgrav wrote: Can you all please tell me which revision(s) you were running before you upgraded? Something like "bzgrep 11.0-CURRENT /var/log/messages*" should do the trick. +1 here. 'Corrupted' /usr. Changed entry in fstab to not check fs. [zrhws131:/boot/kern

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

Le 31/10/2014 22:23, Dag-Erling Smørgrav a écrit : Can you all please tell me which revision(s) you were running before you upgraded? Something like "bzgrep 11.0-CURRENT /var/log/messages*" should do the trick. DES Absolutely here it is /var/log/messages:Oct 31 12:11:05 kernel: FreeBSD 11.0-

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

At 02:44 PM 10/31/2014, Andreas Tobler wrote: >On 31.10.14 22:23, Dag-Erling Smørgrav wrote: >>Can you all please tell me which revision(s) you were running before you >>upgraded? Something like "bzgrep 11.0-CURRENT /var/log/messages*" >>should do the trick. > >+1 here. 'Corrupted' /usr. Changed

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

Le 31/10/2014 22:50, Martin MATO a écrit : Le 31/10/2014 22:23, Dag-Erling Smørgrav a écrit : Can you all please tell me which revision(s) you were running before you upgraded? Something like "bzgrep 11.0-CURRENT /var/log/messages*" should do the trick. DES Absolutely here it is /var/log/mes

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The problem should have been corrected by r273919. Please update your system and update /etc/ with mergemaster. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE-

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

Am Fri, 31 Oct 2014 22:23:28 +0100 Dag-Erling Smørgrav schrieb: > Can you all please tell me which revision(s) you were running before you > upgraded? Something like "bzgrep 11.0-CURRENT /var/log/messages*" > should do the trick. > > DES r273800 was the last (obviously) working on one box, r273

Jenkins build is still unstable: FreeBSD_HEAD-tests2 #163

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"

Re: Jenkins build is unstable: FreeBSD_HEAD-tests2 #161

On Oct 31, 2014, at 10:12, Garrett Cooper wrote: >> On Oct 31, 2014, at 10:04, jenkins-ad...@freebsd.org wrote: >> >> See > > Hi Craig, >I have a potential fix for this on my github branch (I ATFified the > testcase and fix

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

On Oct 31, 2014, at 15:35, Martin MATO wrote: > Le 31/10/2014 22:50, Martin MATO a écrit : >> Le 31/10/2014 22:23, Dag-Erling Smørgrav a écrit : >>> Can you all please tell me which revision(s) you were running before you >>> upgraded? Something like "bzgrep 11.0-CURRENT /var/log/messages*" >>>

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

Le 31/10/2014 23:35, Martin MATO a écrit : Le 31/10/2014 22:50, Martin MATO a écrit : Le 31/10/2014 22:23, Dag-Erling Smørgrav a écrit : Can you all please tell me which revision(s) you were running before you upgraded? Something like "bzgrep 11.0-CURRENT /var/log/messages*" should do the tri

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

"O. Hartmann" writes: > r273800 was the last (obviously) working on one box, r273872 seems to > have the problem: Are you sure? If I understand Manfred correctly, r273905 was running fine for him. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

Manfred Antar writes: > Then for some reason /var started to being mounted mfs. > so for me i think it has something to do with the new rc.d startup files. > If I have varmfs="NO" and cleanvar_enable="NO" everything works fine. Not really. The default for varmfs is AUTO, which mounts a memory f

Re: Jenkins build is unstable: FreeBSD_HEAD-tests2 #161

On Fri, Oct 31, 2014 at 10:04 AM, wrote: > See > > Mateusz, Can you take a look at: https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/ The last successful pass was GRN r273871. I'm not sure, but you made a bunch of co

Re: Jenkins build is unstable: FreeBSD_HEAD-tests2 #161

On Fri, Oct 31, 2014 at 06:52:43PM -0700, Craig Rodrigues wrote: > On Fri, Oct 31, 2014 at 10:04 AM, wrote: > > > See > > > > > Mateusz, > > Can you take a look at: > https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/ >

Re: Jenkins build is unstable: FreeBSD_HEAD-tests2 #161

On Oct 31, 2014, at 19:00, Mateusz Guzik wrote: > On Fri, Oct 31, 2014 at 06:52:43PM -0700, Craig Rodrigues wrote: >> On Fri, Oct 31, 2014 at 10:04 AM, wrote: >> >>> See >>> >>> >> Mateusz, >> >> Can you take a look at: >> ht

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

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"

Re: Jenkins build is unstable: FreeBSD_HEAD-tests2 #161

On Oct 31, 2014 7:01 PM, "Mateusz Guzik" wrote: > > There was a regression after commits related to new random code which > resulted in /dev/md0 being created and mounted to /var. > > Looks like the test in question assumes it always gets /dev/md0. > > The test works for me not what the regression

Re: CURRENT: WARNING! r273914 leaves filesystems in inconsistent/corrupted condition!

On Sat, 01 Nov 2014 01:33:09 +0100 Dag-Erling Sm〓rgrav wrote: > Manfred Antar writes: > > Then for some reason /var started to being mounted mfs. > > so for me i think it has something to do with the new rc.d startup files. > > If I have varmfs="NO" and cleanvar_enable="NO" everything works fin