[Bug 242891] mlx5_core0 ERR
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242891 --- Comment #8 from commit-h...@freebsd.org --- A commit references this bug: Author: hselasky Date: Mon Jan 6 09:50:44 UTC 2020 New revision: 356410 URL: https://svnweb.freebsd.org/changeset/base/356410 Log: MFC r356201: Fix spelling. PR: 242891 Sponsored by: Mellanox Technologies Changes: _U stable/12/ stable/12/sys/dev/hyperv/netvsc/if_hn.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 242891] mlx5_core0 ERR
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242891 --- Comment #9 from commit-h...@freebsd.org --- A commit references this bug: Author: hselasky Date: Mon Jan 6 09:51:22 UTC 2020 New revision: 356411 URL: https://svnweb.freebsd.org/changeset/base/356411 Log: MFC r356201: Fix spelling. PR: 242891 Sponsored by: Mellanox Technologies Changes: _U stable/11/ stable/11/sys/dev/hyperv/netvsc/if_hn.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 242891] mlx5_core0 ERR
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242891 --- Comment #10 from commit-h...@freebsd.org --- A commit references this bug: Author: hselasky Date: Mon Jan 6 09:51:55 UTC 2020 New revision: 356412 URL: https://svnweb.freebsd.org/changeset/base/356412 Log: MFC r356201: Fix spelling. PR: 242891 Sponsored by: Mellanox Technologies Changes: _U stable/10/ stable/10/sys/dev/hyperv/netvsc/if_hn.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 243126] Assertion fl->ifl_cidx == cidx failed at /usr/src/sys/net/iflib.c:2531
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243126 Bug ID: 243126 Summary: Assertion fl->ifl_cidx == cidx failed at /usr/src/sys/net/iflib.c:2531 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: a...@freebsd.org This happened with FreeBSD head r351653 and if_em interface in a VMware guest. I have a crash dump. This is the stack trace: #11 kdb_enter (why=0x80bdbcb7 "panic", msg=0x80bdbcb7 "panic") at /usr/src/sys/kern/subr_kdb.c:483 #12 0x8077cff1 in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:987 #13 0x8077c2cd in kassert_panic (fmt=0x80b4f01d "Assertion %s failed at %s:%d") at /usr/src/sys/kern/kern_shutdown.c:879 #14 0x808b721e in rxd_frag_to_sd (rxq=0xfe3fe000, irf=, unload=, sd=0xfe0011a54900, pf_rv=0xfe0011a549b0, ri=0xfe0011a54960) at /usr/src/sys/net/iflib.c:2531 #15 0x808b10e4 in assemble_segments (rxq=, ri=0x1dd05ea, sd=0xf80002d1b470, pf_rv=0x1) at /usr/src/sys/net/iflib.c:2594 #16 iflib_rxd_pkt_get (rxq=, ri=) at /usr/src/sys/net/iflib.c:2671 #17 iflib_rxeof (rxq=, budget=16) at /usr/src/sys/net/iflib.c:2803 #18 _task_fn_rx (context=) at /usr/src/sys/net/iflib.c:3795 #19 0x807c72a9 in gtaskqueue_run_locked (queue=0xf80002922600) at /usr/src/sys/kern/subr_gtaskqueue.c:377 #20 0x807c7028 in gtaskqueue_thread_loop (arg=) at /usr/src/sys/kern/subr_gtaskqueue.c:558 #21 0x8073ce34 in fork_exit (callout=0x807c6fa0 , arg=0xfe7f9008, frame=0xfe0011a54ac0) at /usr/src/sys/kern/kern_fork.c:1048 I can provide any additional information. Also, I can do some debugging myself, but I need some help with that as I don't know iflib code at all. -- 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 243126] Assertion fl->ifl_cidx == cidx failed at /usr/src/sys/net/iflib.c:2531
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243126 Andriy Gapon 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 242891] mlx5_core0 ERR
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242891 --- Comment #11 from Michael --- I did not find a more informative output of messages from different Linux. Everyone has a system log as some sort of chaotic nonsense. CentOS v8 garbage collection of messages when adding a network interface with SR-IOV enabled: /var/log/messages : nm-dispatcher[40509]: req:1 'dhcp4-change' [eth0]: new request (3 scripts) nm-dispatcher[40509]: req:1 'dhcp4-change' [eth0]: start running ordered scripts... systemd-udevd[40520]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. NetworkManager[996]: [1578320647.9579] manager: (eth1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/5) NetworkManager[996]: [1578320647.9795] device (eth1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready NetworkManager[996]: [1578320647.9954] device (eth1): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready NetworkManager[996]: [1578320648.1653] device (eth1): carrier: link connected kernel: hv_netvsc cc91b9de-cf8f-4729-8e30-bc4cf0e3f604 eth1: VF slot 2 added kernel: hv_vmbus: registering driver hv_pci kernel: hv_pci c2f22477-5994-443d-ae4b-7012efabe867: PCI VMBus probing: Using version 0x10002 kernel: hv_pci c2f22477-5994-443d-ae4b-7012efabe867: PCI host bridge to bus ae4b:00 kernel: pci_bus ae4b:00: root bus resource [mem 0xfe000-0xfe00f window] kernel: pci ae4b:00:02.0: enabling Extended Tags kernel: pci ae4b:00:02.0: 0.000 Gb/s available PCIe bandwidth, limited by Unknown speed x0 link at ae4b:00:02.0 (capable of 63.008 Gb/s with 8 GT/s x8 link) kernel: pci ae4b:00:02.0: BAR 0: assigned [mem 0xfe000-0xfe00f 64bit pref] systemd[1]: Starting Initialize the iWARP/InfiniBand/RDMA stack in the kernel... kernel: mlx5_core ae4b:00:02.0: firmware version: 14.26.1040 kernel: mlx5_core ae4b:00:02.0: handle_hca_cap:537:(pid 12693): log_max_qp value in current profile is 18, changing it to HCA capability limit (12) kernel: mlx5_core ae4b:00:02.0: MLX5E: StrdRq(0) RqSz(1024) StrdSz(64) RxCqeCmprss(0) kernel: hv_netvsc cc91b9de-cf8f-4729-8e30-bc4cf0e3f604 eth1: VF registering: eth2 kernel: mlx5_core ae4b:00:02.0 eth2: joined to eth1 NetworkManager[996]: [1578320649.0723] manager: (eth2): new Ethernet device (/org/freedesktop/NetworkManager/Devices/6) NetworkManager[996]: [1578320649.0726] device (eth2): enslaved to non-master-type device eth1; ignoring kernel: mlx5_ib: Mellanox Connect-IB Infiniband driver v5.0-0 systemd-udevd[40538]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. kernel: mlx5_core ae4b:00:02.0 enP44619s2: renamed from eth2 NetworkManager[996]: [1578320649.1427] device (eth2): interface index 6 renamed iface from 'eth2' to 'enP44619s2' NetworkManager[996]: [1578320649.1431] device (enP44619s2): enslaved to non-master-type device eth1; ignoring NetworkManager[996]: [1578320649.1543] device (enP44619s2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') systemd[1]: Created slice system-rdma\x2dload\x2dmodules.slice. systemd[1]: Starting Load RDMA modules from /etc/rdma/modules/rdma.conf... systemd[1]: Starting Load RDMA modules from /etc/rdma/modules/infiniband.conf... systemd[1]: Starting Load RDMA modules from /etc/rdma/modules/roce.conf... systemd[1]: Starting RDMA Node Description Daemon... systemd[1]: Started RDMA Node Description Daemon. systemd[1]: Started Load RDMA modules from /etc/rdma/modules/roce.conf. kernel: Loading iSCSI transport class v2.0-870. kernel: mlx5_core ae4b:00:02.0 enP44619s2: Link up kernel: hv_netvsc cc91b9de-cf8f-4729-8e30-bc4cf0e3f604 eth1: Data path switched to VF: enP44619s2 NetworkManager[996]: [1578320649.2483] device (enP44619s2): carrier: link connected NetworkManager[996]: [1578320649.2562] device (enP44619s2): enslaved to non-master-type device eth1; ignoring NetworkManager[996]: [1578320649.2564] device (enP44619s2): enslaved to non-master-type device eth1; ignoring NetworkManager[996]: [1578320649.2565] device (enP44619s2): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') systemd-modules-load[40640]: Inserted module 'ib_ipoib' systemd-modules-load[40640]: Inserted module 'ib_umad' NetworkManager[996]: [1578320649.3233] device (enP44619s2): enslaved to non-master-type device eth1; ignoring systemd[1]: Started Load RDMA modules from /etc/rdma/modules/infiniband.conf. kernel: iscsi: registered transport (iser) systemd-modules-load[40639]: Inserted module 'ib_iser' systemd-modules-load[40639]: Inserted module 'rdma_ucm' kernel
[Bug 241531] autofs: stale entries remain in /media, "automount -c" does not remove them
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241531 --- Comment #6 from Victor Sudakov --- (In reply to Jason W. Bacon from comment #5) autofs is most certainly not ready for production use. When it becomes all stale and stops detecting new media (which happens regularly), I restart the whole thing with the following script: service automountd stop service autounmountd stop umount -Aft autofs service automountd start service autounmountd start automount No need to reboot. -- 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 243132] posixshmcontrol(1) lists incorrect release version
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243132 Bug ID: 243132 Summary: posixshmcontrol(1) lists incorrect release version Product: Documentation Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: nbaltun...@gmail.com CC: d...@freebsd.org posixshmcontrol(1) says 'The posixshmcontrol command appeared in FreeBSD 13.0'. The release notes for FreeBSD 12.1-RELEASE are here: https://www.freebsd.org/releases/12.1R/relnotes.html In the release notes, we find this: > 4.2 Userland Application Changes > ... > The posixshmcontrol(1) utility has been added. [r348426] The source path to the manpage is `usr.bin/posixshmcontrol/posixshmcontrol.1'. I can get a patch for this in later. -- 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 243136] factor(6) gives inconsistent results with and without OpenSSL compiled int
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243136 Bug ID: 243136 Summary: factor(6) gives inconsistent results with and without OpenSSL compiled int Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: ka...@freebsd.org Created attachment 210487 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=210487&action=edit patch to fix the bug See the eamil thread that starts here: https://lists.freebsd.org/pipermail/freebsd-current/2019-December/075018.html Basically, compiling with -DWITH_OPENSSL and -DWITHOUT_OPENSSL generates a binary for factor(6), which gives inconsistent results for hexadecimal input. The patch fixes the problem. Here's a svn log entry. * usr.bin/factor/factor.6: . Update documentation to note that hexadecimal strings are accepted. . Document that a hexadecimal number can have an optional 0x or 0X prefix. . Document that a 0 value in interactive mode terminates factor(6). . Fix the maximum value for 'stop' in primes(6). . While here, spell "white-space" as "whitespace" and "non-digit" as "nondigit". * usr.bin/factor/factor.c: . Include stdbool to get acces to bool type. . Use consistent style for function prototypes. . New function. is_hex_str() looks for the longest substring and determines if it is a hexadecimal number. . New function. Factor (pun intended) out common code into convert_str2bn(). . For the WIHTOUT_OPENSSL case, make BN_dec2bn() and BN_hex2bn() return 0 on error like their OpenSSL counterparts. * usr.bin/primes/primes.c: . Fix comment. -- 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 243136] factor(6) gives inconsistent results with and without OpenSSL compiled int
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243136 Mark Linimon changed: What|Removed |Added Keywords||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 243144] pkg size mismatch error
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243144 Bug ID: 243144 Summary: pkg size mismatch error Product: Base System Version: 11.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: d...@safeport.com In the event the local copy of the repository catalogue get corrupted the command "pkg update -f" must be run. I propose a change to both the error message and the PKG-UPDATE man page to suggest this. User's having been googling for this answer since 2014. I started using FreeBSD with version 4.5 and never hit this error until updating from 10.3 --> 11.3. I also had to google for the answer. -- 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 243136] factor(6) gives inconsistent results with and without OpenSSL compiled int
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243136 Kirk McKusick changed: What|Removed |Added Status|New |Open CC||mckus...@freebsd.org --- Comment #1 from Kirk McKusick --- Thanks for the submission. Garance Alistair Drosehn or I will get it reviewed and committed. -- 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 243144] pkg size mismatch error
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243144 Conrad Meyer changed: What|Removed |Added Assignee|b...@freebsd.org|ports-b...@freebsd.org Product|Base System |Ports & Packages CC||c...@freebsd.org Version|11.3-RELEASE|Latest Component|bin |Individual Port(s) --- Comment #1 from Conrad Meyer --- Better yet, pkg should be able to detect this condition and perform the equivalent `pkg update -f` itself (unless `--no-repo-update` was specified). -- 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 243094] reboot problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 Jack changed: What|Removed |Added CC||xxjack1...@gmail.com --- Comment #10 from Jack --- I think the correct solution would be to update how reboot works on the next major version of FreeBSD and put it in the RELEASE notes. That way people can know what to expect if they were still using the reboot command and not have any surprises. -- 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"
