Re: Huge hpet0 interrupt storm, but only if HGST HTS721010A9E630 HDD is present at the boot _and_ formatted with recognized fs (??)
I've overwrote the disk with zeroes- storms ceased. But as soon as you gpart create mbr/gpt scheme it starts. It has nothing to do with fs. -- View this message in context: http://freebsd.1045724.x6.nabble.com/Huge-hpet0-interrupt-storm-but-only-if-HGST-HTS721010A9E630-HDD-is-present-at-the-boot-and-formatted-tp6151041p6152025.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Should 4K AF disk with FAT32 (newfs_msdos -F32 -S 4096) be unmountable?
Hello, FreeBSD 11.0-STABLE #0 r309991 here, if I use -S 4096 the mount_msdosfs complains about "mount_msdosfs: /dev/ada1s1: Invalid argument". Is this expected? See example: $ sudo newfs_msdos -F32 -S 4096 /dev/ada1s1 Password: newfs_msdos: trim 3 sectors to adjust to a multiple of 63 /dev/ada1s1: 244182720 sectors in 3815355 FAT32 clusters (262144 bytes/cluster) BytesPerSec=4096 SecPerClust=64 ResSectors=4 FATs=2 Media=0xf0 SecPerTrack=63 Heads=16 HiddenSecs=0 HugeSectors=244190205 FATsecs=3726 RootCluster=2 FSInfo=1 Backup=2 $ sudo mount_msdosfs -o large /dev/ada1s1 /mnt/ Password: $ sudo mount_msdosfs: /dev/ada1s1: Invalid argument $ sudo newfs_msdos -F32 /dev/ada1s1 Password: newfs_msdos: trim 24 sectors to adjust to a multiple of 63 /dev/ada1s1: 1953044736 sectors in 30516324 FAT32 clusters (32768 bytes/cluster) BytesPerSec=512 SecPerClust=64 ResSectors=32 FATs=2 Media=0xf0 SecPerTrack=63 Heads=16 HiddenSecs=0 HugeSectors=1953521640 FATsecs=238409 RootCluster=2 FSInfo=1 Backup=2 $ sudo mount_msdosfs -o large /dev/ada1s1 /mnt/ Password: $ etc... -- View this message in context: http://freebsd.1045724.x6.nabble.com/Should-4K-AF-disk-with-FAT32-newfs-msdos-F32-S-4096-be-unmountable-tp6152018.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD_STABLE_10-i386 - Build #1548 - Fixed
FreeBSD_STABLE_10-i386 - Build #1548 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/1548/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/1548/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/1548/console Change summaries: 310082 by dim: Merge r309860 from stable/9, as this also applies to stable/10: Fix libllvmanalysis build failure after r309857: on stable/9, llvm is compiled by gcc, and without -std=c++11, so the nullptr keyword is unknown. Use the old-school plain zero syntax instead. 310081 by avg: MFC r277511: Fix remote DMA based firewire debugging when targeting systems with more than 4GB of physical memory. 310080 by avg: MFC r309119: virtio_pci: fix announcement of MSI-X interrupts for queues 310078 by avg: MFC r309093: firewire: initialize tag label to -1 in fw_xfer_alloc() 310076 by avg: MFC r308529: intpm: clean up intsmb_bread and intsmb_pcall ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: broken source upgrade 9.3-STABLE to 10.3-STABLE
On 14 Dec 2016, at 10:14, Eugene Grosbein wrote: > > On 14.12.2016 16:07, Kurt Jaeger wrote: >> Hi! >> >>> I've got legacy FreeBSD server running 8.4-STABLE and I'm trying to upgrade >>> it. >>> Source upgrade for 8.4 to 9.3-STABLE r310015 went flawlessly. >>> After reboot, I checked out stable/10 r310043 sources and ran buildworld >>> again. >>> It fails: >> >> I suggest two different approaches (have not tried that, but...) >> >> 1) sidegrade (with build-from-source) to 9.3-RELEASE, then use >> freebsd-update to 10.x >> >> 2) don't upgrade to 10-STABLE, but surce-upgrade to 10.0 or 10.1-RELEASE >> > > I've manually applied single-line change r309860 to stable/10 tree > and that fixed the problem, now build continues. Hi Eugene, This was a mistake on my part, sorry about that. Obviously, the version of clang in 10.x should support compiling with gcc 4.2.1, since that is the easiest way of upgrading from previous releases. I applied the same fix to stable/10 in r310082. -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: FreeBSD_STABLE_10-i386 - Build #1547 - Failure
On 14/12/2016 19:04, jenkins-ad...@freebsd.org wrote: > --- fwohci.o --- > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc > -DHAVE_KERNEL_OPTION_HEADERS -include > /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -fno-common > -g -I/usr/obj/usr/src/sys/GENERIC -mno-aes -mno-avx -mno-mmx -mno-sse > -msoft-float -ffreestanding -fstack-protector -gdwarf-2 -std=iso9899:1999 > -Qunused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs > -fdiagnostics-show-option -Wno-error-tautological-compare > -Wno-error-empty-body > -Wno-error-parentheses-equality -Wno-error-unused-function -c > /usr/src/sys/modules/firewire/firewire/../../../dev/firewire/fwohci.c -o > fwohci.o > --- all_subdir_drm2 --- > --- radeon_ttm.o --- > ctfconvert -L VERSION -g radeon_ttm.o > --- all_subdir_firmware --- > ctfconvert -L VERSION -g subr_firmware.o > --- all_subdir_firewire --- > /usr/src/sys/modules/firewire/firewire/../../../dev/firewire/fwohci.c:1878:9: > error: use of undeclared identifier 'prequpper' > (prequpper & 0x)) { Sorry about this, should be fixed by r310081. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD_STABLE_10-i386 - Build #1547 - Failure
FreeBSD_STABLE_10-i386 - Build #1547 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/1547/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/1547/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/1547/console Change summaries: 310074 by avg: MFC r309092: fwohci: report whether PhysicalUpperBound register is implemented 310071 by avg: MFC r306589: Implement iicbus_write_ivar and impelemnt the NOSTOP ivar in both read and write. 310069 by avg: MFC r308985: revert r304520, set canmount=on is not supposed to mount the filesystem 310067 by avg: MFC r308887,309090: fix unsafe modification of zfs_vnodeops when DIAGNOSTIC is enabled 310063 by avg: MFC r308480: pmc_process_csw_out: ignore deleted counters 310062 by avg: make smbus_get_addr() an ivar accessor This is a direct commit to this branch. smbus_get_addr() was declared as a funciton prototype, but the function was never defined. read_ivar and write_ivar methods were unused. This was exposed after jedec_ts driver was imported to this branch as that driver turned out to be the first user of smbus_get_addr(). This change is a small subset of a larger change in r281985. Reported by:jhb Pointyhat to: avg 310060 by des: MFH (r308996, r309051, r309738): refactor, avoid repeating DNS requests The end of the build log: [...truncated 170633 lines...] cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -fno-common -g -I/usr/obj/usr/src/sys/GENERIC -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -gdwarf-2 -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function-c /usr/src/sys/modules/fdc/../../dev/fdc/fdc_acpi.c -o fdc_acpi.o --- all_subdir_ext2fs --- ctfconvert -L VERSION -g ext2_vnops.o --- all_subdir_drm2 --- --- radeon_pm.o --- ctfconvert -L VERSION -g radeon_pm.o --- all_subdir_ext2fs --- --- ext2fs.kld --- ld -d -warn-common -r -d -o ext2fs.kld ext2_alloc.o ext2_balloc.o ext2_bmap.o ext2_extents.o ext2_hash.o ext2_htree.o ext2_inode.o ext2_inode_cnv.o ext2_lookup.o ext2_subr.o ext2_vfsops.o ext2_vnops.o ctfmerge -L VERSION -g -o ext2fs.kld ext2_alloc.o ext2_balloc.o ext2_bmap.o ext2_extents.o ext2_hash.o ext2_htree.o ext2_inode.o ext2_inode_cnv.o ext2_lookup.o ext2_subr.o ext2_vfsops.o ext2_vnops.o --- all_subdir_fdescfs --- ===> fdescfs (all) --- all_subdir_fdc --- ctfconvert -L VERSION -g fdc_acpi.o --- fdc.kld --- ld -d -warn-common -r -d -o fdc.kld fdc.o fdc_isa.o fdc_pccard.o fdc_acpi.o ctfmerge -L VERSION -g -o fdc.kld fdc.o fdc_isa.o fdc_pccard.o fdc_acpi.o --- all_subdir_fdescfs --- --- fdesc_vfsops.o --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -fno-common -g -I/usr/obj/usr/src/sys/GENERIC -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -gdwarf-2 -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function-c /usr/src/sys/modules/fdescfs/../../fs/fdescfs/fdesc_vfsops.c -o fdesc_vfsops.o --- all_subdir_fdc --- :> export_syms awk -f /usr/src/sys/conf/kmod_syms.awk fdc.kld export_syms | xargs -J% objcopy % fdc.kld --- fdc.ko.debug --- ld -Bshareable -d -warn-common -o fdc.ko.debug fdc.kld --- fdc.ko.symbols --- objcopy --only-keep-debug fdc.ko.debug fdc.ko.symbols --- fdc.ko --- objcopy --strip-debug --add-gnu-debuglink=fdc.ko.symbols fdc.ko.debug fdc.ko --- all_subdir_drm2 --- --- radeon_sa.o --- cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -fno-common -g -I/usr/obj/usr/src/sys/GENERIC -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -gdwarf-2 -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare
suspend/resume on Skylake (Lenovo T460s) with FreeBSD11 stable
Hi everybody! i have been hardly trying to get my Lenovo T460s to suspend *and to resume again*. Eventually the system suspends when i close the lid. The power LED is slowly blinking on and off. That is it! I am not able to resume my system anymore. When I push the power button once the power LED *keeps* slowly blinking on and off. :( Has anyone of you been able to setup suspend/resume with a notebook equipped with current Intel chipset? on FreeBSD 11.0-STABLE or on FreeBSD 12.0-CURRENT? Any hints or help is highly appreciated. Below you'll find my pciconf -lv if needed i am happy to hand in dmesg aswell. best regards Chris -- snipp -- root@fb:~ # pciconf -lv hostb0@pci0:0:0:0:class=0x06 card=0x223317aa chip=0x19048086 rev=0x08 hdr=0x00 vendor = 'Intel Corporation' device = 'Skylake Host Bridge/DRAM Registers' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0:class=0x03 card=0x223317aa chip=0x19168086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' device = 'HD Graphics 520' class = display subclass = VGA none0@pci0:0:8:0:class=0x088000 card=0x223317aa chip=0x19118086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Skylake Gaussian Mixture Model' class = base peripheral xhci0@pci0:0:20:0:class=0x0c0330 card=0x223317aa chip=0x9d2f8086 rev=0x21 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-LP USB 3.0 xHCI Controller' class = serial bus subclass = USB none1@pci0:0:20:2:class=0x118000 card=0x223317aa chip=0x9d318086 rev=0x21 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-LP Thermal subsystem' class = dasp none2@pci0:0:22:0:class=0x078000 card=0x223317aa chip=0x9d3a8086 rev=0x21 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-LP CSME HECI' class = simple comms none3@pci0:0:22:3:class=0x070002 card=0x223317aa chip=0x9d3d8086 rev=0x21 hdr=0x00 vendor = 'Intel Corporation' class = simple comms subclass = UART pcib1@pci0:0:28:0:class=0x060400 card=0x223317aa chip=0x9d108086 rev=0xf1 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib2@pci0:0:28:2:class=0x060400 card=0x223317aa chip=0x9d128086 rev=0xf1 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib3@pci0:0:28:4:class=0x060400 card=0x223317aa chip=0x9d148086 rev=0xf1 hdr=0x01 vendor = 'Intel Corporation' device = 'Sunrise Point-LP PCI Express Root Port' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0:class=0x060100 card=0x223317aa chip=0x9d488086 rev=0x21 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-LP LPC Controller' class = bridge subclass = PCI-ISA none4@pci0:0:31:2:class=0x058000 card=0x223317aa chip=0x9d218086 rev=0x21 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-LP PMC' class = memory hdac0@pci0:0:31:3:class=0x040300 card=0x223317aa chip=0x9d708086 rev=0x21 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-LP HD Audio' class = multimedia subclass = HDA none5@pci0:0:31:4:class=0x0c0500 card=0x223317aa chip=0x9d238086 rev=0x21 hdr=0x00 vendor = 'Intel Corporation' device = 'Sunrise Point-LP SMBus' class = serial bus subclass = SMBus em0@pci0:0:31:6:class=0x02 card=0x223317aa chip=0x156f8086 rev=0x21 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Connection I219-LM' class = network subclass = ethernet none6@pci0:2:0:0:class=0xff card=0x223317aa chip=0x522a10ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTS522A PCI Express Card Reader' iwm0@pci0:4:0:0:class=0x028000 card=0x01308086 chip=0x24f38086 rev=0x3a hdr=0x00 vendor = 'Intel Corporation' device = 'Wireless 8260' class = network nvme0@pci0:5:0:0:class=0x010802 card=0xa801144d chip=0xa804144d rev=0x00 hdr=0x00 vendor = 'Samsung Electronics Co Ltd' class = mass storage subclass = NVM root@fb:~ # -- snipp -- ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
O Que Você Quer ser Amanhã? Cursos Técnicos 2017 na Faculdade SENAI
___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf
Ian Lepore skrev: > > On Tue, 2016-12-13 at 10:13 -0700, Ian Lepore wrote: >> On Tue, 2016-12-13 at 10:00 +, tech-lists wrote: >> > >> > On 12/12/2016 23:40, Herbert J. Skuhra wrote: >> > > >> > > >> > > PORTS_MODULES does not work if KERNCONF contains multiple >> > > kernels: >> > > >> > > The problem is obviously in /usr/src/sys/conf/kern.post.mk (line >> > > 66): >> > > >> > > WRKDIRPREFIX?= ${MAKEOBJDIRPREFIX}${SRC_BASE}/sys/${KERNCONF} >> > hmm! I didn't know that. >> > >> > I can't confirm exactly when the old way stopped working and when >> > I >> > started defining modules in src.conf. >> > >> > If I wanted to install a known, good kernel as /boot/workingkernel >> > with >> > all of its modules, so that I can avoid kernel.old being a bad >> > kernel >> > and kernel being non-bootable, how would I go about doing it? >> > >> > many thanks, >> > >> I think the problem might have started with some changes to the >> kernel >> build infrastructure that result in reading make.conf and/or src.conf >> when they didn't used to, so now KERNCONF with multiple entries is >> defined differently in kern.post.mk than it used to be. >> >> I wonder if this patch might fix it (I'm not in a position to test it >> myself right now -- this is purely a shot in the dark)... >> >> iIndex: sys/conf/kern.post.mk >> === >> --- sys/conf/kern.post.mk(revision 302505) >> +++ sys/conf/kern.post.mk(working copy) >> @@ -63,7 +63,7 @@ OSRELDATE!=awk >> '/^\#define[[:space:]]*__FreeBSD_v >> ${MAKEOBJDIRPREFIX}${SRC_BASE}/include/osreldate >> .h >> .endif >> # Keep the related ports builds in the obj directory so that they >> are only rebuilt once per kernel build >> -WRKDIRPREFIX?= ${MAKEOBJDIRPREFIX}${SRC_BASE}/sys/${KERNCONF} >> +WRKDIRPREFIX?= ${MAKEOBJDIRPREFIX}${SRC_BASE}/sys/${.OBJDIR} >> PORTSMODULESENV=\ >> PATH=${PATH}:${LOCALBASE}/bin:${LOCALBASE}/sbin \ >> SRC_BASE=${SRC_BASE} \ >> >> -- Ian > > Actually, now that I look at it again, I wonder if it should be just: > > +WRKDIRPREFIX?= ${.OBJDIR} Yeah, this could work: Before: ===> Ports module x11/nvidia-driver (all) cd ${PORTSDIR:-/usr/ports}/x11/nvidia-driver; env -u CC -u CXX -u CPP PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin SRC_BASE=/usr/src OSVERSION=1100506 WRKDIRPREFIX=/usr/obj/usr/src/sys/WS01 GENERIC make -B clean all After: ===> Ports module x11/nvidia-driver (all) cd ${PORTSDIR:-/usr/ports}/x11/nvidia-driver; env -u CC -u CXX -u CPP PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin SRC_BASE=/usr/src OSVERSION=1100506 WRKDIRPREFIX=/usr/obj/usr/src/sys/WS01 make -B clean all -- Herbert ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: broken source upgrade 9.3-STABLE to 10.3-STABLE
On 14.12.2016 16:07, Kurt Jaeger wrote: > Hi! > >> I've got legacy FreeBSD server running 8.4-STABLE and I'm trying to upgrade >> it. >> Source upgrade for 8.4 to 9.3-STABLE r310015 went flawlessly. >> After reboot, I checked out stable/10 r310043 sources and ran buildworld >> again. >> It fails: > > I suggest two different approaches (have not tried that, but...) > > 1) sidegrade (with build-from-source) to 9.3-RELEASE, then use >freebsd-update to 10.x > > 2) don't upgrade to 10-STABLE, but surce-upgrade to 10.0 or 10.1-RELEASE > I've manually applied single-line change r309860 to stable/10 tree and that fixed the problem, now build continues. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: broken source upgrade 9.3-STABLE to 10.3-STABLE
Hi! > I've got legacy FreeBSD server running 8.4-STABLE and I'm trying to upgrade > it. > Source upgrade for 8.4 to 9.3-STABLE r310015 went flawlessly. > After reboot, I checked out stable/10 r310043 sources and ran buildworld > again. > It fails: I suggest two different approaches (have not tried that, but...) 1) sidegrade (with build-from-source) to 9.3-RELEASE, then use freebsd-update to 10.x 2) don't upgrade to 10-STABLE, but surce-upgrade to 10.0 or 10.1-RELEASE -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: broken source upgrade 9.3-STABLE to 10.3-STABLE
CC'ing Dimitry Andric On 14.12.2016 14:27, Eugene Grosbein wrote: > I've got legacy FreeBSD server running 8.4-STABLE and I'm trying to upgrade > it. > Source upgrade for 8.4 to 9.3-STABLE r310015 went flawlessly. > After reboot, I checked out stable/10 r310043 sources and ran buildworld > again. > It fails: > > ===> lib/clang/libllvmanalysis (all) > c++ -O2 -pipe > -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/include > -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/tools/clang/include > -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis -I. > -I/usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/../../lib/clang/include > -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS > -D__STDC_CONSTANT_MACROS -DNDEBUG -fno-strict-aliasing > -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd10.3\" > -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd10.3\" > -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/tmp\" > -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c > /usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis/LazyValueInfo.cpp > -o LazyValueInfo.o > /usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis/LazyValueInfo.cpp: > In member function 'llvm::Constant* > llvm::LazyValueInfo::getConstant(llvm::Value*, llvm::BasicBlock*)': > /usr/src/lib/clang/libllvmanalysis/../../../contrib/llvm/lib/Analysis/LazyValueInfo.cpp:1054: > error: 'nullptr' was not declared in this scope > *** Error code 1 > > Does it mean that FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final > 208032) 20140512 > is unable to build more recent clang version? There was r309722: > Pull in r281586 from upstream llvm trunk (by Wei Mi): > Add some shortcuts in LazyValueInfo to reduce compile time of Correlated > Value Propagation. And there was MFC for r309722 to stable/9,10,11 (r309857) that broke things. And there was a fix r309860 committed to stable/9 but not to stable/10: --- stable/9/contrib/llvm/lib/Analysis/LazyValueInfo.cpp2016/12/11 23:36:11 309859 +++ stable/9/contrib/llvm/lib/Analysis/LazyValueInfo.cpp2016/12/12 00:09:08 309860 @@ -1051,7 +1051,7 @@ Constant *LazyValueInfo::getConstant(Value *V, BasicBlock *BB) { // Bail out early if V is known not to be a Constant. if (isKnownNonConstant(V)) -return nullptr; +return 0; LVILatticeVal Result = getCache(PImpl).getValueInBlock(V, BB); Please unbreak source upgrade from 9.3-STABLE to 10.3-STABLE. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"