[Bug 242070] scp on 12.1p1-RELEASE is painfully slow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242070 Bug ID: 242070 Summary: scp on 12.1p1-RELEASE is painfully slow Product: Base System Version: 12.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: o...@oz42.eu scp on 12.1p1-RELEASE is painfully slow: 2% 80KB 4.5KB/s 11:25 ETA Network is 10 GBit/s (both hosts are on ESXi). net.inet.tcp.cc.algorithm is newreno (default). No firewall, scp client is on the same network. -- 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 Masachika ISHIZUKA changed: What|Removed |Added CC||i...@amail.plala.or.jp --- Comment #18 from Masachika ISHIZUKA --- I'm using zfs on vps with very small rams (512mb). It was good operating on 10.3R, 11.0R, 11.1R, 11.2R and 12.0R. Recently, I upgraded to 12.1R and many processes were killed because of 'out of swap space' but no 'swap_pager_getswapspace failed'. So, I set 'sysctl vm.pageout_oom_seq=1024' on /boot/loader.conf and this reduced killed processes. Now, I'm watching the situation by increasing 1024 to 10240. -- 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 242072] netstat -sp pfkey is broken
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242072 Bug ID: 242072 Summary: netstat -sp pfkey is broken Product: Base System Version: 11.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: jean-francois.h...@stormshield.eu netstat -sp pfkey returns nothing. After some investigation this commit (https://svnweb.freebsd.org/base?view=revision&revision=323016) is the culprit. kresolve_list() should be called even on live system since some protocols like pfkey need the resolved values. -- 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 242056] bsnmpd: ipv4 addresses in begemotSnmpdTransInetStatus table are reversed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242056 Andrey V. Elsukov changed: What|Removed |Added Assignee|b...@freebsd.org|a...@freebsd.org Status|New |In Progress CC||a...@freebsd.org --- Comment #1 from Andrey V. Elsukov --- Created attachment 209245 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209245&action=edit Proposed patch Hello, can you test this patch? -- 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 242067] libc: r354823 riscv64 has a fault in printf() where IEEE754-2008 fp128 data is output wrong
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242067 --- Comment #4 from Dennis Clarke --- (In reply to Kubilay Kocak from comment #3) The output should be the valid IEEE754-2008 floating point representation for pi exactly the same as the Solaris 10 sparcv9 server does : ( 1 ) expected output should be in the last lines : b8 01 17 c5 8c 89 69 84 d1 42 44 b5 1f 92 00 40 pi may be 3.1415926535897932384626433832795028e+00 That would be precisely correct for a little endian RISC-V architecture. ( 2 ) actual output is very correct in memory and very wrong printf behavior : b8 01 17 c5 8c 89 69 84 d1 42 44 b5 1f 92 00 40 pi may be 2.076405016834831430856216761921e+00 # So I don't think that pi is that close to 2.0764... :) The other question is have I ever seen this work ? The answer is no. Sadly I have never seen this work correctly. The output here suggests that the printf() routine correctly handles the static format string seen in the assembly listing at LC46 in that we do get the correct number of ascii digits in the correct places however the in memory little endian fp128 data is not handled well. The text [1]"Handbook of Floating-Point Arithmetic", 2nd Ed, pg48, by Muller, J.-M., Brunie, N., de Dinechin, F., Jeannerod, C.-P., Joldes, M., Lefèvre, V., Melquiond, G., Revol, N., Torres, S. states that the 128 bit floating point format should have a single sign bit, a set of 15 exponent bits and then a mantissa or significand of 112 bits wherein there is an implied leading "1" bit for an effective 113 bit significand. The IEEE 754-1985 standard did not define this format whereas the [2]IEEE 754-2008 standard does. This is well implemented in Solaris and OpenSolaris as well as on IBM Power9 systems running Red Hat Enterprise Linux. I have single stepped through the relevant lines of the code on an IBM Power system and I think the issue is with /lib/libc/stdio/vfprintf.c where the in memory data is handled wrongly. I have a theory on why we are seeing a value near 2.0 but have to work on that yet. [1] https://www.springer.com/gp/book/9783319765259 [2] IEEE Computer Society. IEEE Standard for Floating-Point Arithmetic. IEEE Standard 754-2008, August 2008. also ISBN: 978-0-7381-5752-8 https://ieeexplore.ieee.org/document/4610935 -- 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 242067] libc: r354823 riscv64 has a fault in printf() where IEEE754-2008 fp128 data is output wrong
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242067 --- Comment #5 from Dennis Clarke --- The output from the Solaris 10 sparcv9 server is clearly to be big endian however for claity I simply want to point out that the RISC-V architecture is little endian and that the in memory data is precisely correct. Regardless we should never see a value of pi as 2.... -- 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 242081] dhclient doesn't exit on link down event, and devd is only configured to start dhclient on link up.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242081 Bug ID: 242081 Summary: dhclient doesn't exit on link down event, and devd is only configured to start dhclient on link up. Product: Base System Version: 11.3-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Some People Priority: --- Component: conf Assignee: b...@freebsd.org Reporter: m...@latt.net dhclient does not exit when interfaces transition down, it merely unconfigures the last lease on that interface, then sits there. As devd.conf is only configured to start dhclient on link up events, not restart dhclient if it's running, this causes hosts to fall off the network (dhclient is running but does not do anything but poll() -- there may be a bug in the state machine handling?) I've been able to work around it for now by adding a devd.conf entry that stops dhclient on link down events, causing the link up start entry to work properly. Some options: 1) dhclient is fixed to exit correctly (as documented in the man page.) - This might be some sort of state machine handling bug that would be worth digging into. 2) devd.conf's link up entry is modified to perform a restart, rather than a start, to allow it to function if dhclient is still running. 3) devd.conf as shipped has a link down entry that stops dhclient. -- 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 241118] [boot] 12.1-BETA3 installer hangs before loader menu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241118 --- Comment #23 from Chris R --- Just commenting to confirm that the work-around I'm currently using is to copy the /boot/loader and /boot/loader.efi from 12.0-RELEASE into my /boot. This is definitely a regression in the loader since 12.0-RELEASE. -- 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 241831] freebsd-update from 11.3 to 12.1 causes error messages "Directory not empty"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241831 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #2 from Ed Maste --- Confirmed with 11.2->12.1 update, root@twelve:~ # freebsd-update install src component not installed, skipped Installing updates...rmdir: ///var/db/etcupdate/current/usr/share/openssl/man/en.ISO8859-1: Directory not empty rmdir: ///var/db/etcupdate/current/usr/share/openssl/man: Directory not empty rmdir: ///var/db/etcupdate/current/usr/share/openssl: Directory not empty rmdir: ///var/db/etcupdate/current/usr/share/man/en.UTF-8: Directory not empty rmdir: ///var/db/etcupdate/current/usr/share/man/en.ISO8859-1: Directory not empty rmdir: ///var/db/etcupdate/current/usr/share/man: Directory not empty done. -- 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 242087] aacraid
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242087 Bug ID: 242087 Summary: aacraid Product: Base System Version: 12.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: i...@itn.ru Created attachment 209257 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209257&action=edit Patch solves problems I am using Adaptec 6805e with 8 disks without arrays. In FreeBSD9, I used the driver from the Adaptec site. When migrating to FreeBSD10 or later, I switched to the system aacraid. All disks from the controller disappeared in the system and passX devices remained. Patch solves these problems, I use it on 12.1-STABLE for three months (I also tested it on 11-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 231172] [sshd] ssh login fails if server is set sysctl kern.trap_enotcap=1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231172 Ed Maste changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2347 ||93 -- 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 241918] make buildworld fails: freebsd.cf: No such file or directory
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241918 Mark Millard changed: What|Removed |Added CC||marklmi26-f...@yahoo.com --- Comment #2 from Mark Millard --- (In reply to oklaspec from comment #1) Quoting the build man page: MAKEOBJDIRPREFIX Defines the prefix for directory names in the tree of built objects. Defaults to /usr/obj if not defined. This variable should only be set in the environment or /etc/src-env.conf and not via /etc/make.conf or /etc/src.conf or the command line. Note that last: not to be set in the command line (after "make"). So: make MAKEOBJDIRPREFIX=/usr/obj DESTDIR=/home/rj/RELENG_12_1.tmpl distrib-dirs distribution is inappropriate. Possibly presuming a specific shell type: env MAKEOBJDIRPREFIX=/usr/obj make DESTDIR=/home/rj/RELENG_12_1.tmpl distrib-dirs distribution would be appropriate (set in the environment) . You may wat to try that. -- 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 241714] /usr/bin/diff --tabsize dies with SIGSEGV
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241714
pproca...@gmail.com changed:
What|Removed |Added
CC||pproca...@gmail.com
--- Comment #3 from pproca...@gmail.com ---
tabsize is set to have an optional argument.
I can't explain why as it seems to me it always require an argument.
This patch here makes tabsize require an argument which also solves the problem
of the SEGfault as line 255 of diff.c is expecting optarg to be something.
--- diff.c.orig 2019-11-20 01:16:41.377456000 -0500
+++ diff.c 2019-11-20 01:16:51.17640 -0500
@@ -90,7 +90,7 @@
{ "no-ignore-file-name-case", no_argument,NULL,
OPT_NO_IGN_FN_CASE },
{ "normal", no_argument,NULL,
OPT_NORMAL },
{ "strip-trailing-cr", no_argument,NULL,
OPT_STRIPCR },
- { "tabsize",optional_argument, NULL,
OPT_TSIZE },
+ { "tabsize",required_argument, NULL,
OPT_TSIZE },
{ "changed-group-format", required_argument, NULL,
OPT_CHANGED_GROUP_FORMAT},
{ NULL, 0, 0, '\0'}
};
--
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 242087] aacraid: with system aacraid instead of vendor aacraid, all disks from the controller disappeared
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242087 Mark Linimon changed: What|Removed |Added Keywords||patch Summary|aacraid |aacraid: with system ||aacraid instead of vendor ||aacraid, all disks from the ||controller disappeared -- 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 242072] netstat -sp pfkey is broken
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242072 Mark Linimon changed: What|Removed |Added CC||b...@freebsd.org --- Comment #1 from Mark Linimon --- Cc: committer of svn rev in question. -- 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 242070] scp on 12.1p1-RELEASE is painfully slow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242070 Mark Linimon changed: What|Removed |Added Keywords||regression 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 242087] aacraid: with system aacraid instead of vendor aacraid, all disks from the controller disappeared
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242087 Andriy Gapon changed: What|Removed |Added CC||ac...@freebsd.org --- Comment #1 from Andriy Gapon --- I believe that the code is self-consistent as it was designed. You can question whether the design is sane, but that's a different story. By default the driver exposes only logical disks. If you want it to expose physical devices you need to set '8' (3rd bit) in its flags. And, of course, a part of the problem is that this is not documented. -- 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"
