[Bug 165059] vtnet(4): Networking breaks with a router using virtio net driver on KVM host
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059 --- Comment #27 from elico --- (In reply to Kubilay Kocak from comment #26) I will try to test later on. Since Ubuntu 14.04 is not supported anymore I will try to reproduce on later versions of Ubuntu 20.04/22.04 and Oracle Linux 8. I will try to verify with 12.3 and 12.4 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267749] Running "grep -Fivx -f known.words new.words" gives wrong result
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267749 Bug ID: 267749 Summary: Running "grep -Fivx -f known.words new.words" gives wrong result Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: jonathan.leff...@gmail.com Created attachment 238058 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238058&action=edit List of known words in the repro The command "grep -Fivx -f known.words new.words" is meant to compare a list of putatively new words against a list of known words, reporting only those new words not present amongst the known words. The context is a script for helping with the New York Times "Spelling Bee" puzzle, but that doesn't matter much. Testing "grep (BSD grep) 2.5.1-FreeBSD" as found on macOS Big Sur 11.7.1 against "grep (GNU grep) 2.27", I get different results for the following files: New Words: decedent deceived decident detected dietetic Known Words: Civic Decedent Deceit Deceive Deceived Decent Decide Decided Deiced Detect Detected Detective Device Dice There are no blanks in the files; the only white space is the newlines. There are no blank lines in the files. GNU grep produces the (correct) list: decident dietetic BSD grep produces the (incorrect) list: deceived decident detected dietetic Both "deceived" and "detected" are in the list of known words and neither should be reported. I believe this is a bug in BSD grep. My short-term workaround is to use GNU grep, but I'd rather it wasn't necessary. I'm not clear whether this should be reported to Apple or FreeBSD (or both). (I think I ran into 253209 "grep -v -f some-empty-file -- does the wrong thing" previously, but I worked around that, too. It isn't directly relevant to this bug, though; neither file is empty in this bug.) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267749] Running "grep -Fivx -f known.words new.words" gives wrong result
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267749 --- Comment #1 from Jonathan Leffler --- Created attachment 238059 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238059&action=edit List of new words from repro -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267750] omp_set_num_threads fails to set number of threads
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267750
Bug ID: 267750
Summary: omp_set_num_threads fails to set number of threads
Product: Base System
Version: 13.1-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: misc
Assignee: b...@freebsd.org
Reporter: y...@freebsd.org
This program:
> #include
>
> int main(int, char* []) {
>omp_set_num_threads(4);
>std::cout << "ncpu=" << omp_get_num_threads() << std::endl;
> }
prints:
> ncpu=1
instead of
> ncpu=4
--
You are receiving this mail because:
You are the assignee for the bug.
Problem reports for b...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- New |197876 | [devfs] an error in devfs leads to data loss and New |198797 | [PATCH] Added an option to install BSDstats to bs New |202362 | ntp: restore refclocks selection (10.2-RELEASE re New |202740 | vi/ex string substitution problem when there is m New |204097 | witness_initialize() does not perform bound check New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi New |209213 | UEFI Loader shows only black screen with Nvidia G New |210804 | installerconfig - using ZFS create in custom scri New |223470 | freebsd-update: Cannot identify running kernel (/ New |230620 | "install -d" issue New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( New |252123 | fetch(3): Fix wrong usage of proxy when request i Open|177821 | sysctl: Some security.jail nodes are funky, dupli Open|182466 | [headers] [patch] make self-contained Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf Open|192573 | Add ps(1) option: Print process start time in sec Open|194925 | [pf] [ifconfig] interface group keywords do not w Open|197921 | scheduler: Allow non-migratable threads to bind t Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4) Open|206649 | cyapa(4): Add common gestures for Cypress APA I2C Open|207940 | stand/efi/boot1: Add boot partition selection Open|212608 | sockstat(1) and lsof(8) can not identity the owne Open|220246 | syslogd does not send RFC3164-conformant messages Open|221305 | Mouse cursor loss when moving cursor while loadin Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL Open|221854 | makefs: Reject UFS labels that are too long to fi Open|226893 | freebsd-update: Support patchlevel argument for f Open|231810 | [build] release always fails with "mkimg: partiti Open|233578 | Unprivileged local user can prevent other users l Open|233988 | freebsd-update: Improve progress output on termin Open|236718 | system panics with message: vm_fault_hold: fault Open|237287 | moused(8) ignores button release events in virtua Open|237924 | Possible infinite loop in function empty_aux_buff Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana Open|238486 | Possible buffer overflow bug in sc_allocate_keybo Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea Open|241697 | i915kms: Kernel panic loading module on custom ke Open|247132 | Fix build error: use of undeclared identifier 'cp Open|248352 | mfi(4): Remove RAID map sync functionality Open|257149 | CFLAGS not passed to whole build New |260138 | TPM2 Support in bootloader / kernel in order to r New |261306 | Geli rc.d script does not support insertion of US New |262957 | mpr(4), mps(4): change formally to formerly New |267537 | contrib/nvi: Fix core dump when tags file pattern Open|179832 | manual page of mac_from_text suggests incorrect f 47 problems total for which you should take action.
[Bug 165059] vtnet(4): Networking breaks with a router using virtio net driver on KVM host
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059 --- Comment #28 from elico --- (In reply to elico from comment #27) OK so just to mention the NAT related documents are at: http://draft.scyphus.co.jp/freebsd/nat.html and ontop of Oracle Enterprise Linux 8 KVM host the issue exists on 12.3 the setup is very simple: * Alpine 3.16 with ip 192.168.111.1/24 gw 192.168.111.254 DNS 8.8.8.8 * FreeBSD 12.3 with two interfaces: vtnet0 192.168.110.1/24 GW 192.168.110.254 vtnet1 192.168.111.254/24 pf rules to nat on $ext_inf * VyOS 1.3.2 with two interfaces: eth0 192.168.122.183/24 GW 192.168.122.1 eth1: 192.168.110.254/24 ping from Alpine to 8.8.8.8 via FreeBSD (NAT) -> VyOS (NAT) = works (ICMP_ wget from Alpine to 8.8.8.8 via FreeBSD (NAT) -> VyOS (NAT) = doesn't work (TCP) When I am running the next on the vtnet0 and vtnet1 interfaces the TCP works: ifconfig vtnet0 -rxcsum ifconfig vtnet1 -rxcsum It was resolved long ago in OpenBSD so now there only should be a fix and a text. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261169] [Intel AlderLake]Read&Write files to FAT32 or UFS partition cause data corrupt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261169 --- Comment #5 from Vico --- Amar, you needn't disable E core in BIOS, the workaround is disable pcid. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267750] omp_set_num_threads fails to set number of threads
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267750 Daniel Tameling changed: What|Removed |Added CC||tamelingdan...@gmail.com --- Comment #1 from Daniel Tameling --- This is in accordance with the specification. It says: "The omp_get_num_threads routine returns the number of threads in the team that is executing the parallel region to which the routine region binds. If called from the sequential part of a program, this routine returns 1." See also https://stackoverflow.com/questions/8969748/set-number-of-threads-using-omp-set-num-threads-to-2-but-omp-get-num-threads for a similar discussion. -- You are receiving this mail because: You are the assignee for the bug.
