[Bug 231457] Out of swap space on ZFS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231457 --- Comment #12 from di...@dz.dn.ua --- I check and made sure that 12.0-RELEASE/amd64 is also affected by this problem, test tool and sendmail processes was killed by OOM after physical memory is over and several megabytes of swap were used. Short hardware details: CPU: Intel(R) Celeron(R) CPU 847 @ 1.10GHz (1097.53-MHz K8-class CPU) real memory = 2147483648 (2048 MB) avail memory = 1987403776 (1895 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) da0: Removable Direct Access SPC-4 SCSI device da0: 14663MB (30031250 512 byte sectors) You can a very simple test on your hardware or VM: 1. Install system from DVD to cleaned drive in "Auto (ZFS)" mode. 2. Comment GPT swap entry (created by installer) in /etc/fstab. 3. Create swap space on ZFS pool: # zfs create -V 8GB -o org.freebsd:swap=on zroot/swap 4. Reboot. 5. Compile and use "Memory occupation test tool" from bug report attachments: # ./memphage 9500 Argument is memory occupation limit (mem free + swap free - 500) in megabytes. -- 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 219846] [panic] [kevent] mutex nm_kn_lock not owned, netmap with INVARIANTS+WITNESS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219846 Vincenzo Maffione changed: What|Removed |Added Status|New |Open CC||vmaffi...@freebsd.org --- Comment #3 from Vincenzo Maffione --- I still have to setup a test environment for this bug, but please note that now stable/11 contains the latest netmap code (as well as stable/12 and HEAD). -- 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 231457] Out of swap space on ZFS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231457 --- Comment #11 from di...@dz.dn.ua --- Created attachment 201015 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201015=edit Memory occupation test tool -- 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 234846] [lagg] race condition when adding port
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234846 Bug ID: 234846 Summary: [lagg] race condition when adding port Product: Base System Version: 11.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: alexandre.mart...@stormshield.eu Greetings, I'm facing some random crash when I'm adding a port into an LACP aggregate. In the coredump, I found that the crash is due to a race condition when the interface is added to the aggregate. The condition is the following: The thread 1 (ifconfig lagg0 laggport em0) is adding an interface to an LACP aggregate. The code enter the function lagg_port_create in the file if_lagg.c. That function "publish" an update of the interface with the following code: /* Change the interface type */ lp->lp_iftype = ifp->if_type; ifp->if_type = IFT_IEEE8023ADLAG; ifp->if_lagg = lp; lp->lp_ioctl = ifp->if_ioctl; ifp->if_ioctl = lagg_port_ioctl; lp->lp_output = ifp->if_output; ifp->if_output = lagg_port_output; In the thread 2, thereafter that publication, a packet come on the interface em0, use the new state of the interface, so lagg_input_p is called. Because the setup of the LACP is not finished (the call to lagg_proto_addport is after the publication), the LACP code uses a NULL pointer and the kernel crashes. Can I change the code of the lagg_port_create function and put the "publication" of the new state of the interface at the end of the function ? Best regards, Alexandre -- 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 230465] ixl: not working in netmap mode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230465 --- Comment #5 from Charles Goncalves --- (In reply to Vincenzo Maffione from comment #4) Hello Vincenzo, thank you for your answer! I was running tests in FreeBSD 11.2 STABLE. For coming months I'll upgrade to 12.0 STABLE. -- 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 234846] [lagg] race condition when adding port
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234846 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@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 234838] ena drop-outs on 12.0-RELEASE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234838 --- Comment #3 from Leif Pedersen --- Just fyi, I updated to 12.0-RELEASE-p2, which I saw had announced a fix for networking. Over night, the problem appeared again twice, so apparently that didn't fix it. Jan 11 02:03:21 db1 kernel: ena_com_prepare_tx() [TID:100482]: Not enough space in the tx queue Jan 11 02:03:21 db1 kernel: Jan 11 02:03:21 db1 kernel: ena0: failed to prepare tx bufs Jan 11 03:03:54 db1 kernel: ena_com_prepare_tx() [TID:100385]: Not enough space in the tx queue Jan 11 03:03:54 db1 kernel: Jan 11 03:03:54 db1 kernel: ena0: failed to prepare tx bufs -- 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 234874] pf: pfr_update_stats: assertion failed.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234874 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@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 234567] FreeBSD 12.0: periodically panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234567 --- Comment #8 from Martin Birgmeier --- Hi Mark, Thank you for your reply. I have prepared an encrypted compressed file, unfortunately I do not have a webspace where I could host it. It has 51 MB. Would you happen to have somewhere I could upload this? I would then send you the PW via mail. -- Martin -- 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 234874] pfr_update_stats: assertion failed.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234874 Bug ID: 234874 Summary: pfr_update_stats: assertion failed. Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: rozhuk...@gmail.com To many messages, bad user experience: Jan 11 17:00:05 firewall kernel: pfr_update_stats: assertion failed. Jan 11 17:00:43 firewall syslogd: last message repeated 36 times Jan 11 17:02:48 firewall syslogd: last message repeated 194 times Jan 11 17:12:41 firewall syslogd: last message repeated 2723 times Jan 11 17:22:45 firewall syslogd: last message repeated 12772 times Remove this message, or fix, or make it only if some debug is on. -- 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 234874] pf: pfr_update_stats: assertion failed.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234874 rozhuk...@gmail.com changed: What|Removed |Added Summary|pfr_update_stats: assertion |pf: pfr_update_stats: |failed. |assertion failed. -- 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 234885] cmp(1) Capsicum error if stdin closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234885 Bug ID: 234885 Summary: cmp(1) Capsicum error if stdin closed Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: na...@freebsd.org cmp(1) errors out with a Capsicum error when called with stdin closed: $ sh -c 'cmp /bin/ls /bin/cat <&-' cmp: /bin/ls: Capabilities insufficient Since fd 0 is closed, open() of the first file argument returns fd=0, and a subsequent fstat(0, ...) produces the error. I found this because GNU tar 1.31's test suite includes some test scripts that, for whatever reason, close stdin (exec <&-) and later call cmp. -- 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 234454] ar produces corrupt .a archive when >4GB
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234454 --- Comment #4 from commit-h...@freebsd.org --- A commit references this bug: Author: emaste Date: Fri Jan 11 19:53:45 UTC 2019 New revision: 342950 URL: https://svnweb.freebsd.org/changeset/base/342950 Log: MFC r342575, r342580: ar: detect and error out on 32-bit symbol table overflow BSD ar currently does not support the /SYM64/ 64-bit symbol table, and previously truncated to 32-bits, silently producing corrupted archives larger than 4GB. PR: 234454 Changes: stable/11/usr.bin/ar/write.c -- 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 234886] shutdown not installed with setuid bit in pkgbase
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234886 Bug ID: 234886 Summary: shutdown not installed with setuid bit in pkgbase Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: ema...@freebsd.org CC: kmo...@freebsd.org As reported by kmoore in https://lists.freebsd.org/pipermail/freebsd-pkgbase/2017-December/000350.html: > Anybody else noticed a recent regression (say past month or so) where > pkg base of latest HEAD is now failing to throw setuid on some files? We > saw it at first because /sbin/shutdown lost its setuid bit, so users > can't shutdown the box. I investigated and found that it appears to be due to the way install(1) handles links with -M (https://lists.freebsd.org/pipermail/freebsd-pkgbase/2017-December/000361.html): For regular installs we invoke: install -l h and the link then has the same permissions via the existing inode. With -M install produces a metalog containing ./ type=file mode=0755 size=0 (i.e., permissions not explicitly set) and we end up with two entries in the metalog referencing two names for the same inode, but with different permissions. If we passed in the mode when invoking install for a hardlink we should have the expected permissions, regardless of sorting: # install -M METALOG -m4554 -l h ./ type=file mode=04554 size=0 On a positive note there are only a few Makefiles with LINKS as well as BINOWN, BINMODE, or BINGRP. As far as I can tell: release/picobsd/tinyware/passwd/Makefile sbin/shutdown/Makefile usr.bin/at/Makefile usr.sbin/authpf/Makefile And after that email was sent, also stand/efi/loader/Makefile and stand/i386/loader/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 234567] FreeBSD 12.0: periodically panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234567 --- Comment #9 from Mark Johnston --- (In reply to Martin Birgmeier from comment #8) I don't have anything handy. Can you share it via google drive? If not, please mail me and we'll figure something out. -- 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 234454] ar produces corrupt .a archive when >4GB
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234454 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: emaste Date: Fri Jan 11 19:49:19 UTC 2019 New revision: 342949 URL: https://svnweb.freebsd.org/changeset/base/342949 Log: MFC r342575, r342580: ar: detect and error out on 32-bit symbol table overflow BSD ar currently does not support the /SYM64/ 64-bit symbol table, and previously truncated to 32-bits, silently producing corrupted archives larger than 4GB. PR: 234454 Changes: _U stable/12/ stable/12/usr.bin/ar/write.c -- 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 234886] shutdown not installed with setuid bit in pkgbase
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234886 Ed Maste changed: What|Removed |Added Keywords||pkgbase -- 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 233751] BSD_CRTBEGIN does not work on powerpc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233751 Justin Hibbits changed: What|Removed |Added Assignee|b...@freebsd.org|jhibb...@freebsd.org Status|New |In Progress --- Comment #5 from Justin Hibbits --- Review available at https://reviews.freebsd.org/D18826 -- 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 223957] man page for pf.conf references pflow(4) which doesn't exist.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223957 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: kp Date: Sat Jan 12 05:38:48 UTC 2019 New revision: 342955 URL: https://svnweb.freebsd.org/changeset/base/342955 Log: MFC r342784: pf: Remove references to pflow from the pf.conf man page pflow no longer exists. It was removed as part of a pf update back in 2012 (r240233). PR: 223957 Changes: _U stable/12/ stable/12/share/man/man5/pf.conf.5 -- 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 223957] man page for pf.conf references pflow(4) which doesn't exist.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223957 Kristof Provost changed: What|Removed |Added Resolution|--- |FIXED Status|Open|Closed -- 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 223957] man page for pf.conf references pflow(4) which doesn't exist.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223957 --- Comment #4 from commit-h...@freebsd.org --- A commit references this bug: Author: kp Date: Sat Jan 12 05:44:10 UTC 2019 New revision: 342956 URL: https://svnweb.freebsd.org/changeset/base/342956 Log: MFC r342784: pf: Remove references to pflow from the pf.conf man page pflow no longer exists. It was removed as part of a pf update back in 2012 (r240233). PR: 223957 Changes: _U stable/11/ stable/11/share/man/man5/pf.conf.5 -- 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"
