00:00:51 <creith> I can send you the exact confiuration
00:01:33 <creith> Anyway, the first thing would be the capsicumize the base system ... that would be a step
00:01:42 <creith> I would love to help
00:05:32 <creith> if a pledged application tries a system call, it is not allowed to, it will be aborted
00:06:26 <creith> but the idea behind unveil was that an attacker can not see the difference between an unveil and an unexisting file, therefore ENOEnT
00:06:37 <RhodiumToad> poke through src/usr.bin and see which ones (a) don't already link to libcasper (see Makefile) and (b) look like possible candidates for it
00:21:17 <creith> @ RhodiumToad I will do
00:23:29 <creith> Though I think the daemons are appropriate candidates ... but maybe that's just what I have been doing for too long
00:23:41 <creith> usr.bin is fine
00:25:17 <creith> what is the general philosophy ? trying to keep with Linux ?
00:27:08 <RhodiumToad> philosophy of what exactly?
00:28:58 <creith> well, one thing I like about OpenBSD is the idea of radical simplicity
00:30:12 <creith> have a look at the echo.c at FreeBSD ... is this a show off of C11 ? NetBSD and OpenBSD keep it with a simple iteration over argv
00:30:45 <creith> this is what I sometimes don't understand
00:31:43 <creith> in the source code
00:33:52 <RhodiumToad> what in there is C11?
00:38:54 * checkpoint has just lookped through /usr/src/bin/echo/main.c and could admit that man page for echo is bigger than the source code
00:40:06 <RhodiumToad> looking at the history, it seems that once upon a time someone decided that echo could be made smaller by not using stdio (back when /bin could not be dynamic-linked this was more important, and still matters a bit for /rescue),
00:40:21 <RhodiumToad> and then it was changed to use writev() to restore the previous performance
00:42:53 <RhodiumToad> (we're talking 2002-2003 here)
00:42:57 <creith> once upon time ... I would like to meet Ken Thompaon ... but it will never happen ,,,
00:43:23 * RhodiumToad remembers when you could boot off two floppies
00:43:35 <creith> oh, writev() was 99 ... sorry, I get old
00:43:56 <RhodiumToad> writev has been in BSD since... about forever?
00:44:13 <RhodiumToad> since 4.2BSD anyway
00:44:36 <RhodiumToad> and therefore since 1983
00:44:39 <creith> I remember a Schneider CPC128 ... you didn't need floppies to boot
00:45:17 <creith> 1983 was UNIX very far away from me, I was 8
00:45:33 <RhodiumToad> I first used unix in about 1988
00:45:47 <RhodiumToad> and freebsd in 1997
00:46:12 <creith> writev is that old ... ok ... forgive the young guy
00:46:57 <creith> My first Linux was in 1996, the X configuration shredded my gf's monitor
00:47:06 <RhodiumToad> looks like writev was added to the spec in XPG4.2
00:47:07 <creith> hahaha
00:47:35 <RhodiumToad> ah, the days of writing your own modelines for X
00:47:54 <creith> I am not good in history ... I still think it's overkill for echo
00:48:03 <RhodiumToad> using writev?
00:48:07 <creith> oh yes, the modelines
00:48:41 <RhodiumToad> looping over write() uses a lot of system cpu for echoing many arguments
00:48:52 <creith> echo can be written in still plain 89 C in 20 lines ...
00:49:33 <creith> hey, it was just an example .. the simplest I could think of
00:49:35 <RhodiumToad> looping over puts() doesn't use much system cpu but, as I said, back in the days when /bin had to be static linked it bloats the binary quite a bit
00:50:10 <RhodiumToad> arguably it could be changed back to using stdio now that it's dynamic linked
00:50:22 <creith> FreeBSD tends to have bloated coat ... but hey it's Friday
00:52:58 <creith> I don't care much about the 1970s
00:52:58 <creith> UNIX survived becaused it was simple and therefore adoptable
00:52:58 <creith> Greetings VMS ... rest in peace ... I love you
00:58:14 <creith> I will go through usr.bin tomorrow
00:58:14 <creith> Good night everyone
01:00:04 <RhodiumToad> anyone know any reason why a usb thumb drive, unused but plugged in for some weeks/months, would decide to become extremely slow to read?
01:00:43 <RhodiumToad> as in ~3MB/sec for a usb3 device on a usb3 port
01:04:45 <RhodiumToad> I'm pretty sure it was not this slow originally
01:07:36 <checkpoint> RhodiumToad: electrons caught in NAND cells become tired and need rest ?
01:09:36 <RhodiumToad> that is _almost_ a thing :-)
01:09:56 <RhodiumToad> flash cells do need to be written again after a certain number of reads
01:10:32 <RhodiumToad> but (a) nothing was reading the drive and (b) I just completed a full read of all blocks and it's _still_ slow
01:11:44 <checkpoint> is writing slow as well ?
01:11:51 <RhodiumToad> haven't tried
01:12:02 <RhodiumToad> but writing is usually pretty slow anyway
01:13:10 <checkpoint> 3MB/s is way too slow
01:13:31 <RhodiumToad> indeed
01:13:38 <RhodiumToad> esp. for a usb3 device
01:14:09 <checkpoint> good old SD/MMC class 10 does 15MB/s on regular 4 bit socket
01:16:05 <checkpoint> did you try reading it in different USB port ?
01:17:25 <RhodiumToad> yes, no change
01:17:45 <RhodiumToad> also if I stick a usb3 sdcard reader in the same port I can get 80MB/sec reads
01:18:46 <RhodiumToad> sec, I should have another thumbdrive of the same type, unused since purchase - lemme find it
01:20:11 <checkpoint> as it was long time powered, perhaps a voltage regulator got broken which leads to higher error rate
01:21:00 <checkpoint> hence more retransmits/re-reads
01:36:41 <RhodiumToad> ok, unused device of the same type is giving ~95MB/s
01:39:55 <RhodiumToad> so it's definitely not the port :-)
01:43:05 <jauntyd> whew!
01:44:25 <RhodiumToad> no errors are being shown at the USB bus level, so if there are errors/retries then it's inside the device
01:53:29 <RhodiumToad> interesting. write speed when writing zeros to the dodgy device is very high
01:53:46 <RhodiumToad> oh wait, scratch that, it just dropped
02:06:10 <jauntyd> 95MB/s? I don't get but 55MB/s or so
02:08:42 <RhodiumToad> it'll depend a lot on the device I suspect
02:12:12 <RhodiumToad> fastest usb3 drive I have does >220MB/s
02:13:38 <jauntyd> i've hit 200MB/s or so but it doesn't sustain
02:13:50 <jauntyd> that's good
02:13:58 <jauntyd> 220 *whistles*
02:14:21 <spork_css> Anyone know how to set what IP a jail uses as a source address when using iocage?
02:14:57 <spork_css> I've got two external IPs on a jail - one "fixed", the other a CARP IP, which may or may not be up depending on the status of the other CARP member on another host.
02:15:21 <RhodiumToad> vnet jail?
02:15:42 <spork_css> The jail insists on sending traffic out the CARP interface even when it's in "BACKUP" mode.
02:16:02 <spork_css> Nope, old-fashioned non-VNET.
02:16:27 <spork_css> VNET is my next step if I can't figure this out, but I've never used VNET in production, so wasn't crazy about testing it out.
02:16:52 <RhodiumToad> what do ip4.addr and ip4.saddrsel end up set to on the jail?
02:17:24 <spork_css> I've tried changing the order in the "ip4_addr" parameter, and tried "ip4_saddrsel" set to "0" and "1" with the same result.
02:18:07 <spork_css> Testing at home this was fine, but I also had a simpler setup with only a single interface - the actual hosts have an internal and external NIC which seems to play some role in this not quite working.
02:20:56 <RhodiumToad> is the CARP address uses only for a service running in this jail, and not for anything else on the host?
02:21:03 <spork_css> Actually, I take that back about "ip4_saddrsel" - with it set to "0", I can reach the internal network, the external only if the CARP IP is MASTER, and if I set "ip4_saddrsel" to "1" I lose connectivity to the internal network (which is where my DNS resides).
02:21:14 <spork_css> Correct only on the jail.
02:21:32 <spork_css> And I may have a need to move it from host to host in the future.
02:21:47 <RhodiumToad> vnet's probably the way to go then
02:22:26 <spork_css> Yeah, that would make it even more "portable" in that I wouldn't have to have any CARP junk in rc.conf.
02:22:40 <spork_css> ALthough I'm not finding confirmation CARP on VNET is actually supported.
02:24:57 <spork_css> I'm really puzzled on what setting "ip4_saddrsel" does to break the internal network.
02:27:26 <spork_css> The jail (and iocage) manpages are not super clear on what exactly "ip4_saddrsel" - they both use language that references some other part of the manpage that I'm not seeing.
02:27:50 <spork_css> But I feel like what it might be doing is forcing all the internal net traffic out the primary (external).
02:27:58 * spork_css goes to tcpdump this
02:29:13 <spork_css> Yep, pinging something in the internal net sources the ping from the external.
02:29:52 <RhodiumToad> remember that source address selection doesn't necessarily control what interface is used, just what the source address in the packet is
02:30:40 <spork_css> Yeah, I'm seeing that with tcpdump - source from an external IP, but going out the internal net interface.
02:31:07 <RhodiumToad> if source address selection isn't forced, then it should normally match the interface
02:31:30 <spork_css> Just wish there was a way to specify (with "ip4_saddrsel" set to "0"), which IP, by default, traffic is sourced from inside the jail.
02:31:35 <RhodiumToad> since the default is to try and route the packet to its destination, and pick the outgoing interface's primary address as the source address
02:31:37 <spork_css> Config order doesn't do it.
02:32:08 <RhodiumToad> the order of ip4.addrs matters only when normal source address selection fails to match one of the IPs that the jail is allowed to use
02:33:43 <spork_css> And I have it backwards up there, I meant "(with "ip4_saddrsel" set to "1")" not "0".
02:35:22 <RhodiumToad> vnet is at least potentially simpler to understand since the jail has its own network stack to itself
02:36:44 <spork_css> This kind of puzzles me:
02:36:45 <spork_css> [root@clwebX /home/spork]# iocage get ip4_addr haproxy02
02:36:45 <spork_css> ext0|1.2.3.247,1.2.3.248,int0|10.99.88.241/32
02:37:43 <spork_css> I would think 1.2.3.247 would be the default source address, but in any order, it always sources from 1.2.3.248 (which is the CARP IP). Just odd, seems like it should be configurable in some way.
02:38:29 <spork_css> I do not use the "interface|IP" form for the CARP IP because then I end up with the an extra alias for the CARP IP.
02:38:53 <spork_css> (manpage says specifying an interface forces creating an alias)
02:39:16 <RhodiumToad> the one thing I'm unsure of is whether epair supports carp, it's possible it does not
02:39:28 <spork_css> Anyhow, just wanted to check if I was missing anything obvious before I move to a completely new and different setup. :)
02:39:35 <spork_css> I'm about to find out I think!
02:40:04 <spork_css> This just does not seem to be true:
02:40:06 <spork_css> "If a jail requests a specific IP address, the host attempts to add that address as a new alias. All traffic sourced from the jail uses the first IP assigned as the source IP."
02:40:34 <RhodiumToad> I'd _guess_ it should because the common ethernet code handles it, and I think epair uses that
02:40:37 <spork_css> But that's MWL and not the manpage...
02:41:17 <spork_css> Maybe at some point I'm just going to end up using bhyve. :)
02:45:03 <spork_css> I think that "first assigned IP is the source" really translates to "first IP *configured by the jail/iocage* is the source *if* no existing IPs are used by the jail" - meaning the CARP IP is already there, which in some sense makes it "first".
02:47:28 <spork_css> I could also not assign the CARP IP to the jail and instead let the host's devd add/remove it with CARP state changes...
03:02:10 <spork_css> Anyhow, thanks so much for talking me through this mess!
03:03:13 <RhodiumToad> fascinating, the dodgy thumbdrive is sustaining a 20MB/s write speed (which is what it's rated for)
04:21:33 <kenrap> RhodiumToad: 👍
04:38:13 * RhodiumToad 's irc client isn't good at emojis
04:50:27 <kenrap> RhodiumToad: s/👍/*Thumbs up*/
04:50:33 <kenrap> :)
05:10:37 <RhodiumToad> and having zeroed the whole drive, I now get ~130MB/s read speed
05:24:17 <jauntyd> dang, that's very good
05:24:31 <jauntyd> would be for me anyways
05:24:44 <hd1> anyone want to help me fix the scipy port?
05:25:16 <jauntyd> i'm new to porting but i'd like to help. have room for a noob?
05:25:31 * RhodiumToad can advise
05:25:43 <RhodiumToad> how is it broken?
05:26:27 <hd1> it was the last time I installed it, trying again, to see if it still is, hold please?
05:26:45 <hd1> WARNING: Ignoring invalid distribution ~equests (/mnt/extra/ec2-user/.virtualenvs/units/env/lib/python3.11/site-packages)
05:26:46 <hd1> WARNING: Ignoring invalid distribution ~equests (/mnt/extra/ec2-user/.virtualenvs/units/env/lib/python3.11/site-packages)
05:28:01 <hd1> those are the first lines when I try doing a pip install -e from  the extracted make patch directory
05:30:02 <jauntyd> https://www.pythonpool.com/solving-python-ignoring-invalid-distribution/ basically says to delete the "~package name>" dirs
05:30:04 <VimDiesel> Title: Solving Python Ignoring Invalid Distribution - Python Pool
05:36:12 <hd1> ok, pythran reinstalled without issue
05:38:35 <jauntyd> ^5
05:38:47 <Beladona> Whats the best way to turn off drives power to avoid them from spinning?
05:40:42 <RhodiumToad> depends on the drive
05:46:42 <Beladona> RhodiumToad https://pastebin.mozilla.org/EFA3i7VM
05:46:43 <VimDiesel> Title: Mozilla Community Pastebin/EFA3i7VM (Plain Code)
05:52:21 <RhodiumToad> you can probably set the standby timer using smartctl
05:55:31 <Beladona> Can I unmount the drives and use camcontrol standby adaX to turn off the spindle on HDDs and camcontrol idle adaX to spin it back up.
05:55:35 <Beladona> RhodiumToad ^
05:55:54 <Beladona> or I need `powerd`?
05:56:56 <RhodiumToad> do you particularly need to unmount them?
05:57:35 <RhodiumToad> (rather than just having them spin down when idle)
05:58:08 <Beladona> those are backup drives. I don't want to keep them running except a bi weekly backup time
05:58:39 <Beladona> RhodiumToad I would prefer full power off. But as those are on sata cable, I can't just plug them off
05:58:44 <Beladona> updated https://pastebin.mozilla.org/AH4Ktr2i#L1
05:58:45 <VimDiesel> Title: Mozilla Community Pastebin/AH4Ktr2i (Plain Code)
05:59:41 <Beladona> but I may want them to reuse them. so what are my options
06:03:38 <RhodiumToad> if they're not mounted, then by all means try camcontrol standby
06:05:28 <Beladona> RhodiumToad so umount, standy and mount again to use? thats all
06:07:23 <RhodiumToad> should do
06:07:42 <RhodiumToad> however, rebooting the machine will probably spin them up again even if not mounted
06:08:02 <Beladona> RhodiumToad my/all hdd support this? I don't need EPC or whatever? also i don't need powed?
06:08:36 <RhodiumToad> you don't need powerd. not all hdd support it, try it and see if it works
06:09:17 <Beladona> ok. I usually do this : gelli attach /dev/adaX   <- this i the point where it is mounted?
06:09:42 <Beladona> Current power state: PM0:Active or PM1:Idle(0xff)  <---- its onn, as you said, even not mounted
06:09:50 <RhodiumToad> that doesn't mount it, that just attaches it for decryption, but that will access the drive so it should spin up
06:09:53 <Beladona> I am doing standby to check
06:10:23 <Beladona> then maybe `zpool import ..` will
06:10:30 <Beladona> then maybe `zpool import ..` will mount it
06:12:27 <Beladona> How to check the device state after standby?
06:12:37 <Beladona> that it was really on standby now
06:13:06 <RhodiumToad> what does it report now for current power state?
06:13:26 <Beladona> camcontrol epc ada3 -c status  -> Current power state: PM0:Active or PM1:Idle(0xff)
06:13:37 <Beladona> same as before. nothing changed
06:13:40 <RhodiumToad> well it might not support it then
06:13:41 <Beladona> despite standby
06:13:58 <Beladona> EPC: Supported, NOT Enabled
06:14:17 <Beladona> Low Power Standby NOT Supported
06:14:24 <Beladona> Set EPC Power Source NOT Supported
06:14:31 <Beladona> APM: NOT Supported, NOT Enabled
06:15:21 <Beladona> RhodiumToad I am doing camcontrol epc ada3 -c enable
06:15:45 <Beladona> Now, EPC: Supported, Enabled
06:16:12 <Beladona> its still. Current power state: PM0:Active or PM1:Idle(0xff)
06:16:17 <RhodiumToad> when you query the status, use  camcontrol epc ada3 -c status -P
06:16:41 <Beladona> same
06:16:41 <Beladona> Current power state: PM0:Active or PM1:Idle(0xff)
06:17:39 <RhodiumToad> camcontrol epc ada3 -c goto -D -p Standby_z
06:17:45 <RhodiumToad> then  camcontrol epc ada3 -c status -P
06:18:58 <Beladona> that worked
06:19:33 <Beladona> Current power state: Standby_z(0x00)
06:19:36 <Beladona> I wonder
06:22:04 <Beladona> Why it says active if I don't use -P
06:22:35 <Beladona> camcontrol idle ada3 , camcontrol epc ada3 -c status -P
06:22:35 <Beladona> Current power state: Idle_a(0x81)
06:23:10 <RhodiumToad> some commands will bring it out of standby
06:23:27 <RhodiumToad> without -P, that status option issues several commands
06:24:01 <Beladona> so I need EPC: Supported for any of this to work?
06:24:08 <RhodiumToad> yes
06:25:29 <Beladona> no other option?
06:26:04 <Beladona> so without -P , the other commadns make it active again?
06:26:22 <hd1> https://pastebin.com/UZTnBMyD
06:26:23 <VimDiesel> Title: In file included from scipy/stats/_stats_pythran.cpp:34: In file inc - Pastebin.com
06:26:58 <hd1> that's the error pip install encounters from the port
06:27:25 <hd1> incidentally, an install into the linuxulator works without problem
06:27:32 <hd1> (using ubuntu)
06:30:48 <RhodiumToad> hd1: what are you doing exactly?
06:31:14 <hd1> still messing with the scipy port
06:31:23 <RhodiumToad> no, what exact commands are you doing
06:32:59 <hd1> pip install -e . from the work-py311/scipy-1.10.1 directory
06:33:08 <RhodiumToad> why are you doing that?
06:33:45 <hd1> because make install installs the package globally and I want it only in this vitrualenv
06:33:49 <Beladona> RhodiumToad confusion. as per https://serverfault.com/questions/1047331/how-do-i-disable-hard-disk-spin-down-or-head-parking-in-freebsd , `camcontrol epc ada3 -c state -d -p standby_z` is used to disable spin-down (Standby_z) via EPC?
06:33:50 <VimDiesel> Title: How do I disable hard disk spin down or head parking in FreeBSD? - Server Fault
06:34:41 <RhodiumToad> but you don't want to disable it, do you
06:35:01 <Beladona> no
06:35:13 <Beladona> but the command says that it will disable it
06:35:21 <RhodiumToad> hd1: that's not the port's problem. the port exists to build a package which you can install on your system
06:35:30 <Beladona> but actually it PUT it on standby <-- desired
06:35:35 <Beladona> hence the confusion
06:35:36 <RhodiumToad> hd1: if you want to do something else, you're on your own
06:35:55 <RhodiumToad> Beladona: that command is not the one I told you to use
06:36:12 <RhodiumToad> goto != state, -d != -D
06:36:29 <Beladona> oh I missed that
06:36:54 <Beladona> thanks, i think that is all I need
06:38:12 <Beladona> (I guess)
06:38:28 <Beladona> No need for head parking either
06:38:32 <Beladona> (I guess)
06:50:40 <rtprio> probably ok if you don't plan on dropping your computer
06:56:21 <Beladona> rtprio so power outage will hurt?
06:56:30 <Beladona> How to know in depth, where is the disk consumed? which files take most space
06:57:26 <pstef_> maybe ncdu
07:04:35 <RhodiumToad> du -k | sort -rn
07:06:13 <rtprio> Beladona: the heads won't hit the discs in that case
07:09:20 <Beladona> RhodiumToad du -h -depth=2 /* | sort -rhb > /tmp/disk.txt ?
07:09:37 <RhodiumToad> no
07:09:41 <Beladona> I see
07:10:25 <Beladona> rtprio on reboot, they will. I mean no danger in doing this standby/idle thing in power managment?
07:11:06 <RhodiumToad> it's in all respects safer than having the drives running
07:13:23 <Beladona> RhodiumToad you mean, having it on standby / idle is better and safer?
07:13:44 <RhodiumToad> yes
07:14:57 <Beladona> ok
08:37:03 <qmr> Error loading module '/usr/local/lib/samba4/modules/vfs/fruit.so': /usr/local/lib/samba4/private/libsmbd-base-samba4.so: version SAMBA_4.16.11_SAMBA4 required by /usr/local/lib/samba4/modules/vfs/fruit.so not found
08:37:43 <qmr> both of those files exist
08:39:38 <qmr> huh restarting samba and it's working now
08:40:25 <RhodiumToad> let me guess, you upgraded it while it was running
08:41:12 <RhodiumToad> it wasn't complaining that the file didn't exist, it was complaining that it didn't define the symbol version that it was expecting
08:45:31 <qmr> very possible
09:28:30 <RhodiumToad> ... fascinating, having overwritten this thumbdrive with random data, it's now performing at full speed for reads, >30x faster than before
09:53:34 <kenrap> RhodiumToad: would this be something that's usb related or filesystem related?
10:04:47 <RhodiumToad> can't be either
10:05:07 <RhodiumToad> mostly I was testing with dd, bypassing the filesystem
10:12:19 <pstef_> no UAS(P)
10:13:45 <RhodiumToad> ?
10:14:31 <pstef_> I'm "complaining" about the lack of UAS(P) support in FreeBSD
10:14:44 <pstef_> https://lists.freebsd.org/pipermail/freebsd-hardware/2017-November/007921.html
10:14:45 <VimDiesel> Title: USB Attached SCSI (UAS/UASP) support and fallback to BOT
10:15:44 <RhodiumToad> for this example, that's not really relevant
10:17:46 <pstef_> for this example, perhaps not, I don't know what this example is
10:20:04 <RhodiumToad> ludicrously slow reads from a thumbdrive, but it's now really fast again after overwriting it all
10:22:33 <pstef_> ah, well, without much thought I'd be quick to blame the firmware
10:34:18 <vkarlsen> Saved by randomness
11:36:40 <qmr> Any ideas how my zfs on root resized before my eyes?  it was 4.9 of 4.9 , then when I'm struggling to free some space 4.9 out of 16
11:40:21 <RhodiumToad> it's very easy to forget about space used by snapshots
11:50:19 <qmr> yes I removed many.  but I'm confused why it would change the available space?  the snapshots were also only hundreds of megs at most
11:50:39 <qmr> then it suddenly became 4.9 out of 16.  some housekeeping that happened many minutes later?
13:25:11 <kyonsalt> hello,I met trap about the freebsd install mountroot error 19 problem. Even in usb mode or isoemu mode to load freebsd13.2-amd64-bootonly.iso.
14:10:13 <Beladona> Unable to understand why I got rebooted when I tried to resume screen off by mouse ( I did this few hours ago `sleep 1; xset -display :0.0 dpms force off`)  /var/log/messages: https://pastebin.mozilla.org/1vTsbXLn
14:10:14 <VimDiesel> Title: Mozilla Community Pastebin/1vTsbXLn (Plain Code)
14:36:43 <redlegion> I'm having a hell of a time installing alacritty.info on FreeBSD
14:37:19 <redlegion> I can't get it to set terminal capabilities correctly
14:37:47 <redlegion> the weirdest part is that installing alacritty on the freebsd host doesn't even seem to allow TERM to be set to `alacritty`
15:14:43 <kyonsalt> damn,I create a new usb stick with ventroy, debian could install. but freebsd13.2 still enter mountroot error 19 problem.`
15:24:16 <Beladona> Disconnected
15:24:17 <Beladona> Unable to understand why I got rebooted when I tried to resume screen off by mouse ( I did this few hours ago `sleep 1; xset -display :0.0 dpms force off`)  /var/log/messages: https://pastebin.mozilla.org/1vTsbXLn
15:24:19 <VimDiesel> Title: Mozilla Community Pastebin/1vTsbXLn (Plain Code)
15:27:33 <kyonsalt> OK,I think it's a bug of freebsd13.2.iso. I just try ventroy+freebsd12.4-bootonly.iso, it cloud install normally.
17:24:33 <rtprio> redlegion: how are you installing it?
17:25:19 <rtprio> kyonsalt: use the .img for usb sticks; what are you installing on?
17:25:48 <rtprio> qmr: yes, i believe snapshot deletes happen in the background
17:45:52 <Beladona> How can I know who triggered this boot? https://pastebin.mozilla.org/1vTsbXLn#L90,91,92,93
17:45:53 <VimDiesel> Title: Mozilla Community Pastebin/1vTsbXLn (Plain Code)
17:56:45 <rtprio> a crash would be my guess
19:21:23 <markmcb> anyone know if much change is coming to bhyve sr-iov with 14? i can consistently trigger a crash when i start the install process for freebsd in bhyve using a chelsio T520 passed through pci device. the whole card will freeze about 2-3 mins. any attempt to reset the device triggers a panic.
19:21:53 <markmcb> it's not critical. just wondering if i should report a bug, or wait and see in a few weeks.
19:25:05 <michaeldexter> markmcb: Several of us have been tracking this on the bhyve call, notably John D and Santiago M. What is the key PR that is impacting you?
19:27:38 <markmcb> michaeldexter: PR=pull request? i'm running on 13.2 RELEASE. Haven't tested at all with changes in STABLE or CURRENT.
19:27:57 <michaeldexter> Problem Report.
19:28:39 <markmcb> ah, sorry. i haven't reported it yet. i can browse and look for a match.
19:29:26 <markmcb> i assume bugs.freebsd.org is the place to look?
19:29:53 <michaeldexter> Do look at 234073 271456 270966 and 266325
19:30:24 <markmcb> thanks, will do
19:31:05 <michaeldexter> And possibly 269133 269133 263046. Thank you! Do report back and share any new information you can in the tickets.
19:32:31 <markmcb> 234073 for sure is still an issue. i'm the last comment on that one. that was on an X710-DA2, which seemed quirky in general. i've replaced it with a Chelsio T520.
19:35:03 <markmcb> the rest don't quite match. i can passthrough the device and load the driver for it. shortly after though i'll experience the freeze, which kills the whole card, i.e., event the host loses networking.
19:35:17 <markmcb> *even
19:36:26 <michaeldexter> markmcb: Is the Chelsio giving you issues too?
19:36:36 <markmcb> Yes
19:37:09 <markmcb> the freeze i was describing is with the Chelsio
19:38:00 <michaeldexter> Do mention that in the ticket if it’s not there already.
19:38:01 <npn> I use Chelsio cards passed through into bhyve VMs for almost all cxgbe(4) development.
19:38:19 <michaeldexter> Are you using SR-IOV?
19:38:20 <npn> Are you passing through SR-IOV devices or the main PF (physical function)
19:38:30 <npn> no I'm not using SR-IOV
19:38:50 <npn> I know of a problem in 13.2 that seems to be fixed in 14-Stable
19:38:52 <markmcb> T520-SO-CR, have 4 SR-IOV VFs set to passthough
19:39:20 <michaeldexter> markmcb: Have you tested on 14?
19:39:25 <npn> what is the exact failure?  a bhyve hang or something else?
19:39:32 <markmcb> SR-IOV works without issues in jails and the VFs not set to passthrough in iovctl.conf
19:39:58 <markmcb> michaeldexter: not yet, was waiting for the first version i can get to with freebsd-update
19:40:18 <npn> file a bug if you see the problem with 14
19:40:28 <npn> and I'll fix it before release
19:40:45 <npn> (if it's in the driver)
19:41:02 <markmcb> npn: i'd have to trigger it again for specifics. i'll do that today and capture it all in a PR
19:42:26 <michaeldexter> markmcb: Do you have hands-on access to the hardware or is it in a distant colo?
19:42:41 <markmcb> hands on, it's in a rack in my garage
19:43:54 <michaeldexter> markmcb: For quick tests, I use this script, which can dd a VM-IMAGE on a physical device, and boot it with a USB to SATA adapter: https://github.com/michaeldexter/occambsd/blob/main/imagine.sh
19:43:55 <VimDiesel> Title: occambsd/imagine.sh at main · michaeldexter/occambsd · GitHub
19:44:22 <michaeldexter> Ping me if you have any questions though I am not always on IRC.
19:44:55 <markmcb> ok, thanks
19:45:12 <michaeldexter> NP
19:45:19 <npn> I had a report of the 13.2 SR-IOV cxgbev driver failing to attach on a hyper-v host (no bhyve there).  I could see PCIe problems (misconfigured BARs) even before an attempt to load the driver.  I assumed there was a bug in the pcie code in 13.2 and tried 14.0-alpha1, which worked., and I dropped the debug.
19:45:43 <npn> take a look at pciconf -lvbc before you load the driver (in case you see miconfigured BARs too)
19:45:44 <michaeldexter> Noted
19:48:13 <markmcb> npn: you check on the host or guest? i'm not sure what to look for to identify a misconfigured BAR. i see bar line items on the host, but not sure what they should/shouldn't be
19:49:55 <npn> look in the guest.  In my case one of the BARs had an address with all ffs in the upper bits and that's not a valid phys addr, and the BARs were not enabled either.
19:50:35 <npn> boot the guest in verbose mode and the pcie drivers will print this info too when they enumerate the devices
19:51:08 <markmcb> ok, i'll give that a look. thanks.
20:28:12 <_xor> What are my options for a command included in base, that supports libxo ideally, to see which PIDs have open handle(s) to a given file? (specifically in my case, I'm looking to add a rule to devd that sends SIGHUP to any PIDs holding open /dev/dsp6 when my headphones become unplugged)
20:28:44 <_xor> I know there's fstat, but from what I can tell, it doesn't support libxo, which means awk/cut/whatever to hack the output text.
20:31:12 <_xor> My USB headphones come unplugged every once in a while and Firefox doesn't release /dev/dsp6 when there are tabs open with an audio player (even if paused). So I figure I'll add a short script that's triggered by devd for the headphones to get a list of PIDs holding it open and send SIGHUP so that it gets released. When the headphones are plugged
20:31:12 <_xor> back in, they don't show up as a dev device until dsp6 is released (and I don't want to just tell it to create a new dspX device and set it as the default).
21:35:11 <Erhard> Anyone know of a tool that would let me spoof a response to a broadcast packet to then reply with an address on a different subnet? I have a device that only uses broadcast packets to find the server to connect to, and doesn't permit direct ip entry in the client. I'd like to have the server on a different subnet, but the client can't find it because it will only find it via broadcast.
21:39:07 <vxwarlock> Erhard > broadcast L2 feature | cannot leave the subnet it is on
21:39:33 <Erhard> Yeah, that's the issue. I think I may need to listen for the broadcast and sniff the protocol and reply with the correct ip
21:40:13 <Erhard> The client is closed source and they refuse to allow direct ip entry because they think it might confuse users (idiots)
21:40:37 <Erhard> But my wifi is on a separate subnet and I would like to connect from it...
21:41:48 <vxwarlock> If you are in a different subnet, there should be a routing once in a while.
21:42:44 <Erhard> Not sure I know what that means. There is routing, and that is via a FreeBSD box.
21:43:03 <Erhard> BUt the clinet owuld be on wifi, which is a different subnet from the LAN where the server is.
21:43:17 <vxwarlock> 192.168.1.0/24 wifi ; 192.168.2.0/24 cllient = L3 routing
21:43:35 <Erhard> Yeah. I have that setup... but the broadcast bit is layer 2
21:45:49 <Erhard> Maybe I can do an IP alias.. I guess I will do some more research
21:46:37 <vxwarlock> Sorry, I don't fully understand what you want to do. I can't help.
21:47:02 <TommyC> Erhard: do you need a fully fledged tool, or will a framework that's done some heavy lifting be enough?
21:47:09 <TommyC> (albeit you have to know how to use the framework, but still)
21:47:39 <Erhard> It's OK. I will do some more research. What I want is client on 192.168.0.0/24 to connect to server on 192.168.1.0/24, but the client will ONLY locate the server via broadcast, and does not permit entry of a server IP.
21:48:01 <Erhard> It's a one off for this one client/server.
21:48:05 <Erhard> Can be hacky.
21:48:43 <TommyC> Erhard: If you're familiar with python, I'm 99% sure the python scapy module can do what you want.
21:48:51 <Erhard> If I can sniff the ptotocol the client uses to sommunicate with the server via broadcast then perhaps I can mimic that with python
21:49:01 <Erhard> scapy? OK. I will look at that, thanks.
21:49:55 <Erhard> This looks good. Thanks. bbl
22:32:34 <markmcb> michaeldexter: following up from earlier, I added 273372
22:33:10 <markmcb> npn: see above message
23:04:30 <nevafrost> Hey, new to freebsd I have issues with pkg's network speed I tried using mirrors but fastest I get is 400kb/s
23:04:58 <nevafrost> I tried to post the issue on freebsd forums before but coudn't find a solution
23:15:21 <skered> Who do you have to poke to get zfs-get to list props in alpha sort?   All things zfs are now an upstream project?
23:17:21 <skered> sys/contrib/openzfs makes me thing it is
23:27:50 <markmcb> I see "ALPHA" referenced in the freebsd-update man page. is that a normally available option? looking at the 14 schedule, i only see BETA referenced.
23:56:15 <debdrup> markmcb: I think it's an artefact of the manual pages being built on 14-CURRENT, which is technically speaking 14.0-ALPHA2 right now (if it hasn't moved onto ALPHA3)
23:57:09 <debdrup> skered: github.com/openzfs/zfs