savecore: operation not permitted

2022-11-26 Thread void
On 13-stable (n253148), am seeing in the console at startup savecore[1415]: /dev/ada0s1b: Operation not permitted Writing crash summary to /var/crash/core.txt.3. It's enabled in rc.conf: # sysrc savecore_enable savecore_enable: YES # dumpon -l ada0s1b What's broken? tia, --

Re: savecore: operation not permitted

2022-11-27 Thread void
On Sat, 26 Nov 2022, at 19:17, Warner Losh wrote: > What's your secure level? Can you run the command by hand after boot? > (Usually on modern systems you don't swap right away and have time for > a test like that). thanks, I'll try that > Trying to see if this is prohibited by secure level or

avoiding periodic(8) during long poudriere runs

2023-02-03 Thread void
Hello stable@ How does one avoid periodic(8) during long poudriere runs? I find that it'll cause the system to thrash if periodic starts when poudriere is running. is there some established way of telling it not to run when, for example, 5 min load is over 2.00 ? I've seen ubuntu do similar, bu

Re: buildworld fails with bhyverun.c:1270:6 unused variable???

2023-02-03 Thread void
On Sat, Jan 21, 2023 at 07:55:05PM +0100, Mathias Picker wrote: I have this for some time, had no time to look into this, but today I deleted /usr/src, fetched source again, switched to stable/13, did a su -l root, removed /etc/make.conf and rebuild, same error. Not sure if you've tried this, b

Re: installing to usb3 disk or thumbdrive, result isn't bootable

2023-07-31 Thread void
On Mon, Jul 31, 2023 at 06:42:24PM +0100, void wrote: Next to try is setting destination usb3 MBR/ufs2 and setting it active in alt-f4 before booting. gpart show da4 on the install media shows slice 2 [freebsd] as active in mbr Ensured this was the case, and the destination usb3 booted

installing to usb3 disk or thumbdrive, result isn't bootable

2023-07-31 Thread void
Hi stable@ I'm having odd problems booting an installation to usb3 disk or stick. steps-to-reproduce: 1. download (e.g:) https://download.freebsd.org/releases/ISO-IMAGES/13.2/FreeBSD-13.2-RELEASE-amd64-memstick.img 2. write it to usb3. We'll call this one the installation usb3 3. boot it up an

problems trying to use powerd with Xeon E5-2690 on HP ProLiant DL380p

2023-08-09 Thread void
Hello stable@ I'm trying to run powerd (stable/13-n254781) but it fails to load, and this appears in dmesg: interface hwpstate_intel.1 already present in the KLD 'kernel'! linker_load_file: /boot/kernel/cpufreq.ko - unsupported file type and, earlier: est0: numa-domain 0 on cpu0 est: CPU supp

Re: problems trying to use powerd with Xeon E5-2690 on HP ProLiant DL380p

2023-08-09 Thread void
Hi Mark, On Wed, Aug 09, 2023 at 07:52:59PM -0400, Mark Saad wrote: Hi void It will work , you will need to re-enable c-states and p-states etc in the bios . Dmesg is only showing the cpu has the options but the bios controls the ability to use it . Iirc hp has some opaque options to

configuring the console on 14-stable with hdmi-attached screen

2023-08-25 Thread void
Hello list, tl;dr: I'd like to have a smaller/better font/finer "graphics" in a non-xorg console.[1] Is this possible with FreeBSD at the moment? I can see there's "sc" and "vt" in the kernel but have never successfully set a console screen font going by the handbook. In addition to the font

Re: configuring the console on 14-stable with hdmi-attached screen

2023-08-25 Thread void
In dmesg I see the following: VT(vga): resolution 640x480 VT-x: Basic Features=0xda0400 x86bios: IVT 0x00-0x0004ff at 0xf800 vtvga0: VT(vga): resolution 640x480 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID vtvga0: How can I change the 640x480 to say 1920x1080 ? --

Re: configuring the console on 14-stable with hdmi-attached screen

2023-08-25 Thread void
On Fri, Aug 25, 2023 at 10:04:01AM -0600, Warner Losh wrote: The only way I know is to use UEFI and control it that way... How would I change from bios to uefi? --

