[Bug 192528] pwd_mkdb fails if /etc/shells contains duplicates
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192528 Kyle Evanschanged: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|kev...@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 226154] zfs compile error
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226154 Andriy Gaponchanged: What|Removed |Added Resolution|--- |Unable to Reproduce Status|New |Closed --- Comment #3 from Andriy Gapon --- (In reply to Ofloo from comment #2) With all due respect, it doesn't happen either for me or for automatic builds infrastructure. And from the lack of "me too"-s I guess that it doesn't happen for anyone else but you. So, please follow my advice from comment #1. -- 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 225450] 11.1-* panics on AMD Opteron 2k due to EARLY_AP_STARTUP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225450 --- Comment #20 from John Baldwin--- Grrr, not sure why my patch didn't prevent it from recursing. You could try '|| cold' instead of '|| n == 1' perhaps. You could also try changing the 'DELAY(1)' in _mtx_lock_indefinite_check() in sys/kern/kern_mutex.c to be something like 'if (cold) cpu_spinwait(); else DELAY(1);' instead of the 'n == 1' hack. Oh, I see why 'n == 1' didn't help. The early_delay callback that is used when that 'n == 1' check fails is i8254_delay (set in amd64/amd64/machdep.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 217149] seq(1) inconsistently omits 'last' when using float increment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149 --- Comment #17 from Conrad Meyer--- Ok, GNU seq basically takes the same approach as your comment #4 patch. So I've come around to 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 226154] zfs compile error
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226154 Ofloochanged: What|Removed |Added Resolution|Unable to Reproduce |--- Status|Closed |New --- Comment #2 from Ofloo --- happens on make buildworld removed /usr/obj and recompiled but gives same result # cat /etc/make.conf # Build all ports' -march against my cpu for best performance CPUTYPE?=native # Use clang instead of gcc, only needed for versions before 10.0 CC=clang CXX=clang++ CPP=clang-cpp NO_X=yes WITHOUT_X11=yes KERNCONF=OFL # cat OFL # # CUSTOM KERNEL # include GENERIC ident OFL options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_DEFAULT_TO_ACCEPT options DUMMYNET options IPDIVERT options CONSPEED=115200 # svn info Path: . Working Copy Root Path: /usr/src URL: https://svn0.eu.freebsd.org/base/stable/11 Relative URL: ^/stable/11 Repository Root: https://svn0.eu.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 330016 Node Kind: directory Schedule: normal Last Changed Author: hselasky Last Changed Rev: 330015 Last Changed Date: 2018-02-26 09:00:01 +0100 (Mon, 26 Feb 2018) echo zfs.full: /usr/obj/usr/src/tmp/usr/lib/libc.a /usr/obj/usr/src/tmp/usr/lib/libjail.a /usr/obj/usr/src/tmp/usr/lib/libnvpair.a /usr/obj/usr/src/tmp/usr/lib/libuutil.a /usr/obj/usr/src/tmp/usr/lib/libzfs_core.a /usr/obj/usr/src/tmp/usr/lib/libzfs.a >> .depend clang -O2 -pipe -I/usr/src/cddl/contrib/opensolaris/lib/libzpool/common -I/usr/src/cddl/compat/opensolaris/include -I/usr/src/cddl/compat/opensolaris/lib/libumem -I/usr/src/sys/cddl/compat/opensolaris -I/usr/src/cddl/contrib/opensolaris/head -I/usr/src/cddl/contrib/opensolaris/lib/libuutil/common -I/usr/src/cddl/contrib/opensolaris/lib/libzfs/common -I/usr/src/cddl/contrib/opensolaris/lib/libzfs_core/common -I/usr/src/cddl/contrib/opensolaris/lib/libumem/common -I/usr/src/cddl/contrib/opensolaris/lib/libnvpair -I/usr/src/sys/cddl/contrib/opensolaris/uts/common -I/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs -I/usr/src/sys/cddl/contrib/opensolaris/uts/common/sys -I/usr/src/sys/cddl/contrib/opensolaris/common/zfs -march=native -DNEED_SOLARIS_BOOLEAN -g -MD -MF.depend.zfs_main.o -MTzfs_main.o -std=gnu99 -fstack-protector-strong -Wno-pointer-sign -Wno-unknown-pragmas -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -c /usr/src/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c -o zfs_main.o /usr/src/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c:1353:9: warning: format specifies type 'unsigned long long' but the argument has type 'int64_t' (aka 'long') [-Wformat] cb.cb_snapused); ^~ /usr/src/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c:2095:15: warning: format specifies type 'unsigned long long' but the argument has type 'uint64_t' (aka 'unsigned long') [-Wformat] "%llu", cb->cb_version); ^~ %lu /usr/src/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c:2204:7: warning: format specifies type 'unsigned long long' but the argument has type 'uint64_t' (aka 'unsigned long') [-Wformat] cb.cb_numupgraded); ^ /usr/src/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c:2208:8: warning: format specifies type 'unsigned long long' but the argument has type 'uint64_t' (aka 'unsigned long') [-Wformat] cb.cb_numsamegraded); ^~~ /usr/src/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c:2571:54: warning: format specifies type 'unsigned long long' but the argument has type 'uint64_t' (aka 'unsigned long') [-Wformat] (void) snprintf(sizebuf, sizeof (sizebuf), "%llu", space); ^ %lu /usr/src/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c:2642:36: warning: format specifies type 'unsigned long long' but the argument has type 'uint64_t' (aka 'unsigned long') [-Wformat] (void) sprintf(valstr, "%llu", val64); ^ %lu /usr/src/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c:2650:37: warning: format
[Bug 199378] [patch] dhclient violates RFC2131 when sending early DHCPREQUEST message to re-obtain old IP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199378 David Brightchanged: What|Removed |Added Status|New |In Progress CC||d...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|d...@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 217149] seq(1) inconsistently omits 'last' when using float increment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217149 --- Comment #16 from fernando.apesteg...@gmail.com --- (In reply to Conrad Meyer from comment #15) I tried to pre-calculate the number of steps and iterate regardless of the cur<=last condition but it doesn't work either. I can't see how we can get rid of the rounding error by playing with the numbers. -- 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 184691] [patch] getty(8): remove leftovers from COMPAT_43 removal, sync man page
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184691 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: trasz Date: Mon Feb 26 17:51:19 UTC 2018 New revision: 330022 URL: https://svnweb.freebsd.org/changeset/base/330022 Log: Fix gettytab(5) to document f0, f1, and f2 as unsupported; they've been gone since r131091. PR: 184691 (partial) Submitted by: naddy@ MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Changes: head/libexec/getty/gettytab.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 226086] [nvme] Intel Optane 900P kernel panic when device is passed through ESXi (6.5)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226086 Wessel van Norelchanged: What|Removed |Added Resolution|--- |Not A Bug Status|New |Closed --- Comment #1 from Wessel van Norel --- I've updated the ESXi drivers for the nvme device and that solved the issue. https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESX65-INTEL-INTEL-NVME-1328=614 With this driver installed the FreeBSD current ISO boots. So this issue can be 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 226218] "r"eading into an empty ed(1) buffer doesn't set modified status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226218 Bug ID: 226218 Summary: "r"eading into an empty ed(1) buffer doesn't set modified status Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: free...@tim.thechases.com Created attachment 191017 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=191017=edit Remove the broken check for "addr != addr_last" in /usr/src/bin/ed/main.c To reproduce: $ ed r file.txt 314 q $ Expected behavior: $ ed r file.txt 314 q ? q $ which keeps it in line with the POSIX requirement http://pubs.opengroup.org/onlinepubs/009604599/utilities/ed.html "If the buffer has changed since the last time the entire buffer was written, the user shall be warned" Reading a file changes the buffer. Compare with the correct $ ed a x . q ? q $ where the buffer is changed and the "modified" flag is properly set. The solution appears to be to base "modified" purely on whether any lines were read in (addr > 0), regardless of whether "addr != addr_last" as performed by the attached 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 226217] if_qlxgb (QLogic cLOM8214) not working for me when configured via netif
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226217 Bug ID: 226217 Summary: if_qlxgb (QLogic cLOM8214) not working for me when configured via netif Product: Base System Version: 11.1-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: p...@pogotopia.net Hi, i got an QLogic cLOM8214 (if_qlxgb) which is working fine when i configure the interface manually: # uname -psr FreeBSD 11.1-RELEASE-p4 amd64 # ifconfig ql1 inet 192.168.200.5 netmask 255.255.255.0 up # ifconfig ql1 ql1: flags=8843metric 0 mtu 1500 options=8013b ether 8c:dc:d4:59:c1:6c hwaddr 8c:dc:d4:59:c1:6c inet 192.168.200.5 netmask 0xff00 broadcast 192.168.200.255 nd6 options=29 media: Ethernet autoselect (10Gbase-SR ) status: active # ping 192.168.200.10 PING 192.168.200.10 (192.168.200.10): 56 data bytes 64 bytes from 192.168.200.10: icmp_seq=0 ttl=255 time=0.304 ms 64 bytes from 192.168.200.10: icmp_seq=1 ttl=255 time=0.111 ms But it is not working when configured via netif: rc.conf: ifconfig_ql1="inet 192.168.200.5 netmask 255.255.255.0" # ifconfig ql1 after boot: ql1: flags=8843 metric 0 mtu 1500 options=8013b ether 8c:dc:d4:59:c1:6c hwaddr 8c:dc:d4:59:c1:6c inet 192.168.200.5 netmask 0xff00 broadcast 192.168.200.255 nd6 options=29 media: Ethernet autoselect (10Gbase-SR ) status: active # ping 192.168.200.10 PING 192.168.200.10 (192.168.200.10): 56 data bytes --- 192.168.200.10 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss # dmesg|grep ql1 ql1: mem 0xfb80-0xfb9f,0xfb7f-0xfb7f irq 31 at device 0.1 on pci8 ql1: qla_pci_attach: firmware[4.20.1.1429931003] ql1: Ethernet address: 8c:dc:d4:59:c1:6c ql1: qla_hw_send: (nsegs[1, 42, 0x0] > Q8_TX_MAX_SEGMENTS) ql1: link state changed to UP ql1: qla_dump_buf8: qla_hw_send: wrong pkt 0x2a dump start ql1: 0x: ff ff ff ff ff ff 8c dc d4 59 c1 6c 08 06 00 01 ql1: 0x0010: 08 00 06 04 00 01 8c dc d4 59 c1 6c c0 a8 c8 05 ql1: 0x0020: 00 00 00 00 00 00 c0 a8 c8 05 ql1: qla_dump_buf8: qla_hw_send: wrong pkt dump end ql1: qla_hw_send: (nsegs[1, 42, 0x0] > Q8_TX_MAX_SEGMENTS) ql1: qla_dump_buf8: qla_hw_send: wrong pkt 0x2a dump start ql1: 0x: ff ff ff ff ff ff 8c dc d4 59 c1 6c 08 06 00 01 ql1: 0x0010: 08 00 06 04 00 01 8c dc d4 59 c1 6c c0 a8 c8 05 ql1: 0x0020: 00 00 00 00 00 00 c0 a8 c8 0a ql1: qla_dump_buf8: qla_hw_send: wrong pkt dump end ql1: qla_hw_send: (nsegs[1, 42, 0x0] > Q8_TX_MAX_SEGMENTS) ql1: qla_dump_buf8: qla_hw_send: wrong pkt 0x2a dump start ql1: 0x: ff ff ff ff ff ff 8c dc d4 59 c1 6c 08 06 00 01 ql1: 0x0010: 08 00 06 04 00 01 8c dc d4 59 c1 6c c0 a8 c8 05 ql1: 0x0020: 00 00 00 00 00 00 c0 a8 c8 0a ql1: qla_dump_buf8: qla_hw_send: wrong pkt dump end ql1: qla_hw_send: (nsegs[1, 98, 0x0] > Q8_TX_MAX_SEGMENTS) ql1: qla_dump_buf8: qla_hw_send: wrong pkt 0x62 dump start ql1: 0x: 90 e2 ba eb 01 68 8c dc d4 59 c1 6c 08 00 45 00 ql1: 0x0010: 00 54 37 be 00 00 40 01 31 8a c0 a8 c8 05 c0 a8 ql1: 0x0020: c8 0a 08 00 22 30 22 19 00 01 5a 94 07 ae 00 00 ql1: 0x0030: 66 70 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 ql1: 0x0040: 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 ql1: 0x0050: 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 ql1: 0x0060: 36 37 ql1: qla_dump_buf8: qla_hw_send: wrong pkt dump end The driver is loaded via /boot/loader.conf both times. Cheers, Daniel Schossig -- 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"