[Bug 233341] 12.0-RC1 i386 vnet does not behave like the amd64 vnet version.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233341 --- Comment #4 from Kristof Provost --- (In reply to Joe Barbish from comment #3) Please check with tcpdump on bridge0/xl0 to see if you actually see that traffic there too. I'll try to reproduce the panic on shutdown. That does look like a pflog 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 230747] [patch] Minor nit in ipfw(8) manpage
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230747 Guangyuan Yang changed: What|Removed |Added Status|New |In Progress Assignee|b...@freebsd.org|y...@freebsd.org CC||y...@freebsd.org -- 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 232458] jevents: Program terminated with signal 11, Segmentation fault when build word of 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232458 iron.ud...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|New |Closed --- Comment #2 from iron.ud...@gmail.com --- It was fixed somewhere between r339445 and r340717. -- 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 115631] [libc] [patch] [request] make dlclose(3) atexit-aware
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=115631 --- Comment #8 from Bryan Drewery --- *Very naive and untested*. It seems like we need something like this: diff --git lib/libc/stdlib/atexit.c lib/libc/stdlib/atexit.c index bc9ad3ebd7bf..8df6cd4e31b0 100644 --- lib/libc/stdlib/atexit.c +++ lib/libc/stdlib/atexit.c @@ -125,6 +125,8 @@ atexit_register(struct atexit_fn *fptr) return 0; } +extern void *__dso_handle __hidden; + /* * Register a function to be performed at exit. */ @@ -137,7 +139,7 @@ atexit(void (*func)(void)) fn.fn_type = ATEXIT_FN_STD; fn.fn_ptr.std_func = func; fn.fn_arg = NULL; - fn.fn_dso = NULL; + fn.fn_dso = __dso_handle; error = atexit_register(); return (error); -- 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 115631] [libc] [patch] [request] make dlclose(3) atexit-aware
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=115631 --- Comment #7 from Bryan Drewery --- The patch here is interesting but not something that should be committed. A real solution should be committed that prevents a crash. Perhaps making atexit() aware that it is being called from a dso and properly registering that dso in atexit_register(), etc. -- 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 115631] [libc] [patch] [request] make dlclose(3) atexit-aware
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=115631 --- Comment #6 from Bryan Drewery --- Old discussion here: https://freebsd-arch.freebsd.narkive.com/zzyHX3Bw/dlclose-vs-atexit glibc handles this: Linux notes Since glibc 2.2.3, atexit() (and on_exit(3)) can be used within a shared library to establish functions that are called when the shared library is unloaded. -- 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 233341] 12.0-RC1 i386 vnet does not behave like the amd64 vnet version.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233341 --- Comment #3 from Joe Barbish --- I don't disagree that the traffic looks like a device announcing itself using the Simple Service Discovery Protocol. Thanks for identifying what it is. The problem is it never ends. The log file is flooded until it fills up and then rotates. This is not happening on amd64 system and if I use ipfw on the host and vnet jail this also does't happen. That is the problem. Cut the following out of the vmcore dump. Hope its what you want. in6_purgeaddr: err=65, destination address delete failed Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x2f9528c8 fault code = supervisor read, page not present instruction pointer = 0x20:0x18c0f2c0 stack pointer = 0x28:0x16614b6c frame pointer = 0x28:0x16614b74 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (thread taskq) trap number = 12 panic: page fault cpuid = 0 time = 1542749869 KDB: stack backtrace: #0 0x11080cf at kdb_backtrace+0x4f #1 0x10bb097 at vpanic+0x147 #2 0x10baf4b at panic+0x1b #3 0x16910a5 at trap_fatal+0x395 #4 0x16910e3 at trap_pfault+0x33 #5 0x169072f at trap+0x3cf #6 0xffc0315d at PTDpde+0x4165 #7 0x11b9a06 at if_clone_destroyif+0x1a6 #8 0x11ba17c at if_clone_detach+0xbc #9 0x18c0f441 at vnet_pflog_uninit+0x21 #10 0x11dfaeb at vnet_destroy+0x10b #11 0x1083da4 at prison_deref+0x284 #12 0x1119c59 at taskqueue_run_locked+0x189 #13 0x111ae07 at taskqueue_thread_loop+0x97 #14 0x107c731 at fork_exit+0x71 #15 0xffc033ba at PTDpde+0x43c2 -- 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 232786] ipfw.8: fix allowed DSCP values range. 0..64 -> 0..63
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232786 Guangyuan Yang changed: What|Removed |Added CC||y...@freebsd.org Assignee|b...@freebsd.org|y...@freebsd.org Status|New |In Progress -- 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 233362] Building riscv with BSD_CRTBEGIN fails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233362 Bug ID: 233362 Summary: Building riscv with BSD_CRTBEGIN fails Product: Base System Version: CURRENT Hardware: riscv OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: ema...@freebsd.org /usr/local/bin/riscv64-unknown-freebsd11.2-ld: /scratch/tmp/emaste/obj/scratch/tmp/emaste/freebsd/riscv.riscv64/tmp/usr/lib/crtbeginS.o: can't link hard-float modules with soft-float modules /usr/local/bin/riscv64-unknown-freebsd11.2-ld: failed to merge target specific data of file /scratch/tmp/emaste/obj/scratch/tmp/emaste/freebsd/riscv.riscv64/tmp/usr/lib/crtbeginS.o collect2: error: ld returned 1 exit status -- 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 233361] mips build with BSD_CRTBEGIN, Clang, LLD fails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233361 Ed Maste changed: What|Removed |Added Hardware|Any |mips -- 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 233361] mips build with BSD_CRTBEGIN, Clang, LLD fails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233361 Bug ID: 233361 Summary: mips build with BSD_CRTBEGIN, Clang, LLD fails Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: ema...@freebsd.org >From _.mips.mips.buildworld (mips* same): --- crtbeginS.o --- :9:1: error: no .cprestore used in PIC mode [-Werror,-Winline-asm] jal __do_global_dtors_aux ^ :18:1: error: no .cprestore used in PIC mode [-Werror,-Winline-asm] jal register_classes ^ _.mips.mips64.buildworld (mips64* same): /scratch/tmp/emaste/obj/scratch/tmp/emaste/freebsd/mips.mips64/tmp/usr/bin/ld: /scratch/tmp/emaste/obj/scratch/tmp/emaste/freebsd/mips.mips64/tmp/usr/lib/crtbeginS.o: CALL16 reloc at 0x18 not against global symbol /scratch/tmp/emaste/obj/scratch/tmp/emaste/freebsd/mips.mips64/tmp/usr/lib/crtbeginS.o: could not read symbols: Bad value cc: error: linker command failed with exit code 1 (use -v to see invocation) _.mips.mipsn32.buildworld: /scratch/tmp/emaste/obj/scratch/tmp/emaste/freebsd/mips.mipsn32/tmp/usr/bin/ld: /scratch/tmp/emaste/obj/scratch/tmp/emaste/freebsd/mips.mipsn32/tmp/usr/lib/crtbeginS.o: CALL16 reloc at 0x14 not against global symbol /scratch/tmp/emaste/obj/scratch/tmp/emaste/freebsd/mips.mipsn32/tmp/usr/lib/crtbeginS.o: could not read symbols: Bad value cc: error: linker command failed with exit code 1 (use -v to see invocation) -- 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 233359] PkgBase: make packages doesn't include version information
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233359 --- Comment #1 from Sylvain Garrigues --- make -C release MK_AUTO_OBJ=no -V BRANCH gives me "PRERELEASE" The EXTRA_VERSION timestamp suffix is appended to package names when we are on a BRANCH which iS STABLE or CURRENT or ALPHA. There is the bug :) -- 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 233359] PkgBase: make packages doesn't include version information
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233359 Bug ID: 233359 Summary: PkgBase: make packages doesn't include version information Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: sylv...@sylvaingarrigues.com Created attachment 199390 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=199390=edit make packages output On -CURRENT, running `make packages' used to print things like: ===> Creating FreeBSD-runtime-12.0.sSomeTimeStamp Now I switched to stable/12 and I don't see any version or timestamp in package names: ===> Creating FreeBSD-runtime-12.0 Plus a lot of "pkg: duplicate directory listing: ..., ignoring" Please see attached log. As a consequence, I cannot update my remote systems as `pkg upgrade` don't feel the need to upgrade packages with the same version. However, it sees the new packages. [root@home ~]# pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-base repository catalogue... Fetching meta.txz: 100%260 B 0.3kB/s00:01 Fetching packagesite.txz: 100% 16 KiB 16.4kB/s00:01 Processing entries: 100% FreeBSD-base repository update completed. 214 packages processed. All repositories are up to date. Checking for upgrades (3 candidates): 100% Processing candidates (3 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [root@home ~]# -- 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 233341] 12.0-RC1 i386 vnet does not behave like the amd64 vnet version.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233341 --- Comment #2 from Kristof Provost --- (In reply to Joe Barbish from comment #1) That traffic looks like you've got a device announcing itself using the Simple Service Discovery Protocol. I'm pretty sure that if you tcpdump on bridge0 on the host you'd see the traffic too. (And that's why the vnet jail sees it.) That's almost certainly not a bug. Do you have a backtrace for the panic on shutdown? -- 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 233345] 12.0-RC1 - Autoloading module - message displayed too many times
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233345 Conrad Meyer changed: What|Removed |Added Version|12.0-STABLE |CURRENT CC||c...@freebsd.org -- 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 233094] [meta] Base system tool chain modernization tracking
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233094 --- Comment #2 from commit-h...@freebsd.org --- A commit references this bug: Author: emaste Date: Tue Nov 20 16:54:43 UTC 2018 New revision: 340681 URL: https://svnweb.freebsd.org/changeset/base/340681 Log: stand: remove CLANG_NO_IAS from btx and gptboot Many components under stand/ had CLANG_NO_IAS added when Clang's Integrated Assembler (IAS) did not handle .codeNN directives. Clang gained support quite some time ago, and we can now build stand/ with IAS. Note that in some cases there are small differences in the generated output, so CLANG_NO_IAS should be removed only after testing (or after finding no differences in the output). PR: 205250, 233094 Sponsored by: The FreeBSD Foundation Changes: head/stand/i386/btx/btx/Makefile head/stand/i386/btx/btxldr/Makefile head/stand/i386/gptboot/Makefile -- 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 233355] 12.0-RC1 vt(4) has no boot time splash screen support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233355 Tobias Kortkamp changed: What|Removed |Added Status|New |Closed Resolution|--- |DUPLICATE --- Comment #2 from Tobias Kortkamp --- *** This bug has been marked as a duplicate of bug 210432 *** -- 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 233094] [meta] Base system tool chain modernization tracking
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233094 Ed Maste changed: What|Removed |Added See Also||https://bugs.llvm.org/show_ ||bug.cgi?id=39101 -- 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 233094] [meta] Base system tool chain modernization tracking
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233094 Ed Maste changed: What|Removed |Added See Also||https://bugs.llvm.org/show_ ||bug.cgi?id=33647 -- 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 233355] 12.0-RC1 vt(4) has no boot time splash screen support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233355 --- Comment #1 from Joe Barbish --- Same effect in amd64 or i386 systems. -- 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 233094] [meta] Base system tool chain modernization tracking
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233094 Ed Maste changed: What|Removed |Added See Also||https://bugs.llvm.org/show_ ||bug.cgi?id=32462 -- 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 233094] [meta] Base system tool chain modernization tracking
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233094 Ed Maste changed: What|Removed |Added See Also||https://bugs.llvm.org/show_ ||bug.cgi?id=25525 -- 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 233356] 12.0-RC1 vt(4) doesn't support rc.conf parameters saver= or blanktime=
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233356 Bug ID: 233356 Summary: 12.0-RC1 vt(4) doesn't support rc.conf parameters saver= or blanktime= Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: qja...@a1poweruser.com The vt default console screen driver doesn't support the rc.conf parameters saver= or blanktime=. The boot time console messages has this message, Configuring vt: blanktime screensaver But really has no effect. rc.conf contains saver="warp" & blanktime="900" If kern.vty=sc in /boot/loader.conf then they work. -- 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 233355] 12.0-RC1 vt(4) has no boot time splash screen support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233355 Bug ID: 233355 Summary: 12.0-RC1 vt(4) has no boot time splash screen support Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: qja...@a1poweruser.com The Boot time splash screen function does not work in vt(4) the OS default console screen. This works fine using kern.vty=sc Have this in loader.conf splash_bmp_load="YES" bitmap_name="/boot/splash.bmp" bitload_load="YES" -- 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 231325] rescue/sh check failed, installation aborted
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231325 --- Comment #7 from Ed Maste --- (In reply to Kubilay Kocak from comment #4) > BYPASS_INSTALLCHECK_SH=yes gets installworld further, which later fails at: Note that I added the installworld rescue test explicitly to make sure a working rescue will exist after the install in case it's needed for recovery. BYPASS_INSTALLCHECK_SH should only be used if you have some other way to recover (a ZFS boot environment, alternate boot media, etc.) -- 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 228858] panic when delivering knote to a process who has opened a kqueue() is dying
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228858 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: pho Date: Tue Nov 20 09:30:26 UTC 2018 New revision: 340665 URL: https://svnweb.freebsd.org/changeset/base/340665 Log: Added a kevent(2) test. PR: 228858 Sponsored by: Dell EMC Isilon Changes: user/pho/stress2/misc/kevent12.sh -- 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 233345] 12.0-RC1 - Autoloading module - message displayed too many times
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233345 Bug ID: 233345 Summary: 12.0-RC1 - Autoloading module - message displayed too many times Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: verma...@interia.pl Created attachment 199368 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=199368=edit BUG screenshot Hi, the attached photo/screenshot shows the problem of mutiple same messages being displayed. Instead all needed modules should be displayed only once, like that: Autoloading module: uhid.ko Autoloading module: ums.ko Autoloading module: umodem.ko Autoloading module: if_cdce.ko Regards. -- 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"