Re: configuring the console on 14-stable with hdmi-attached screen

2023-08-29 Thread void
Hi, On Sat, Aug 26, 2023 at 10:37:56AM +0200, Helge Oldach wrote: For historical reasons I'm using "sc". Enabled by | kern.vty="sc" in /boot/loader.conf. What are the historical reasons? (sorry - it would help me to understand the why) From my reading so far, it would seem that vt is less

periodic daily takes a very long time to run (14-stable)

2023-10-27 Thread void
Hello list, I'm asking this in order to determine whether I've got something misconfigured or maybe my expectations need recalibrating, or maybe both. context is rpi4b with 8GB and usb3-connected 1tb zfs hard disk. /etc/daily.local has been moved out of the way to try to fix the issue. When pe

Re: periodic daily takes a very long time to run (14-stable)

2023-10-27 Thread void
orts/testing zroot/usr 22.1G 790G96K /usr zroot/usr/home13.5G 790G 13.5G /usr/home zroot/usr/home/tmp 144K 790G 144K /usr/home/void/tmp zroot/usr/obj

Re: periodic daily takes a very long time to run (14-stable)

2023-10-27 Thread void
On Fri, Oct 27, 2023 at 01:45:24PM +0200, Ronald Klop wrote: Can you run "gstat" or "iostat -x -d 1" to see how busy your disk is? And how much bandwidth is uses. when periodic is *not* running, gstat numbers fluctuate between whats indicated below and all zeros: dT: 1.011s w: 1.000s L(q)

Re: periodic daily takes a very long time to run (14-stable)

2023-10-27 Thread void
On Fri, Oct 27, 2023 at 02:46:39PM +0200, Ronald Klop wrote: Mmm. Your pool has a lot of space left. So that is good. About gstat / iostat, yes during the daily scan would be nice. The numbers outside of the daily scan can also help as a reference. NB: There were talks on the ML about vnode r

Re: periodic daily takes a very long time to run (14-stable)

2023-10-27 Thread void
On Fri, Oct 27, 2023 at 03:34:35PM +0200, Ronald Klop wrote: What stands out to me is that you do quite a lot of writes on the disk. (I might be mistaken.) The max. number of IOPS for HDD is around 80 for consumer grade harddisks. I think this counts for USB connected disks. https://en.wikiped

Re: periodic daily takes a very long time to run (14-stable)

2023-10-27 Thread void
Hi, On Fri, Oct 27, 2023 at 11:01:03AM -0400, Paul Mather wrote: This doesn't affect the periodic daily run (to my knowledge) # ps x | grep periodic 59319 14 S+ 0:00.00 grep periodic 27376 17 I+ 0:00.00 /bin/sh - /etc/periodic/security/110.neggrpperm 27987 17 I+ 0:00.00

Re: periodic daily takes a very long time to run (14-stable)

2023-10-27 Thread void
On Fri, Oct 27, 2023 at 05:23:49PM +0200, Ronald Klop wrote: Well. You could remove daily_clean_disks_enable="YES" from /etc/periodic.conf. That saves you the "find". I have never used it before. The default is "off". Yes, I'll try that, but it's a very recent addition. The periodic daily prob

Re: periodic daily takes a very long time to run (14-stable)

2023-10-27 Thread void
On Fri, Oct 27, 2023 at 05:38:58PM +0200, Guido Falsi wrote: If this script is the culprit is easily tested, disable it and see. I guess you can stay a few days without checking for negative permissions. I'm unsure how to disable that one script from periodic. but I think that what you recomm

Re: periodic daily takes a very long time to run (14-stable)

2023-10-27 Thread void
On Fri, Oct 27, 2023 at 05:38:58PM +0200, Guido Falsi wrote: Also, $MP is defined in such a way to exclude filesystems that set "nosuid/noexec". I do happen to have those setup for my ccache directory so it is skipping that. With zfs it is especially easy to set these flags, and I think havin

Re: periodic daily takes a very long time to run (14-stable)

