buildworld fails with clang
Hello, 9-STABLE fails to build with clang and *without* "NO_WERROR=" and "WERROR=" in /etc/make.conf. It used to work not long before : FreeBSD zozo.afpicl.lan 9.0-STABLE FreeBSD 9.0-STABLE #0 r237222M: Mon Jun 18 10:18:54 CEST 2012 r...@zozo.afpicl.lan:/usr/obj/usr/src/sys/CORE amd64 # svnversion 238067M # make NOCLEAN=yes NO_CLEAN=yes buildworld [...] ===> cddl/lib (obj,depend,all,install) ===> cddl/lib/drti (obj) ===> cddl/lib/libavl (obj) ===> cddl/lib/libctf (obj) ===> cddl/lib/libdtrace (obj) ===> cddl/lib/libnvpair (obj) ===> cddl/lib/libumem (obj) ===> cddl/lib/libuutil (obj) ===> cddl/lib/libzfs (obj) ===> cddl/lib/libzpool (obj) ===> cddl/lib/drti (depend) ===> cddl/lib/libavl (depend) ===> cddl/lib/libctf (depend) ===> cddl/lib/libdtrace (depend) ===> cddl/lib/libnvpair (depend) ===> cddl/lib/libumem (depend) ===> cddl/lib/libuutil (depend) ===> cddl/lib/libzfs (depend) ===> cddl/lib/libzpool (depend) ===> cddl/lib/drti (all) ===> cddl/lib/libavl (all) ===> cddl/lib/libctf (all) ===> cddl/lib/libdtrace (all) clang -O2 -pipe -march=corei7 -fomit-frame-pointer -I/usr/obj/usr/src/cddl/lib/libdtrace -I/usr/src/cddl/lib/libdtrace -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/dev/dtrace/amd64 -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris -I/usr/src/cddl/lib/libdtrace/../../../cddl/compat/opensolaris/include -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/head -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libctf/common -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/contrib/opensolaris/uts/common -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/contrib/opensolaris/uts/intel -DDIS_MEM -DNEED_SOLARIS_BOOLEAN -std=gnu89 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-parentheses -Wno-unknown-pragmas -c /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume.c -o dt_consume.o /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume.c:799:40: error: format specifies type 'long long' but the argument has type 'int64_t' (aka 'long') [-Werror,-Wformat] (void) snprintf(c, sizeof (c), ">= %lld", value); ~~~^ ~ %ld 1 error generated. *** [dt_consume.o] Error code 1 Stop in /usr/src/cddl/lib/libdtrace. *** [all] Error code 1 I used NOCLEAN and NO_CLEAN to see the error because I was compiling with -j8 before, but yes, my /usr/obj/ was clean at the time I attempted to buildworld. This may be the culprit ? # svn log -l 1 /usr/src/cddl/contrib/opensolaris/lib/libdtrace/ r237870 | pfg | 2012-07-01 06:15:14 +0200 (dim 01 jul 2012) | 8 lignes MFC r237624, r237714, r237716, r237860: Bring llquantize support into Dtrace. Bryan Cantrill implemented the equivalent of semi-log graph paper for Dtrace so llquantize will use one logarithmic and one linear scale. -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email & vCards X www: http://www.gid0.org- against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: buildworld fails with clang
On 2012-07-03 14:23, Olivier Smedts wrote: > 9-STABLE fails to build with clang and *without* "NO_WERROR=" and > "WERROR=" in /etc/make.conf. It used to work not long before : ... > /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume.c:799:40: > error: format specifies type 'long long' but the > argument has type 'int64_t' (aka 'long') [-Werror,-Wformat] > (void) snprintf(c, sizeof (c), ">= %lld", value); >~~~^ ~ >%ld ... > This may be the culprit ? > > # svn log -l 1 /usr/src/cddl/contrib/opensolaris/lib/libdtrace/ > > r237870 | pfg | 2012-07-01 06:15:14 +0200 (dim 01 jul 2012) | 8 lignes > > MFC r237624, r237714, r237716, r237860: Yep, that is the culprit. Unfortunately I didn't quite follow the commit rush before code freeze, and this problem was introduced. I've committed a fix to head (r238071), but it may take some time to MFC to stable/9, since we've just entered code freeze. Meanwhile, you can apply this patch: http://svnweb.freebsd.org/base/head/cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume.c?view=patch&r1=238071&r2=238070&pathrev=238071 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: buildworld fails with clang
2012/7/3 Dimitry Andric : > Yep, that is the culprit. Unfortunately I didn't quite follow the > commit rush before code freeze, and this problem was introduced. > > I've committed a fix to head (r238071), but it may take some time to MFC > to stable/9, since we've just entered code freeze. > > Meanwhile, you can apply this patch: > > http://svnweb.freebsd.org/base/head/cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume.c?view=patch&r1=238071&r2=238070&pathrev=238071 Thanks for the reply and the fix ! Just to be clear, it may take some time to MFC, but will it be done for releng/9.1 so that 9.1-RELEASE users can simply buildworld with clang ? Cheers -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email & vCards X www: http://www.gid0.org- against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: buildworld fails with clang
On 2012-07-03 14:54, Olivier Smedts wrote:> 2012/7/3 Dimitry Andric : ... >> I've committed a fix to head (r238071), but it may take some time to MFC >> to stable/9, since we've just entered code freeze. ... > Just to be clear, it may take some time to MFC, but will it be done > for releng/9.1 so that 9.1-RELEASE users can simply buildworld with > clang ? That is up to re@, they ultimately decide if something goes into the frozen branch. As this fix is trivial, I don't see why they would disapprove, though. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
bge problems in RELENG_9, bge0: watchdog timeout -- resetting
Hi, I'm having lots of difficulties with BCM5719, which is the default network card of HP Proliant DL 360 G8 servers. I can get a few ping replies before I get a couple of these: bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting Then everything hangs. Can not log in using ssh. I'm running: FreeBSD-9.0-RELENG_9-20120701-JPSNAP-amd64 Info about the NIC: # devinfo -rv | grep phy brgphy0 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=1 brgphy1 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=2 brgphy2 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=3 brgphy3 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=4 # grep bge /var/run/dmesg.boot bge0: mem 0xf6bf-0xf6bf, 0xf6be-0xf6be,0xf6bd-0xf6bd irq 32 at device 0.0 on pci3 bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E miibus0: on bge0 bge0: Ethernet address: 2c:76:8a:54:08:14 bge1: mem 0xf6bc-0xf6bc, 0xf6bb-0xf6bb,0xf6ba-0xf6ba irq 36 at device 0.1 on pci3 bge1: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E miibus1: on bge1 bge1: Ethernet address: 2c:76:8a:54:08:15 bge2: mem 0xf6b9-0xf6b9, 0xf6b8-0xf6b8,0xf6b7-0xf6b7 irq 32 at device 0.2 on pci3 bge2: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E miibus2: on bge2 bge2: Ethernet address: 2c:76:8a:54:08:16 bge3: mem 0xf6b6-0xf6b6, 0xf6b5-0xf6b5,0xf6b4-0xf6b4 irq 36 at device 0.3 on pci3 bge3: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E miibus3: on bge3 bge3: Ethernet address: 2c:76:8a:54:08:17 Searching other bug reports and posts, I've tried: hw.bge.allow_asf="0" hw.pci.enable_msi="0" But it didn't help. Any ideas? If I don't use the loader.conf settings above, I also get (before the watchdog timeouts): bge0: 2 link states coalesced bge0: 2 link states coalesced bge0: 2 link states coalesced Best regards, -- Anders. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: bge problems in RELENG_9, bge0: watchdog timeout -- resetting
Hi Anders I've not had good luck with the BCM5719 in stable/8 either. Not sure if the driver has been updated in 9 or not, but I have a blog post explaining my woes with the BCM5719 at http://blog.hostileadmin.com/ On 7/3/12, Anders Nordby wrote: > Hi, > > I'm having lots of difficulties with BCM5719, which is the default > network card of HP Proliant DL 360 G8 servers. I can get a few ping > replies before I get a couple of these: > > bge0: watchdog timeout -- resetting > > bge0: watchdog timeout -- resetting > > > Then everything hangs. Can not log in using ssh. > > I'm running: FreeBSD-9.0-RELENG_9-20120701-JPSNAP-amd64 > > Info about the NIC: > > # devinfo -rv | grep phy > brgphy0 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=1 > > brgphy1 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=2 > > brgphy2 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=3 > > brgphy3 pnpinfo oui=0x1be9 model=0x22 rev=0x0 at phyno=4 > > # grep bge /var/run/dmesg.boot > bge0: mem > 0xf6bf-0xf6bf, > 0xf6be-0xf6be,0xf6bd-0xf6bd irq 32 at device 0.0 on pci3 > > bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E > > miibus0: on bge0 > > bge0: Ethernet address: 2c:76:8a:54:08:14 > > bge1: mem > 0xf6bc-0xf6bc, > 0xf6bb-0xf6bb,0xf6ba-0xf6ba irq 36 at device 0.1 on pci3 > > bge1: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E > > miibus1: on bge1 > > bge1: Ethernet address: 2c:76:8a:54:08:15 > > bge2: mem > 0xf6b9-0xf6b9, > 0xf6b8-0xf6b8,0xf6b7-0xf6b7 irq 32 at device 0.2 on pci3 > > bge2: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E > > miibus2: on bge2 > > bge2: Ethernet address: 2c:76:8a:54:08:16 > > bge3: mem > 0xf6b6-0xf6b6, > 0xf6b5-0xf6b5,0xf6b4-0xf6b4 irq 36 at device 0.3 on pci3 > > bge3: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E > > miibus3: on bge3 > > bge3: Ethernet address: 2c:76:8a:54:08:17 > > > Searching other bug reports and posts, I've tried: > > hw.bge.allow_asf="0" > > hw.pci.enable_msi="0" > > > But it didn't help. Any ideas? > > If I don't use the loader.conf settings above, I also get (before the > watchdog timeouts): > > bge0: 2 link states coalesced > > bge0: 2 link states coalesced > > bge0: 2 link states coalesced > > > Best regards, > > -- > Anders. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Sent from my mobile device Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
9.0-STABLE: Can't umount umass device
uname -a: FreeBSD wonderland.m5p.com 9.0-STABLE FreeBSD 9.0-STABLE #9: Sun Jun 3 10:01:09 EDT 2012 geo...@wonderland.m5p.com:/usr/obj/usr/src/sys/WONDERLAND amd64 dmesg | grep umass: umass0: on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x4000 umass0:3:0:-1: Attached to scbus3 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI status: Check Condition (probe0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 # mount -t msdosfs /dev/da0s1 /flash # umount /flash umount: unmount of /flash failed: Device busy -- George Mitchell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.0-STABLE: Can't umount umass device
fstat /flash ? On Tue, Jul 03, 2012 at 08:42:55PM -0400, George Mitchell wrote: > uname -a: > FreeBSD wonderland.m5p.com 9.0-STABLE FreeBSD 9.0-STABLE #9: Sun Jun 3 > 10:01:09 EDT 2012 > geo...@wonderland.m5p.com:/usr/obj/usr/src/sys/WONDERLAND amd64 > > dmesg | grep umass: > umass0: on usbus2 > umass0: SCSI over Bulk-Only; quirks = 0x4000 > umass0:3:0:-1: Attached to scbus3 > (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error > (probe0:umass-sim0:0:0:0): SCSI status: Check Condition > (probe0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not > ready to ready change, medium may have changed) > da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 > > # mount -t msdosfs /dev/da0s1 /flash > # umount /flash > umount: unmount of /flash failed: Device busy > > -- George Mitchell > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- - (2^(N-1)) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.0-STABLE: Can't umount umass device
On Tue, 2012-07-03 at 20:42 -0400, George Mitchell wrote: > uname -a: > FreeBSD wonderland.m5p.com 9.0-STABLE FreeBSD 9.0-STABLE #9: Sun Jun 3 > 10:01:09 EDT 2012 > geo...@wonderland.m5p.com:/usr/obj/usr/src/sys/WONDERLAND amd64 > > dmesg | grep umass: > umass0: on usbus2 > umass0: SCSI over Bulk-Only; quirks = 0x4000 > umass0:3:0:-1: Attached to scbus3 > (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error > (probe0:umass-sim0:0:0:0): SCSI status: Check Condition > (probe0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not > ready to ready change, medium may have changed) > da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 > > # mount -t msdosfs /dev/da0s1 /flash > # umount /flash > umount: unmount of /flash failed: Device busy > > -- George Mitchell Are you running a desktop environment that automatically launches gam_server to watch for changes on mounted filesystems? If so, the fix is to edit /usr/local/etc/gamin/gaminrc and tell it to use polling rather than kernel notification on the mount points you use for removable media. -- Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
