Re: FreeBSD_STABLE_10-i386 - Build #1643 - Still Failing
On 01/18/17 12:46, Andriy Gapon wrote: On 18/01/2017 18:58, jenkins-ad...@freebsd.org wrote: FreeBSD_STABLE_10-i386 - Build #1643 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/1643/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/1643/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/1643/console Change summaries: 312386 by pfg: MFC r311947, r311981: rpcgen(1): Avoid unused variable warning on generated code. Avoid "unused variable 'i'" warnings in generated .c files by only emitting the "int i;" for non-opaque arrays. Opaque arrays use xdr_opaque() rather than iterating over the array. Obtained from: OpenBSD (CVS rev 1.28) rpcgen(1): Check getrlimit() return for generated code. Obtained from: NetBSD (CVS rev 1.27, 1.28) 312382 by avg: MFC r310630: libkvm: support access to vmm guest memory, allow writes to fwmem and vmm Sponsored by:Panzura The end of the build log: ... make[5]: make[5]: don't know how to make gzguts.h. Stop make[5]: stopped in /usr/src/sys/boot/libstand32 gzguts.h in libstand32? That does not seem to be related to any of the commits listed at the beginning. It says "still failing" so the breakage comes from the past. Pedro. ___ 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: Problem building stable-11 on FreeBSD stable-10
On 07/08/16 11:04, Pedro Giffuni wrote: Hello; Sorry if this is a naive question, I just tried to build 11-stable on 10-stable and I got this: _ ... cc -O2 -pipe -march=core2 -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/usr/src/sys -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/obj/usr/src/sys/GENERIC -MD -MP -MF.depend.aac.o -MTaac.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -mno-aes -mno-avx -std=iso9899:1999 -c /usr/src/sys/modules/aac/../../dev/aac/aac.c -o aac.o --- all_subdir_aacraid --- /usr/src/sys/modules/aacraid/../../dev/aacraid/aacraid.c:2510:50: error: invalid conversion specifier 'b' [-Werror,-Wformat-invalid-specifier] device_printf(sc->aac_dev, "Supported Options=%b\n", ~^ /usr/src/sys/modules/aacraid/../../dev/aacraid/aacraid.c:2512:10: error: data argument not used by format string [-Werror,-Wformat-extra-args] "\20" ^ 2 errors generated. *** [aacraid.o] Error code 1 make[4]: stopped in /usr/src/sys/modules/aacraid 1 error ... _ For the record, I got around this by building the kernel-toolchain target. Pedro. ___ 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"
Problem building stable-11 on FreeBSD stable-10
Hello; Sorry if this is a naive question, I just tried to build 11-stable on 10-stable and I got this: _ ... cc -O2 -pipe -march=core2 -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/usr/src/sys -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/obj/usr/src/sys/GENERIC -MD -MP -MF.depend.aac.o -MTaac.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -mno-aes -mno-avx -std=iso9899:1999 -c /usr/src/sys/modules/aac/../../dev/aac/aac.c -o aac.o --- all_subdir_aacraid --- /usr/src/sys/modules/aacraid/../../dev/aacraid/aacraid.c:2510:50: error: invalid conversion specifier 'b' [-Werror,-Wformat-invalid-specifier] device_printf(sc->aac_dev, "Supported Options=%b\n", ~^ /usr/src/sys/modules/aacraid/../../dev/aacraid/aacraid.c:2512:10: error: data argument not used by format string [-Werror,-Wformat-extra-args] "\20" ^ 2 errors generated. *** [aacraid.o] Error code 1 make[4]: stopped in /usr/src/sys/modules/aacraid 1 error ... _ So, while here, is there a "blessed" way to upgrade 10-stable to 11-stable, without wiping out my disks? Pedro. ___ 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 for GENERIC 9-STABLE just hangs, no error (was svn commit: r249549 - in stable/9/sys: amd64/conf i386/conf)
On 04/17/13 03:29, Jeremy Chadwick wrote: On Tue, Apr 16, 2013 at 04:09:28PM +, Brooks Davis wrote: Author: brooks Date: Tue Apr 16 16:09:27 2013 New Revision: 249549 URL: http://svnweb.freebsd.org/changeset/base/249549 Log: MFC (much delayed) 234504: Enable DTrace hooks in GENERIC. Modified: stable/9/sys/amd64/conf/GENERIC stable/9/sys/i386/conf/GENERIC Directory Properties: stable/9/sys/ (props changed) ... And here come the complaints, which warrant responses from key folks who are in the know: http://lists.freebsd.org/pipermail/freebsd-stable/2013-April/073132.html It looks like 9 days ago there was a change (r249243) that fixed issues on the userland ctf utilities, so you have to update your userland too if it's not recent (make buildworld works fine). Hope that helps, Pedro. ___ 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: rpc.lockd exiting just after startup @r240811
Hello David; Sorry to have caused you trouble. - Original Message - From: David Wolfskill da...@catwhisker.org ... On Sun, Sep 23, 2012 at 06:43:49PM +0300, Konstantin Belousov wrote: ... Try to revert the r240799. If this does not help, then some digging with gdb would be needed to see why kernel dislikes the buffer. Well, the same digging would be needed even if the revert helps. Thanks for the suggestiion. As noted earlier, I first tried a rebuild (not specifying -DNOCLEAN); that proved ineffective. I then reverted r240799, and rpc.lockd runs; I am now able to issue svn commands against an NFS-resident working copy. The procedure I used (in case I screwed up -- or there's a less inelegant way to do it) was: cd /usr/src \ svn diff -c 240799 /tmp/d \ svn patch --reverse-diff /tmp/d I then performed: make -DNOCLEAN -j 4 buildworld make -DNOCLEAN -j 4 kernel The machine is now running: FreeBSD freebeast.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #478 240856M: Sun Sep 23 15:02:33 PDT 2012 r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 I have subsequently seen similar symptoms on my work desktop, which is running stable/9 as of r240849. Since rpc.lockd seems OK on the systems running head, perhaps there was an issue with the MFC? Both should have the same issue. It does depend on what kind of load your -current box is running, of course. I'll be happy to test further -- I just need a bit of guidance from time to time. :-} What I can do is send you individual patches to see if we can narrow down the culprit. If I can avoid reverting all the change it will be better. It will be a bit boring because you may have to build kernel and libc each time, so I would start with the most obvious candidates. For now just leave r240799 reverted. Pedro. ___ 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: Latest stable/8 broken for mozilla ports (fwd)
Hi Doug; Perhaps you are using -O2 in you CFLAGS? There were reports of gcc issues when optimizing but we never found the smoking gun. Pedro. From: Doug Barton do...@freebsd.org Since I know many of you don't read -stable ... please follow up there though. -- Forwarded message -- From: Doug Barton do...@freebsd.org To: freebsd-stable@FreeBSD.org Date: Tue, 24 Jul 2012 13:41:58 Organization: http://SupersetSolutions.com/ User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Subject: Latest stable/8 broken for mozilla ports For both firefox and thunderbird I'm getting this: firefox Fatal error 'locklevel = 0' at line 98 in file /frontier/svn/stable/8/lib/libthr/thread/thr_kern.c (errno = 2) Redirecting call to abort() to mozalloc_abort Segmentation fault: 11 (core dumped) This is on r238752, previous working version was r238655 thr_kern.c hasn't been updated since the last 8-release, so it would seem to be something else. Insights welcome, Doug -- This mail is for the internal use of the FreeBSD project committers, and as such is private. This mail may not be published or forwarded outside the FreeBSD committers' group or disclosed to other unauthorised parties without the explicit permission of the author(s). ___ 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: sh(1) exiting on SIGWINCH
Hello guys; --- Gio 5/7/12, Peter Jeremy pe...@rulingia.com ha scritto: Brandon Gooch jamesbrandongo...@gmail.com wrote: Seems that the window resize is somehow causing sh(1) to receive an EOF while the shell is sitting at the prompt, which results in the shell exiting; haven't dug too deeply into the source yet, but can you try to run /bin/sh with the '-I' (that's capital letter 'i') and it the shell shouldn't exit (but it will bark at you with a 'Use exit to leave shell.' message on each resize. Interesting. I hadn't tried '-I' but now also see that. I'm CC'ing jilles@ for any potential insight into the behavior of sh(1) (and perhaps this updated libedit snapshot). I would also welcome any insights jilles@ can offer. pfg@ (who shepherded the libedit update into the tree), David Shao (originator of kern/169603) and I have been investigating fixes to libedit but do not have a solution yet. There is a possibility that sh(1) is relying on bugs in the old libedit. At this stage, it seems likely that the libedit update (r237738) will be reverted for 9.1-RELEASE. I am trying hard to identify the specific changes from NetBSD that caused the issue. The problem is known to happen in the latest version of the upstream sources too but I don't want to revert all the patch if I can avoid it because it is becoming increasingly difficult update libedit and we need some of the new features. It seems like David Shao's issue is different but so far I am aware that the issue was introduced in the changes associated with read.c http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libedit/read.c NetBSD fixed the SIGWINCH issue in revisions 1.55, 1.56 and 1.57 of that file but it was caused by revision 1.43 the EOF issue seems to be caused by Revision 1.49 I still have to play more with this. Pedro. ___ 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: sh(1) exiting on SIGWINCH
Hello; --- Gio 5/7/12, Peter Jeremy pe...@rulingia.com ha scritto: ... pfg@ (who shepherded the libedit update into the tree), David Shao (originator of kern/169603) and I have been investigating fixes to libedit but do not have a solution yet. The following partial revert fixes things for me: http://people.freebsd.org/~pfg/patches/libedit/patch-169603 best regards, Pedro. ___ 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: Network unavailable when booting directly to FreeBSD.
Hi again; --- Mar 26/6/12, YongHyeon PYUN pyu...@gmail.com ha scritto: ... -0700, Pedro Giffuni wrote: Hi again; --- Dom 24/6/12, Pedro Giffuni p...@freebsd.org ha scritto: ... --- Lun 25/6/12, YongHyeon PYUN pyu...@gmail.com ha scritto: ... Could you narrow down which commit broke bge(4)? Sean Bruno suggested it may be r233495, but I haven't found the time to revert it. I will let you know tomorrow. Reverting only r233495 didn't fix it either. This will Because your controller is not BCM5704, r233495 should have no effects. take some time :(. Ok, if you happen to find guilty commit let me know. Well... To make it easier to test I dropped the kernel driver and started using only the kld. I also reverted the driver back to the 9.0R version. The network card still gives me the watchdog timeouts and now after X starts I lose control of the mouse and the keyboard. I've seen similar reports on the latest PC-BSD but they went away for me after I added the USB stuff to /boot/defaults. This is all very weird; I suspect it may be some issue in the bus support and not really a driver issue :(. HTH, Pedro. ___ 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: Network unavailable when booting directly to FreeBSD.
Hi again; --- Dom 24/6/12, Pedro Giffuni p...@freebsd.org ha scritto: ... --- Lun 25/6/12, YongHyeon PYUN pyu...@gmail.com ha scritto: ... Could you narrow down which commit broke bge(4)? Sean Bruno suggested it may be r233495, but I haven't found the time to revert it. I will let you know tomorrow. Reverting only r233495 didn't fix it either. This will take some time :(. Pedro. ___ 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: Network unavailable when booting directly to FreeBSD.
--- Lun 25/6/12, YongHyeon PYUN pyu...@gmail.com ha scritto: ... Could you narrow down which commit broke bge(4)? Sean Bruno suggested it may be r233495, but I haven't found the time to revert it. I will let you know tomorrow. Pedro. ___ 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: Network unavailable when booting directly to FreeBSD.
Hello; --- Sab 23/6/12, YongHyeon PYUN pyu...@gmail.com ha scritto: ... amd64 From my dmesg __ ... pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pcib0: Length mismatch for 4 range: 81 vs 7f pci0: ACPI PCI bus on pcib0 pci0: memory, RAM at device 0.0 (no driver attached) pci0: memory, RAM at device 0.1 (no driver attached) pci0: memory, RAM at device 0.2 (no driver attached) pci0: memory, RAM at device 0.3 (no driver attached) pci0: memory, RAM at device 0.4 (no driver attached) pci0: memory, RAM at device 0.5 (no driver attached) pci0: memory, RAM at device 0.6 (no driver attached) pci0: memory, RAM at device 0.7 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 3.0 on pci0 pci2: ACPI PCI bus on pcib2 bge0: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x00b002 mem 0xfdef-0xfdef irq 16 at device 0.0 on pci2 bge0: CHIP ID 0xb002; ASIC REV 0x0b; CHIP REV 0xb0; PCI-E miibus0: MII bus on bge0 brgphy0: BCM5754/5787 1000BASE-T media interface PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Ethernet address: 00:18:8b:76:a4:1e pcib3: ACPI PCI-PCI bridge at device 4.0 on pci0 pci3: ACPI PCI bus on pcib3 Cuse4BSD v0.1.23 @ /dev/cuse bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting WARNING: attempt to domain_add(bluetooth) after domainfinalize() fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 bge0: watchdog timeout -- resetting bge0: link state changed to DOWN bge0: link state changed to UP bge0: watchdog timeout -- resetting bge0: link state changed to DOWN bge0: link state changed to UP bge0: watchdog timeout -- resetting bge0: link state changed to DOWN bge0: link state changed to UP _ Iff I boot Windows first and then reboot to start FreeBSD the network works fine. This looks strange and I can't narrow down what other changes made since 9.0-RELEASE broke the driver. Would you try reverting r235821? I reverted it manually but things didn't change. If that does not solve the issue, would you try a WIP version at the following URL? It's mainly written to improve BCM5720 with APE firmware support and it exactly follows recommendations suggested by Broadcom so it may have some differences. http://people.freebsd.org/~yongari/bge/if_bge.c http://people.freebsd.org/~yongari/bge/if_bgereg.h http://people.freebsd.org/~yongari/bge/brgphy.c No joy either :( Pedro. ___ 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
Network unavailable when booting directly to FreeBSD.
Hello; I noticed a regression from 9.0 and I cannot boot directly FreeBSD and access the network. Unfortunately I cannot recall the exact commit where this started happening. uname -a FreeBSD pcbsd-8555 9.0-STABLE FreeBSD 9.0-STABLE #12: Wed May 30 11:16:35 PDT 2012 r...@build9x64.pcbsd.org:/usr/obj/builds/amd64/pcbsd-build90/fbsd-source/9.0/sys/GENERIC amd64 From my dmesg __ ... pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pcib0: Length mismatch for 4 range: 81 vs 7f pci0: ACPI PCI bus on pcib0 pci0: memory, RAM at device 0.0 (no driver attached) pci0: memory, RAM at device 0.1 (no driver attached) pci0: memory, RAM at device 0.2 (no driver attached) pci0: memory, RAM at device 0.3 (no driver attached) pci0: memory, RAM at device 0.4 (no driver attached) pci0: memory, RAM at device 0.5 (no driver attached) pci0: memory, RAM at device 0.6 (no driver attached) pci0: memory, RAM at device 0.7 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 3.0 on pci0 pci2: ACPI PCI bus on pcib2 bge0: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x00b002 mem 0xfdef-0xfdef irq 16 at device 0.0 on pci2 bge0: CHIP ID 0xb002; ASIC REV 0x0b; CHIP REV 0xb0; PCI-E miibus0: MII bus on bge0 brgphy0: BCM5754/5787 1000BASE-T media interface PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Ethernet address: 00:18:8b:76:a4:1e pcib3: ACPI PCI-PCI bridge at device 4.0 on pci0 pci3: ACPI PCI bus on pcib3 Cuse4BSD v0.1.23 @ /dev/cuse bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting WARNING: attempt to domain_add(bluetooth) after domainfinalize() fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 bge0: watchdog timeout -- resetting bge0: link state changed to DOWN bge0: link state changed to UP bge0: watchdog timeout -- resetting bge0: link state changed to DOWN bge0: link state changed to UP bge0: watchdog timeout -- resetting bge0: link state changed to DOWN bge0: link state changed to UP _ Iff I boot Windows first and then reboot to start FreeBSD the network works fine. Pedro. ___ 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: Network unavailable when booting directly to FreeBSD.
--- Gio 21/6/12, Sean Bruno sean...@yahoo-inc.com ha scritto: On Thu, 2012-06-21 at 12:05 -0700, Pedro Giffuni wrote: Hello; I noticed a regression from 9.0 and I cannot boot directly FreeBSD and access the network. Unfortunately I cannot recall the exact commit where this started happening. uname -a FreeBSD pcbsd-8555 9.0-STABLE FreeBSD 9.0-STABLE #12: Wed May 30 11:16:35 PDT 2012 r...@build9x64.pcbsd.org:/usr/obj/builds/amd64/pcbsd-build90/fbsd-source/9.0/sys/GENERIC amd64 ... I wonder if this is the one that caused your problems? http://svnweb.freebsd.org/base?view=revisionrevision=233495 I will have a look at reverting it locally. Can you post the full verbose dmesg http://people.freebsd.org/~pfg/dmesg-bge-error.txt and the output of pciconf -lvb http://people.freebsd.org/~pfg/pciconf.txt for review? Thanks! Pedro. ___ 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: Why Are You NOT Using FreeBSD?
--- Sab 2/6/12, O. Hartmann ohart...@zedat.fu-berlin.de ha scritto: Since I'm with FreeBSD, StarOffice, OpenOffice and even now LibreOffice is a MESS! ... Can you be more specific about what is wrong with Apache OpenOffice? best regards, Pedro. ___ 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