2023-10-28 Thread void
On Fri, Oct 27, 2023 at 05:38:58PM +0200, Guido Falsi wrote: I have this for ccache FS (zfs): dumpster/ccache atime on local I wondered why you have this set to 'on'? I mean I know /var/mail needs it for mail to function. Is it the same wiht ccache ? --

Re: periodic daily takes a very long time to run (14-stable)

2023-10-28 Thread void
On Sun, Oct 29, 2023 at 12:49:14AM +0200, Guido Falsi wrote: Correcting myaelf: The version we currently have in the ports tree (3.7.x) does not care for atime, as far as I can see in the source code. It checks mtime only. Newer versions do use it though! Thanks for checking. I've set it

pf is broken in stable/14-n265566-4533fa42ad91 arm64

2023-11-18 Thread void
Hi, This context [1] was on stable/14-n265566 where pf worked fine. Source upgrade yesterday to stable/14-n265566 and pf is now broken. # service pf status /usr/src/sys/contrib/libnv/nvlist.c:379: Element 'halfopen_states' of type NUMBER doesn't exist. Abort trap (core dumped) To try and debug

some dirs don't get deleted with make-delete-old

2023-12-08 Thread void
It seems some dirs don't get deleted with make delete-old: # yes | make delete-old [...] /usr/share/doc/atf rmdir: /usr/share/certs/blacklisted: Directory not empty /usr/share/atf [...] /usr/lib/debug/lib rmdir: /usr/lib/debug/boot: Directory not empty /usr/lib/debug/bin is this an error? cont

Re: some dirs don't get deleted with make-delete-old

2023-12-10 Thread void
On Fri, Dec 08, 2023 at 05:33:29PM +0100, Herbert J. Skuhra wrote: Do you use WITHOUT_DEBUG_FILES= in /etc/src.conf? Bingo! % ug DEBUG /etc/src.conf 9: WITHOUT_ASSERT_DEBUG= 17: WITHOUT_DEBUG_FILES= so it's unable to be deleted because it's not there ;) (I guess? though i'd have expecte

leap-second error in console

2024-01-14 Thread void
Context is stable/13-n257165-4c4633fdffbe amd64 built Mon Jan 15 00:20:52 2024 UTC In the console, the following is displayed Security policy loaded: MAC/ntpd (mac_ntpd) Starting ntpd. Jan 15 00:26:48 cloud ntpd[3412]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): expired 19 days ago How

Re: leap-second error in console

2024-01-14 Thread void
Hi, On Mon, 15 Jan 2024, at 01:45, Warner Losh wrote: > Add > > ntp_leapfile_sources="https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list"; > > to your /etc/rc.conf file. This is the reliable, freely available > source for the leap seconds > list. We should make that the default, but doi

Re: USB CD drive does not work with 14-Stable

2024-02-24 Thread void
On Sat, 24 Feb 2024, at 14:12, S.N.Grigoriev wrote: > Hi, list, > > I've found out that my USB CD drive does not work with my 14-Stable (amd64). > It works fine with Linux and Windows and in past worked fine with 12-Stable. > > The following is from /var/log/messages: > > kernel: usb_alloc_device:

Re: USB CD drive does not work with 14-Stable

2024-02-25 Thread void
On Sun, 25 Feb 2024, at 10:07, S.N.Grigoriev wrote: > Hi, void, > > thank you for your response! My kernel config is: > > ## > include GENERIC > > ident GEN > > # No sound support > nodevicesound > nodevicesnd_cmi

Re: USB CD drive does not work with 14-Stable

2024-02-25 Thread void
Another thing maybe worthwhile trying is to just have that one thing plugged into the usb subsystem. Beforehand, tail -f /var/log/messages in an xterm, unplug everything usb (2&3), plug in the cd drive, observe messages.

Re: USB CD drive does not work with 14-Stable

2024-02-25 Thread void
On Sun, 25 Feb 2024, at 16:14, S.N.Grigoriev wrote: >> Another thing maybe worthwhile trying is to just have that one thing >> plugged into the usb subsystem. Beforehand, tail -f /var/log/messages >> in an xterm, unplug everything usb (2&3), plug in the cd drive, >> observe messages. > > I've done

