[Bug 241581] PCIe passthrough is broken in QEMU 4 due to PCI Device ID conflict

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241581 Vincenzo Maffione changed: What|Removed |Added CC||vmaffi...@freebsd.org

[Bug 243482] Link state change does not logged

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243482 Bug ID: 243482 Summary: Link state change does not logged Product: Base System Version: 12.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: A

[Bug 243482] Link state change does not logged

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243482 Toto changed: What|Removed |Added Alias||LinkStateIssue -- You are receiving this m

[Bug 234455] CPU frequency scaling fails for multiple cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455 Dave Green changed: What|Removed |Added CC||d...@fastmail.co.uk --- Comment #4 fr

[Bug 234455] CPU frequency scaling fails for multiple cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455 --- Comment #5 from Conrad Meyer --- @Dave, did you try debug.acpi.disabled="thermal"? It seems bizarre that the default dev.cpu.0.freq is 800. Is that the case at boot, or was your initial description after running, say, powerd? It migh

[Bug 234455] CPU frequency scaling fails for multiple cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455 --- Comment #6 from Dave Green --- CPU is 800 at boot either with or without powerd. Temperature is always stable at 25 degrees. I'll retry debug.acpi.disabled="thermal" but I don't recall it having any effect for 11.2-RELEASE. If I comm

[Bug 234733] Setting CPU frequency with sysctl dev.cpu.0.fr slows a Ryzen 2700X down

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733 --- Comment #2 from Conrad Meyer --- Can both of you try: Adding 'debug.hwpstate_verbose="1"' in /boot/loader.conf and checking dmesg for boot-time messages about hwpstate? This can also be sysctl'd at runtime to see what gets logged when

[Bug 234733] Setting CPU frequency with sysctl dev.cpu.0.fr slows a Ryzen 2700X down

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733 --- Comment #3 from Conrad Meyer --- I tried the following test: $ cpuset -l 0 time sha1 <~200MBfile> (burn one result for caching, then repeat 3 trials) I got average 0.24 real, 0.22 user. You might pick a slightly larger file for bigger

[Bug 234455] CPU frequency scaling fails for multiple cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455 --- Comment #7 from Conrad Meyer --- I wonder where those bogus priorities are coming from, though. I thought I recall looking and seeing acpi_thermal as the only possible source, but I might be mistaken. -- You are receiving this mail b

[Bug 234455] CPU frequency scaling fails for multiple cores

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455 --- Comment #8 from Conrad Meyer --- Also: 800 at boot sounds like a BIOS bug. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list

[Bug 243500] segfault in libcrypto at ssleay_rand_bytes ()

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243500 Bug ID: 243500 Summary: segfault in libcrypto at ssleay_rand_bytes () Product: Base System Version: 11.3-RELEASE Hardware: amd64 OS: Any Status: New

[Bug 242212] usr.sbin/mergemaster/mergemaster.sh: There is no logic to handle symbolic links

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242212 Yasuhiro KIMURA changed: What|Removed |Added Attachment #210786|0 |1 is obsolete|

[Bug 243500] segfault in libcrypto at ssleay_rand_bytes ()

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243500 Kubilay Kocak changed: What|Removed |Added CC||sect...@freebsd.org Keyw

[Bug 242212] usr.sbin/mergemaster/mergemaster.sh: There is no logic to handle symbolic links

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242212 Kubilay Kocak changed: What|Removed |Added Keywords||feature, needs-qa Severi

[Bug 243453] Log duplication

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243453 --- Comment #1 from Michael --- Experimenting with different options from Google, I found a temporary solution to the problem. But it is not so logical. FreeBSD designers must do something about it! We modify the standard configuration file