[Bug 244713] Processes hanging in "nfs" state
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244713 --- Comment #1 from Julien Cigar --- Created attachment 212298 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=212298&action=edit ps -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 244713] Processes hanging in "nfs" state
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244713 Bug ID: 244713 Summary: Processes hanging in "nfs" state Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: jul...@perdition.city Hello, I have a Python webapp which is running in a 10.3-RELEASE JAIL on a 12.1-RELEASE HOST which is randomly hanging in nfs state. Processes are unkillable and require a hard reboot. The HOST is running UFS (with SU, but without +J) and the NFS server is running 10.3-RELEASE. NFS4 shares are mounted on the HOST with "nfsv4,ro,bg,late" options (NFS4 only) It looks like a deadlock to me and I've attached a procstat -kk of the offending processes -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 244713] Processes hanging in "nfs" state
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244713 --- Comment #2 from Julien Cigar --- Created attachment 212299 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=212299&action=edit procstat -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 244699] growfs panics after [r358714, r358716]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244699 Li-Wen Hsu changed: What|Removed |Added Assignee|b...@freebsd.org|lw...@freebsd.org --- Comment #5 from Li-Wen Hsu --- Fix verified. Thanks for the information. I didn't notice that there was followup when analyzing this issue. Leave this open to add (or check) tests for growfs. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496
--- Comment #37 from Peter Eriksson ---
Any SAS-expanders between the SAS HBA and the (SATA) disks?
("mprutil show expanders") - and if so - do they (the expanders) have up to
date firmware?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 --- Comment #38 from Matthias Pfaller --- (In reply to Peter Eriksson from comment #37) Not in our case: [root@nyx ~]# mpsutil show all Adapter: mps0 Adapter: Board Name: SAS9211-8i Board Assembly: Chip Name: LSISAS2008 Chip Revision: ALL BIOS Revision: 0.00.00.00 Firmware Revision: 19.00.00.00 Integrated RAID: no PhyNum CtlrHandle DevHandle Disabled Speed MinMaxDevice 0 N 1.56.0SAS Initiator 1 N 1.56.0SAS Initiator 2 N 1.56.0SAS Initiator 3 N 1.56.0SAS Initiator 4 N 1.56.0SAS Initiator 5 N 1.56.0SAS Initiator 6 N 1.56.0SAS Initiator 7 N 1.56.0SAS Initiator Devices: BTSAS Address Handle ParentDeviceSpeed Enc Slot Wdt Enclosures: Slots Logical ID SEPHandle EncHandleType 08500605b001551a80 0001 Direct Attached SGPIO Expanders: NumPhys SAS Address DevHandle Parent EncHandle SAS Level We did downgrade to firmware 19.00.00.00, but I hadn't the time to run some tests using this firmware level. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 --- Comment #39 from Paul Thornton --- I don't have an expanders (note that this card has IR firmware, in case that is relevant - I wasn't actually aware of that, it is only being used as a dumb HBA): [root@nas1b ~]# mprutil show all Adapter: mpr0 Adapter: Board Name: LSI3008-IR Board Assembly: Chip Name: LSISAS3008 Chip Revision: ALL BIOS Revision: 8.35.00.00 Firmware Revision: 15.00.03.00 Integrated RAID: yes PhyNum CtlrHandle DevHandle Disabled Speed MinMaxDevice 0 N 3.012 SAS Initiator 1 N 3.012 SAS Initiator 2 N 3.012 SAS Initiator 3 N 3.012 SAS Initiator 4 N 3.012 SAS Initiator 5 N 3.012 SAS Initiator 6 N 3.012 SAS Initiator 7 N 3.012 SAS Initiator Devices: BTSAS Address Handle ParentDeviceSpeed Enc Slot Wdt Enclosures: Slots Logical ID SEPHandle EncHandleType 08500304801cf54a05 0001 Direct Attached SGPIO Expanders: NumPhys SAS Address DevHandle Parent EncHandle SAS Level [root@nas1b ~]# -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 224496] mpr and mps drivers seems to have issues with large seagate drives
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 --- Comment #40 from Peter Eriksson --- I've had some random problems when using the cards with IR firmware, so I always make sure they are running IT firmware. Might be worth testing. But that might not be relevant for your problems. We are using them without any issues (so far) but we're using SAS drives (10TB HGST) behind SAS Expanders (and a couple of Intel SSD SATA drives) - so nothing similar to your situation... # mprutil show all Adapter: mpr0 Adapter: Board Name: Dell HBA330 Mini Board Assembly: Chip Name: LSISAS3008 Chip Revision: ALL BIOS Revision: 18.00.00.00 Firmware Revision: 16.00.08.00 Integrated RAID: no -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 244719] Build of 12-STABLE breaks: error: use of undeclared identifier 'compiler_flags'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244719 Bug ID: 244719 Summary: Build of 12-STABLE breaks: error: use of undeclared identifier 'compiler_flags' Product: Base System Version: 12.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: y...@freebsd.org rev.358827 > /usr/src/crypto/openssl/crypto/cversion.c:27:16: error: use of undeclared > identifier 'compiler_flags' > return compiler_flags; >^ Not sure how do I update it now from source. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 244644] Legacy timezones for Ukraine are in the main category, name for only current timezone is confusing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244644 --- Comment #5 from be...@protonmail.com --- TZ is updated (https://github.com/eggert/tz/commit/33fd3277ecf0f60c2d2bf268bbfafd1a3889f2d6), but the installation shows the same tabs. https://i.imgur.com/8hGlxrh.png If FBSD needs to be synced with the TZ, I'm letting you know. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 237463] aacraid(4) doesn't work on powerpc64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237463 --- Comment #17 from Leandro Lupori --- (In reply to Leandro Lupori from comment #5) About this issue of the drive being removed and then re-inserted after a few seconds, further investigation revealed that the problem was caused by two SAS controllers (Adaptec and LSI) being connected to all HDDs through a SAS expander cable. When LSI controller's cable was disconnected, the issue stopped happening. So apparently the issue was some kind of conflict or interference between the 2 adapters connected to the same disks and not a driver issue. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]
On Mon, 9 Mar 2020 at 15:15, Andy Farkas wrote: > > On 2020-03-10 01:04, Konstantin Belousov wrote: > > Take a look at r334530. > > "or the user really hates this feature and can't wait to turn it off" So to confirm, your issue is with sc(4), not vt(4)? ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 244644] Legacy timezones for Ukraine are in the main category, name for only current timezone is confusing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244644 --- Comment #6 from Ed Maste --- Yes, this should show up the next time tzdata gets released and updated into FreeBSD. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 244644] Legacy timezones for Ukraine are in the main category, name for only current timezone is confusing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244644 --- Comment #7 from be...@protonmail.com --- (In reply to Ed Maste from comment #6) Could you please provide the approximate date for such update? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]
On Tue, 10 Mar 2020 05:14:49 +1000 Andy Farkas an...@andyit.com.au said On 2020-03-10 01:04, Konstantin Belousov wrote: > Take a look at r334530. "or the user really hates this feature and can't wait to turn it off" Excellently explained by Bruce as usual: "Revision 314641 - (view) (download) (annotate) - [select for diffs] Modified Sat Mar 4 06:19:12 2017 UTC (3 years ago) by bde File length: 107771 byte(s) Diff to previous 312910 Colorize syscons kernel console output according to a table indexed by the CPU number. This was originally for debugging near-deadlock conditions where multiple CPUs either deadlock or scramble each other's output trying to report the problem, but I found it interesting and sometimes useful for ordinary kernel messages. Ordinary kernel messages shouldn't be interleaved, but if they are then the colorization makes them readable even if the interleaving is for every character (provided the CPU printing each message doesn't change). The default colors are 8-15 starting at 15 (bright white on black) for CPU 0 and repeating every 8 CPUs. This works best with 8 CPUs. OK the colors are CPU/core bound. That explains why initiating the NIC starts on one color, then changes to a *different* color when reporting the status -- the job moved to a *different* CPU/core. Annoying! IMHO. I guess I'll have to have a look at getting the white/high-intensity-white behavior back. A *massive* thanks for all the insight, Andy! --Chris RIP https://photos.app.goo.gl/YiVmFtWiK8Niy3Fw6 -andyf ___ freebsd-sta...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 243229] awk length() function in base system produces an incorrect results for UTF-8 strings
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243229 Serge Volkov changed: What|Removed |Added Hardware|Any |amd64 Component|misc|bin -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 243225] "mpr0: Out of chain frames" boot hang after clang 9.0.1 import (probably timing, not compiler related)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243225 --- Comment #3 from Terry Kennedy --- (In reply to Peter Eriksson from comment #2) X2APIC has been off on this system since it was installed - I see the same USB symptoms that you reported if I enable it. But I get the mpr(4) errors in either case. I updated the BIOS and OS Collector (which isn't used on FreeBSD) - everything else was already up-to-date = and repeated the tests, with the same result. Since I suspect this is timing-related, I enabled Hyperthreading (which I normally force off in the BIOS) and the system booted (at least this one time) without the mpr(4) hang. Again, this system had been working for some time, but then started hanging with the "out of chain frames" at boot time. Dell support moved the controller to a different slot, which "fixed" the problem, at least until the clang 9.x import, which apparently changed the timing enough to make the problem show up again. I think all of the above points to some timing issue in the mpr(4) driver. Hopefully someone with knowledge of that driver's inner workings will see this and comment. I can continue to make the system available (via iDRAC port, so the developer can reset it, change BIOS settings, etc.) if needed for someone to diagnose this issue. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 244713] Processes hanging in "nfs" state
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244713 Konstantin Belousov changed: What|Removed |Added CC||k...@freebsd.org --- Comment #3 from Konstantin Belousov --- The 'grbmaw' thread waits for the xbusy state of the page to pass, so that the caller can sbusy it. There must be other thread which owns the xbusy. Perhaps provide the procstat -kk output for all processes. Also it might be worth trying 12-stable kernel, where some number of bugs in nearby area were fixed. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]
On 2020-03-11 02:19, Ed Maste wrote: So to confirm, your issue is with sc(4), not vt(4)? I don't actually have an issue with either. although: "After booting, all colors can be changed using the syscons.kattr sysctl." % sysctl -a | grep syscons hw.syscons.sc_no_suspend_vtswitch: 0 hw.syscons.kbd_debug: 1 hw.syscons.kbd_reboot: 1 hw.syscons.bell: 1 hw.syscons.saver.keybonly: 0 % Also, both sc and vt are compiled into GENERIC. Is it just a matter of putting "syscons=[sc|vt]" in loader.conf to select whatever driver? FreeBSD drunkfish.andyit.com.au 12.1-STABLE FreeBSD 12.1-STABLE #1 r358253: Sun Feb 23 15:02:00 AEST 2020 -andyf ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235751] Failure to init TLS variables with func ptr inside shared lib
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235751 --- Comment #4 from Mark Millard --- Hmm. For: hydra$ echo $CC /usr/local/bin/gcc8 hydra$ echo $CFLAGS -g -m64 -std=c99 -fno-builtin -O0 -mcpu=970 -mcall-freebsd -mno-altivec -mno-float128 -mno-float128-hardware -mfull-toc -mregnames -fno-unsafe-math-optimizations the system compiler and libraries were not in use. I'd expect an ldd on the ./foo to have shown gcc libraries involved, possibly spanning at least parts of gcc's thread local storage support. I'm not so sure that "Base System" was the right place for this report, in fact it might not even be a FreeBSD specific issue as presented. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207359] head -r339076 TARGET_ARCH=powerpc64 via powerpc64-gcc : some or all c++ exceptions unbounded loop in _Unwind_RaiseException
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207359 Mark Millard changed: What|Removed |Added Status|New |Closed Resolution|--- |Overcome By Events --- Comment #18 from Mark Millard --- Head no longer has the old libunwind code and my understanding is that there is no plan to complete the implementation of DW_CFA_remember_state and DW_CFA_restore_state in 11 or 12 (which still have the old libunwind code as I understand). And, of course, devel/freebsd-gcc* are not the official way of building 11 or 12 (or head for that matter). There are other issues preventing buildworld via the likes of devel/freebsd-gcc9 . So I'm just going to list "Overcome By Events" instead of "fixed". -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207736] clang 3.8.0/powerpc/powerpc64's _Unwind_RaiseException code generation has messed up r31 (frame pointer) save/restore code (SEGV's can result)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207736 Mark Millard changed: What|Removed |Added Status|New |Closed Resolution|--- |FIXED --- Comment #6 from Mark Millard --- Head no longer has the old libunwind code and my understanding is that there is no plan to complete the implementation of DW_CFA_remember_state and DW_CFA_restore_state in 11 or 12 (which still have the old libunwind code as I understand). clang also has progressed so that in head, and eventually 13.0, clang will be officially the means of building powerpc families (64-bit and 32-bit), using llvm's libunwind. The 64-bit ABI has also been changed as part of the activity. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 207325] 11.0-CURRENT/clang 3.8.0 for TARGET_ARCH=powerpc : c++ exceptions cause SEGV (9 line program)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207325 Mark Millard changed: What|Removed |Added Status|New |Closed Resolution|--- |Overcome By Events --- Comment #13 from Mark Millard --- Head no longer has the old libunwind code and my understanding is that there is no plan to complete the implementation of DW_CFA_remember_state and DW_CFA_restore_state in 11 or 12 (which still have the old libunwind code as I understand). clang also has progressed so that in head, and eventually 13.0, clang will be officially the means of building powerpc families (64-bit and 32-bit), using llvm's libunwind. The 64-bit ABI has also been changed as part of the activity. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 237590] powerpc64 PowerMac11,2 and 7,2 context, -r330614 and later (including -r345758): "ofwdump -ap" crashes the system; probable -r330610 "cause"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237590 --- Comment #6 from Mark Millard --- The conflict between the new 64-bit direct map and use of PowerMac G5 openfirmware during: ofwdump -Plog /packages/obp-tftp continues. A usefdt mode patched up sufficiently to work with the PowerMac G5's (and more PowerMacs) can avoid this but needs to deal with some PowerMac openfirmware oddities (violations of some rules), as well as having some fixes to FreeBSD code. The PowerMac's even have at least one example of (extracted from a patch): +// Some Macintoshes have identical package-to-pathname results for +// multiple nodes of the same type and unit under the parent node. +// Avoid blocking this for fdt. (Unfortuantely the (textually small) change is in contrib code. It was the only part of my investigatory code that was.) (One oddity is that the unpatched conversion to fdt code reverses the order of the sibling lists but the FreeBSD code does not work in an order independent manor for uisng the sibling lists. In my investigatory patching, I made the conversion preserve order instead of changing a bunch of code that used the lists.) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 244706] panic: NULL dereference inside __mtx_lock_sleep()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244706 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable12?, ||mfc-stable11? CC||n...@freebsd.org Summary|[panic] NULL dereference|panic: NULL dereference |inside __mtx_lock_sleep() |inside __mtx_lock_sleep() Status|New |Open Keywords|panic |crash, needs-qa -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 244706] panic: NULL dereference inside __mtx_lock_sleep()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244706 Kubilay Kocak changed: What|Removed |Added Hardware|Any |amd64 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 244729] Buildworld fails when installed world is built WITHOUT_LEGACY_CONSOLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244729 Bug ID: 244729 Summary: Buildworld fails when installed world is built WITHOUT_LEGACY_CONSOLE Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: ktulla...@gmail.com I built my system WITHOUT_LEGACY_CONSOLE about a week ago. Now, rebuilding world again on that system fails. (On a side note, I see no indication of what's causing the error unless I build with -jN flag). root@euler:/usr/src # uname -a FreeBSD euler 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r358556: Tue Mar 3 02:50:36 CET 2020 root@euler:/usr/obj/usr/src/amd64.amd64/sys/EULER amd64 root@euler:/usr/src # make -j9 buildworld --- buildworld --- make[1]: "/usr/src/Makefile.inc1" line 323: SYSTEM_COMPILER: libclang will be built for bootstrapping a cross-compiler. make[1]: "/usr/src/Makefile.inc1" line 328: SYSTEM_LINKER: libclang will be built for bootstrapping a cross-linker. --- buildworld_prologue --- -- >>> World build started on Wed Mar 11 02:13:27 CET 2020 -- --- _worldtmp --- -- >>> Rebuilding the temporary build tree -- rm -rf /usr/obj/usr/src/amd64.amd64/tmp cd /usr/src/tools/build; make DIRPRFX=tools/build/ DESTDIR=/usr/obj/usr/src/amd64.amd64/tmp/legacy installdirs --- installdirs --- mkdir -p /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin /usr/obj/usr/src/amd64.amd64/tmp/legacy/lib/casper /usr/obj/usr/src/amd64.amd64/tmp/legacy/lib/geom /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include/casper /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/include/private/zstd /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/lib /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/libexec removing old non-symlink /usr/obj/usr/src/amd64.amd64/tmp/legacy/sbin removing old non-symlink /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin removing old non-symlink /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin ln -sfn bin /usr/obj/usr/src/amd64.amd64/tmp/legacy/sbin ln -sfn ../bin /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin ln -sfn ../bin /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin mkdir -p "/usr/obj/usr/src/amd64.amd64/tmp/legacy//usr/include/sys" mkdir -p "/usr/obj/usr/src/amd64.amd64/tmp/legacy//usr/include/casper" mkdir -p "/usr/obj/usr/src/amd64.amd64/tmp/legacy//usr/include/ufs/ufs" mkdir -p "/usr/obj/usr/src/amd64.amd64/tmp/legacy//usr/include/ufs/ffs" mkdir -p "/usr/obj/usr/src/amd64.amd64/tmp/legacy//usr/include/fs/msdosfs" mkdir -p "/usr/obj/usr/src/amd64.amd64/tmp/legacy//usr/include/sys/disk" cd /usr/src/tools/build; make DIRPRFX=tools/build/ DESTDIR=/usr/obj/usr/src/amd64.amd64/tmp/legacy host-symlinks --- host-symlinks --- Linking host tools into /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/basename -> /usr/bin/basename /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/bzip2 -> /usr/bin/bzip2 /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/bunzip2 -> /usr/bin/bunzip2 /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/chmod -> /bin/chmod /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/chown -> /usr/sbin/chown /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/cmp -> /usr/bin/cmp /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/comm -> /usr/bin/comm /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/cp -> /bin/cp /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/date -> /bin/date /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/dirname -> /usr/bin/dirname /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/echo -> /bin/echo /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/env -> /usr/bin/env /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/false -> /usr/bin/false /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/find -> /usr/bin/find /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/fmt -> /usr/bin/fmt /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/gzip -> /usr/bin/gzip /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/gunzip -> /usr/bin/gunzip /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/head -> /usr/bin/head /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/hostname -> /bin/hostname /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/id -> /usr/bin/id /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/ln -> /bin/ln /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/ls -> /bin/ls /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/mkdir -> /bin/mkdir /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/mv -> /bin/mv /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/nice -> /usr/bin/nice /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/patch -> /usr/bin/patch /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/rm -> /bin/rm /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin/realpath -> /bin/realpath /usr/obj/usr/
[Bug 244729] Buildworld fails when installed world is built WITHOUT_LEGACY_CONSOLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244729 ktulla...@gmail.com changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2308 ||38 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