Re: USB CD drive does not work with 14-Stable

2024-02-27 Thread void
I get the following from my own portable BD machine, from the lsusb command: Bus /dev/usb Device /dev/ugen0.10: ID 0e8d:1956 MediaTek Inc. Samsung SE-506 Portable BluRay Disc Writer There's also lots of "can't get device qualifier: Input/output error" with -v but it's not stopping the disk from

KVA_PAGES

2024-03-08 Thread void
Hi, In 14-stable on amd64, what's the default value for KVA_PAGES ? I'm asking because WINE says something about it: "Some ZFS tuning guides recommend setting KVA_PAGES=512 in your kernel configuration. This is incompatible with Wine. The maximum possible is KVA_PAGES=500, which should still b

Re: KVA_PAGES

2024-03-09 Thread void
On Fri, 8 Mar 2024, at 10:25, Miroslav Lachman wrote: > # config -x /boot/kernel/kernel | grep -i kva_pages > > (it is empty on amd64) aha, makes sense. It's 64-bit only here. thanks all,

freebsd-update to 14.1-RC1 oddity

2024-05-29 Thread void
Hi, Got the following error when running second freebsd-update upgrade incantation after first reboot: # /usr/sbin/freebsd-update install src component not installed, skipped Installing updates...install: ///usr/include/c++/v1/__string/INS@KrFwVd: No such file or directory install: ///usr/tests

new error messages after upgrade 14.0-p5 to 14.1-p1 amd64

2024-06-27 Thread void
After upgrading, I noticed messages like these appearing during rebooting, immediately after kernel: NFS access cache time=60 kernel: rpc.umntall: 10.1.1.102: MOUNTPROG: RPC: Port mapper failure - RPC: Timed out sometimes it appears twice, once it appeared five times. The system eventually comp

Re: new error messages after upgrade 14.0-p5 to 14.1-p1 amd64

2024-06-28 Thread void
Hi Rick, On Thu, Jun 27, 2024 at 09:29:51AM -0700, Rick Macklem wrote: rpcbind_enable="YES" nfs_client_enable="YES" If you have at least one of these in your /etc/rc.conf, then all I can think of is some sort of network/routing issue that interferes with rpcbind working. I have nfs_client_en

Re: new error messages after upgrade 14.0-p5 to 14.1-p1 amd64

2024-06-29 Thread void
On Fri, Jun 28, 2024 at 01:23:29PM +0100, void wrote: (snip) Just to add to this, the reported error does *not* occur on 15.0-CURRENT #5 n270917-5dbf886104b4 arm64 and that system has *only* nfs_client_enable="YES" and it's a slower system --

Re: new error messages after upgrade 14.0-p5 to 14.1-p1 amd64

2024-07-11 Thread void
Hi Rick, The nfs server is 14-stable and the exported dir is zfs with the sharenfs property set. The client (14.1-p1) is a VM on a different machine but the same network. I'll try putting rpcbind_enable=YES in /etc/rc.conf Probably won't make any difference. Sorry for hte slow response -

Re: new error messages after upgrade 14.0-p5 to 14.1-p1 amd64

2024-07-12 Thread void
Hi Rick, There's no freebsd machine I've ever had (any version) that has had the ip specified without the netmask keyword in /etc/rc.conf. Until https://lists.freebsd.org/archives/freebsd-current/2024-June/006075.html I didn't even know it was possible to configure networking and have it work

openbsd 7.5 and nfs via sharenfs zfs freebsd stable/14-n266883-7a3d7b29f83e

2024-07-31 Thread void
Hi, I can't mount an nfs share when the client is openbsd 7.5 The nfs server is freebsd stable/14-n266883-7a3d7b29f83e I *can* mount it from a debian client, and other freebsd machines have no issues Is it a freebsd issue or an openbsd issue? https://marc.info/?l=openbsd-misc&m=172191444915091

Re: openbsd 7.5 and nfs via sharenfs zfs freebsd stable/14-n266883-7a3d7b29f83e

