Re: [Retitled!] some under-VM detections for non-amd64 may be broken

On Feb 19, 2025, at 09:42, Olivier Cochard-Labbé wrote: > On Wed, Feb 19, 2025 at 6:05 PM Mark Millard wrote: >> >> Another example might be if new VM contexts should be added, >> such as UTM for macOS. What do kenv smbios.system.product , >> sysctl kern.vm_guest , and sysctl kern.hz report for

Error messages in 15.0-CURRENT (n275524-8dc0889..)

Folks, I built a GENERIC kernel "hot off the presses" as of the commits cited above. I am surprised that I'm still getting error messages in dmesg​ about: - Firmware errors - i915/skl_dmc_ver1_27.bin: could not load binary firmware /boot/firmware/i915/skl_dmc_ver1_27.bin either (repeats) - drm

Re: Very poor -CURRENT boot performance on AMD

On 25. 2. 19., Mohammad Noureldin wrote: Hi, I've installed -CURRENT using snapshot "FreeBSD-15.0-CURRENT- amd64-20250213-6156da866e7d-275409" on an HP EliteBook 845 G10 with AMD Ryzen 5 7540U. Both when booting from the install media and when booting from disk after installation I get a ve

Re: Very poor -CURRENT boot performance on AMD

Hi Mohammad, I tried the same build on VMware and it came up very fast. I don't have any AMD Ryzen based hw to confirm the behaviour. IMO you should raise a PR. [image: image.png] Thanks & Regards Rupesh Pilania On Thu, Feb 20, 2025 at 8:00 AM Mohammad Noureldin < moham...@thelightbird.com> wrot

RE: Very poor -CURRENT boot performance on AMD

Hi Mohammad, The performance issue(s) have been noted on the UPDATING file. Here is a snippet: NOTE TO PEOPLE WHO THINK THAT FreeBSD 15.x IS SLOW: FreeBSD 15.x has many debugging features turned on, in both the kernel and userland. These features attempt to detect incorrec

Very poor -CURRENT boot performance on AMD

Hi, I've installed -CURRENT using snapshot "FreeBSD-15.0-CURRENT-amd64-20250213-6156da866e7d-275409" on an HP EliteBook 845 G10 with AMD Ryzen 5 7540U. Both when booting from the install media and when booting from disk after installation I get a very poor boot performance up until the FreeBSD Bo

Re: RFC: mount_nfs failure due to dns not running yet

On 2/19/25 5:40 PM, Rick Macklem wrote: Hi, The subject line basically describes the problem glebius@ ran into. When doing an NFS mount in /etc/fstab, it failed since the DNS service was not yet working and, as such, the DNS lookup of the server fqdn failed, causing the mount to fail. Note that

Re: RFC: mount_nfs failure due to dns not running yet

This situation has existed these past 40 years. You have to put your ipadress : hostname pairs into /etc/hosts if you dont have accsss to a working DNS.This is not a bug. Its the way name resolution works. Den ons 19 feb. 2025 23:40Rick Macklem skrev: > Hi, > > The subject line basically

RFC: mount_nfs failure due to dns not running yet

Hi, The subject line basically describes the problem glebius@ ran into. When doing an NFS mount in /etc/fstab, it failed since the DNS service was not yet working and, as such, the DNS lookup of the server fqdn failed, causing the mount to fail. Note that this behaviour has existed for decades.

Re: [Retitled!] some under-VM detections for non-amd64 may be broken

On Wed, Feb 19, 2025 at 6:05 PM Mark Millard wrote: > > Another example might be if new VM contexts should be added, > such as UTM for macOS. What do kenv smbios.system.product , > sysctl kern.vm_guest , and sysctl kern.hz report for UTM on: > > ) amd64 macOS > ) aarch64 macOS > ) . . . ? > Hi,

[Retitled!] some under-VM detections for non-amd64 may be broken

On Feb 19, 2025, at 05:24, Jason Bacon wrote: > > On 2/18/25 20:13, Mark Millard wrote: >> Something I possibly should have done --but did not do was to set: >> kern.hz=100 > > I stopped doing this under VirtualBox a few years ago, because it was causing > clock skew. Apparently an assumption