2024-07-31 Thread void
On Wed, Jul 31, 2024 at 12:52:59PM -0400, Mark Saad wrote: Void silly question on obsd do you have pf up and running ? If so can you try w/o pf ? Hi yes pf is *not* active on the openbsd machine If you look at https://marc.info/?l=openbsd-misc&m=172191444915091&w=2 you'll se

automount errors

2024-10-29 Thread void
hello stable, 14.2-PRERELEASE DESKTOP amd64 1401503 1401503 Upon booting, seeing this in the console Oct 29 12:57:17 desktop kernel: Starting devd. Oct 29 12:57:17 desktop kernel: sh: /usr/sbin/automount: not found Oct 29 12:57:17 desktop syslogd: last message repeated 19 times Oct 29 12:57:17

Re: automount errors

2024-10-29 Thread void
On Tue, Oct 29, 2024 at 07:58:15PM +0100, Herbert J. Skuhra wrote: Do you use WITHOUT_AUTOFS in src.conf? WITHOUT_AUTOFS Do not build autofs(5) related programs, libraries, and kernel modules. d'oh. sorry for the noise, thanks for the tip. i was too narrowly focuss

Re: beastie menu is broken in latest update (stable/14-n269388-1821145f28e9)

2024-11-04 Thread void
On Sat, 2 Nov 2024, at 19:08, Warner Losh wrote: > > I've tested EFI and BIOS and I have a couple of reports that it works > on BIOS so far. Thanks Warner, it's working fine now --

beastie menu is broken in latest update (stable/14-n269388-1821145f28e9)

2024-10-31 Thread void
The ascii display menu is now broken after updating to 14.2-PRERELEASE stable/14-n269388-1821145f28e9 It shows what looks like control characters in where the borders of the menus are usually. This is on amd64. I *think* it uses 'legacy' --

Re: beastie menu is broken in latest update (stable/14-n269388-1821145f28e9)

2024-10-31 Thread void
On Thu, Oct 31, 2024 at 12:16:46PM -0600, Warner Losh wrote: Ok. So this is on bare metal with BIOS boot? I was hoping for a bhyve method since i don't have any rwal bios machines anymore. Yeah it's on bare metal. I can spin up a vm, bring it to stable/14-n269388-1821145f28e9 but it'll take a

Re: beastie menu is broken in latest update (stable/14-n269388-1821145f28e9)

2024-10-31 Thread void
On Thu, Oct 31, 2024 at 11:23:32AM -0600, Warner Losh wrote: On Thu, Oct 31, 2024 at 9:58 AM void wrote: The ascii display menu is now broken after updating to 14.2-PRERELEASE stable/14-n269388-1821145f28e9 It shows what looks like control characters in where the borders of the menus are

Re: service apache24 reload

2024-10-31 Thread void
On Wed, Oct 30, 2024 at 06:50:15AM +0100, ft wrote: Hello, apache24 runs in a jail. service apache24 reload doesn't work? I think you need to run it with -j % service -h Usage: service [-j ] -e service [-j ] -R service [-j ] [-v] -l | -r service [-j ] [-v] [-E var=value] start|stop|etc. ser

Re: beastie menu is broken in latest update (stable/14-n269388-1821145f28e9)

2024-11-02 Thread void
On Sat, Nov 02, 2024 at 10:42:16AM -0600, Warner Losh wrote: OK. This is because the text-only boot loader only supports cons25-level of character set (which is ASCII + upper page IBMPC) rather than Unicode. There's 0 chance that unicode support will be added to that boot loader (you need the gra

Re: freebsd-update doesn't refresh leapsecond file

2024-12-24 Thread void
On Mon, Dec 23, 2024 at 08:45:18PM -0700, Warner Losh wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275419 I think this is what you're looking for. There's a lot of other bugs marked duplicates of that one. Might be a case of same problem different reason, see https://bugs.freebsd

Re: freebsd-update errors 13.3-p11 => 13.4-p2

2024-12-24 Thread void
On Tue, Dec 24, 2024 at 05:58:26PM +0100, Ronald Klop wrote: I had this a while ago. Copied the missing file from another system. Didn’t find the root cause. Freebsd-update could be improved on resilience for inconsistent systems I assume. I'm unsure how inconsistency could have arisen, if t

Re: gpart -t option incorrect in manpages (14.2-RELENG)

2025-01-18 Thread void
Hi, On Sat, 18 Jan 2025, at 20:18, Warner Losh wrote: > It's expected. > > First, I'd skip using MBR. It's super limited, kinda hard and uses > weird things. Using > GPT will just work. MBR should generally only be used for legacy uses, > but it should all > work, once you do it correctly. The

Re: gpart -t option incorrect in manpages (14.2-RELENG)

2025-01-18 Thread void
On Sat, Jan 18, 2025 at 01:18:20PM -0700, Warner Losh wrote: (snip) Just checked - FreeBSD-14.2-RELEASE-amd64-disc1.iso installer still automatically goes to MBR, one has to select GPT when installing auto-ufs. Might be an idea to change the default to GPT if that's what FreeBSD would like to p

Re: gpart -t option incorrect in manpages (14.2-RELENG)

2025-01-18 Thread void
On Sat, Jan 18, 2025 at 06:15:25PM -0700, Warner Losh wrote: Wierd. All the installs I've done in the last what feels like a decade have defaulted to GPT. Are you installing onto media that's pre-formatted with MBR? Nope. I install to an empty image created like this: # truncate -s 64G vmimag

gpart -t option incorrect in manpages (14.2-RELENG)

2025-01-18 Thread void
Hi, context is freebsd 14.2-releng vm (amd64) that has been upgraded with freebsd-update from 13.4. Decided to add another disk so invoking the vm looks like this: # sh vmrun.sh -c 4 -m 16G -t tap2 -d ./vm.img -d ./disk1.img vmname used gpart to create an MBR for disk1.img. tried to make sli

Re: gpart -t option incorrect in manpages (14.2-RELENG)

2025-01-20 Thread void
On Mon, Jan 20, 2025 at 04:39:02PM +0300, Antony Uspensky wrote: If I remember correctly, installer offers MBR on BIOS environment, and GPT on UEFI. Try run your vm as UEFI machine. A. That's interesting. I guess vmrun.sh is 'BIOS' in this context. The host runs other VMs for other OS guest

Re: "Loader needs to be updated" (azure guest context)

2025-01-03 Thread void
On Mon, Dec 30, 2024 at 10:59:47AM -0700, Warner Losh wrote: In this context, it's a known false positive. It's too risky to fix in a pX for 13.4, so will be in 13.5 since the fix is already in stable/13. It's just cosmetic, there's no bug it exposes. Thank you for your full explanation. --

Re: freebsd-update errors 13.3-p11 => 13.4-p2

2024-12-24 Thread void
On Tue, Dec 24, 2024 at 08:20:34PM +, Dave Cottlehuber wrote: I have see this on very small (0,5-1GiB RAM) systems with low cpu. the system log may show processes being killed off, if these are ones doing gzip or sha256 or similar, could that explain it? I've never had this issue on bigger s

freebsd-update errors 13.3-p11 => 13.4-p2

2024-12-23 Thread void
Hello, On upgrading 13.3-p11 to 13.4-p2 (amd64) the following is displayed after the kernel parts finish installing, before the first reboot: # /usr/sbin/freebsd-update install src component not installed, skipped Installing updates...ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or

freebsd-update doesn't refresh leapsecond file

2024-12-23 Thread void
On a system that's been always maintained with freebsd-upgrade (and was installed when 13.1 was new), the following gets printed in the console on boot Dec 23 16:00:21 REDACTED ntpd[604]: leapsecond file (‘/var/db/ntpd.leap-seconds.list’): expired 362 days ago Whenever it's been upgraded, all

Re: freebsd-update doesn't refresh leapsecond file

2024-12-23 Thread void
On Mon, Dec 23, 2024 at 05:54:27PM -0700, Warner Losh wrote: Already been a PR that been fixed months ago. Warner Something must have unfixed it then, because this is from a few hrs ago. Do you know the previous PR? --