Looking for feedback on change to iflib and transmit queuing

that iflib_parse_header() does tons of unnecessary m_pullups() on small UDP packets; as much as 10% of the CPU time can be spent just doing that. It should maybe get modified to not pull-up to the TCP header length for UDP packets. - Eric

review: kernel GDB: do not reboot the target

on Phabricator, see: https://wiki.freebsd.org/Phabricator Cheers, Eric

Re: PAM module for loading ZFS keys on login

ting that apparently they change the key to the dataset when the user changes their password. Anyway, I've seen enough. I'm going to abandon the review for my PAM module and use the upstream one. I'm going to keep the review for the autounmountd patch live, though. On 9/6/21 2:53 PM, Steff

Re: PAM module for loading ZFS keys on login

data after I'm gone.) On 9/6/21 10:01 AM, Steffen Nurpmeso wrote: > Eric McCorkle wrote in > : > |Interesting, I wasn't aware of the upstream module. I'd say that's > > It's existence was the reason i have readded (now optional, and > a tad different) session support for my

Re: PAM module for loading ZFS keys on login

Interesting, I wasn't aware of the upstream module. I'd say that's preferable to the one I wrote. I think you would need to wire that into the 'modules' directory under libpam. I can look into doing that. On 9/5/21 11:27 AM, Greg wrote: > > > On September 5, 2021 4:54:26 PM GMT+03

PAM module for loading ZFS keys on login

All, This patch creates a new PAM module that will load a ZFS key upon a successful login: https://reviews.freebsd.org/D31844. It will use the user's auth token as the key argument to loading a ZFS encryption key on a user-specific ZFS data set. This is the other side of my changeset to have

Re: Alternate Screen

On 5/17/21 9:53 AM, Baptiste Daroussin wrote: On Mon, May 17, 2021 at 09:46:49AM -0500, Eric van Gyzen wrote: On 5/17/21 5:19 AM, Gary Jennejohn wrote: On Sun, 16 May 2021 19:03:07 +0200 Baptiste Daroussin wrote: On Thu, May 13, 2021 at 09:01:53AM -0500, Eric van Gyzen wrote

Re: Alternate Screen

On 5/17/21 5:19 AM, Gary Jennejohn wrote: On Sun, 16 May 2021 19:03:07 +0200 Baptiste Daroussin wrote: On Thu, May 13, 2021 at 09:01:53AM -0500, Eric van Gyzen wrote: There was a recent discussion about a terminal database update and the new Alternate Screen behavior. I'm curious about

Alternate Screen

back, with no alternate screen, and thereby reduce my blood pressure. Alternatively yours, Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-cu

Re: Link flap when adding / removing a vlan (was Re: r360902 breaks VLAN interface on if_em (82579LM))

devices need a restart / which devices do not, or whether a restart is strictly necessary and if there is another way to do this without worrying about restarting the device. - Eric On Fri, Nov 6, 2020 at 3:35 PM mike tancsa wrote: > On 11/6/2020 5:32 PM, Eric Joyner wrote: > > Could

Re: Link flap when adding / removing a vlan (was Re: r360902 breaks VLAN interface on if_em (82579LM))

Could you reply to that issue with what you've found? Though, as far as I can recall, igb(4) devices are not supposed to do the iflib reset talked about in the bug, so I wouldn't expect to see a link flap on those. - Eric On Fri, Nov 6, 2020 at 12:48 PM mike tancsa wrote: > On 11/6/2020 2

top ARC stats are wrong

+84ccaf49083c-c272054. I'll look into it when I have time, but that won't be soon. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-uns

Re: ZFS crash -- zvol_geom_bio_getattr called when volmode=dev

On 10/9/20 7:54 PM, Eric van Gyzen wrote: On 10/9/20 6:27 PM, Ryan Moeller wrote: On 10/9/20 6:22 PM, Alan Somers wrote: This sounds like it might be a regression introduced by the OpenZFS merge. Have you compared vdev_geom.c in OpenZFS vs the old version? -Alan I don't think vdev_geom.c

Re: ZFS crash -- zvol_geom_bio_getattr called when volmode=dev

ody() at g_down_procbody+0x5c/frame 0xfe000edcdbb0 fork_exit() at fork_exit+0x80/frame 0xfe000edcdbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe000edcdbf0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- (The other CPUs were idle.) On Fri, Oct 9, 2020 at 3:48 PM Eric van Gyzen wrote: On 10/9/20 4

Re: ZFS crash -- zvol_geom_bio_getattr called when volmode=dev

On 10/9/20 4:39 PM, Eric van Gyzen wrote: Does this look familiar?  I'm creating a zvol with volmode=dev, but some geom code paths were taken.  If this looks new, I'll provide more details. primarycache=none also seems to be a factor. I can easily repro with: zfs create -s -V 10G -o

ZFS crash -- zvol_geom_bio_getattr called when volmode=dev

Does this look familiar? I'm creating a zvol with volmode=dev, but some geom code paths were taken. If this looks new, I'll provide more details. Thanks in advance, Eric 13.0-CURRENT r366500+84ccaf49083c-c272054 GENERIC #8 #9 zvol_geom_bio_getattr (bp=0xf80376132900) at /usr

Problem with zfs.ko: lockstat_enabled symbol

I recently updated my other laptop, and now I'm getting a problem loading zfs.ko at boot, relating to the lockstat_enabled symbol not being defined (this happens during kernel boot and prevents mounting root, so I can't get an exact trace) Looking at the new kernel, it seems that only zfs.ko

LOR: tun_ioctl after tun_mtx

I see this LOR on head r364364 while running the tcptestsuite (ports/net/tcptestsuite). In fact, I interrupted a test with Ctrl-C, and got a panic. I assume it's the same, since the test was twiddling the MTU, but I haven't looked closely. Eric lock order reversal: (sleepable after non

Re: ${COMPILER_VERSION} < 40300

If I were to clean up obsolete ${COMPILER_VERSION} tests in the tree, which ones should I keep?  I would probably confine it to head, so I could prune quite a few. Thanks for the feedback, everyone. If you're interested: https://reviews.freebsd.org/D24802 Eric

Re: ${COMPILER_VERSION} < 40300

On 5/8/20 1:22 PM, John Baldwin wrote: I think Eric though was asking about and the like. Actually, I was asking about makefile conditions, but this is still a good discussion to have. I'm in a cleanup mood. (BTW, it would be good to know if it's at all useful to keep any of the icc bits

${COMPILER_VERSION} < 40300

If I were to clean up obsolete ${COMPILER_VERSION} tests in the tree, which ones should I keep? I would probably confine it to head, so I could prune quite a few. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman

toolchain status

Which architectures are still often built with an external toolchain? I'd like to re-commit jemalloc 5.2.1. It was reverted because "compilation fails for non-llvm-based platforms." I just built tinderbox worlds with 5.2.1 with no problems, albeit with ll

Re: Working on Zoom port

On 4/13/20 2:59 PM, Pete Wright wrote: > Thanks Eric, I remember trying to get this working several months ago > via the linux compatibility layer and got stuck.  i hope to take another > wack at it based on your repository.  in my ideal world i'd be able to > get this working i

Re: Working on Zoom port

On 4/12/20 9:58 PM, Rodney W. Grimes wrote: > You are aware of the rather large pile of recent security issues > surronding zoom I hope. > I am. All the same, some of us have to use it for work... signature.asc Description: OpenPGP digital signature

Working on Zoom port

All, Given how Zoom is getting used a lot more these days, I've started working on a port that installs the Zoom linux client. Here is a link to my github if anyone wants to help: https://github.com/emc2/freebsd-ports/tree/zoom I'm not done yet. The zoom linux client installs a bunch of Qt

spurious(?) userland malloc/mmap failure

bin/clang/llvm-objdump, so maybe the machine was under memory pressure. It's a bhyve VM with 8 CPUs and 8 GB RAM. The full build log is: https://people.freebsd.org/~vangyzen/2010-01-13-buildworld.txt Eric ___ freebsd-current@freebsd.org mailing list

Re: ffs_fhtovp: inode overflow?

On 12/11/19 3:55 PM, Konstantin Belousov wrote: On Wed, Dec 11, 2019 at 10:26:41AM -0600, Eric van Gyzen wrote: Since ino64 went in, Coverity complains that the two "ino >= foo" comparisons in ffs_fhtovp() compare a 64-bit value to a 32-bit. Is this a problem in practice? I

ffs_fhtovp: inode overflow?

Since ino64 went in, Coverity complains that the two "ino >= foo" comparisons in ffs_fhtovp() compare a 64-bit value to a 32-bit. Is this a problem in practice? Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebs

Re: dtrace not working on bhyve VM without invariant_tsc

s. Pinning the VM to CPUs 1-N (i.e. avoiding CPU 0) worked around it. You might try that as a workaround. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: kernel module code coverage

dows/macOS fixes), so it's still possible we'll see 8.16.6 or 8.16.7 for FreeBSD later, absent any official messaging. On Fri, Dec 6, 2019 at 11:08 AM Jamie Landeg-Jones wrote: > Eric Joyner wrote: > > > I'm reviving an ancient thread, but is Bullseye truly dropping FreeBSD > >

Re: kernel module code coverage

I'm reviving an ancient thread, but is Bullseye truly dropping FreeBSD support? Do you have a link to something that shows that? I still see a FreeBSD tarball in their download archive page for the newest version of their tool, which seems to be 8.16.5. - Eric On Thu, Aug 8, 2019 at 12:08 PM

Re: Can't boot current under bhyve on current

Ok, if I run the bhyve commands manually, then I get a serial console. So something is just borked with vm-bhyve and its use of tmux. Whew. (Now I don't know *what*, but that's at least progress in my diagnosis!) ___ freebsd-current@freebsd.org

Re: Can't boot current under bhyve on current

Ok, with debug=yes I see that it *is* running the VM -- but I have no serial console? This may be operator error here, which is a big relief. An update after I get back from the vet :). Thanks! Sean. ___ freebsd-current@freebsd.org mailing list

Re: Can't boot current under bhyve on current

>Could you test with larger memory setup - instead of 512M, 1-2G? I tried multiple vcpus and 1G of RAM; it made no difference (to either my attempting to boot the system I built, or the ISO; just confirmed the ISO with 1G). Sean. ___

Re: Can't boot current under bhyve on current

>I think vm-bhyve hides stderr output from bhyve by default, but there might >be a flag to make it display the stderr output. Can you try doing that to see >if bhyve is reporting an error? Alternatively, can you see if the bhyve >process is still running? The log file from it is below. bhyve

Can't boot current under bhyve on current

I get: Loading kernel... /boot/kernel/kernel text=0x16c493c data=0x1c8b38+0x819238 syms=[0x8+0x180c18+0x8+0x19df0b] Loading configured modules... can't find '/boot/entropy' \ Note that I am using vm-bhyve as a management & control wrapper, so

Re: FreeBSD and Coreboot

:nwhiteh...@freebsd.org>> > > wrote: > > > >> > >> On 2019-05-27 15:50, Eric McCorkle wrote: > >>> On 5/27/19 5:53 PM, Edward Napierala wrote: > >>>> On Mon, 27 May 2019 at 16:14, Eric McCorkle >

Re: FreeBSD and Coreboot

On 5/27/19 11:13 AM, Eric McCorkle wrote: > My plan is roughly this: > > * Refurbish the GRUB port, get it working again in QEMU (possibly on one > of my machines), also possibly push a patch to GRUB to use the keybufs > mechanism to pass in GELI keys. I managed to get the grub2

Re: FreeBSD and Coreboot

On 5/27/19 5:53 PM, Edward Napierala wrote: > On Mon, 27 May 2019 at 16:14, Eric McCorkle wrote: > > [..] > >> My plan is roughly this: >> >> * Refurbish the GRUB port, get it working again in QEMU (possibly on one >> of my machines), also possibly pus

FreeBSD and Coreboot

Hello everyone, I'm through enough of my job change that I can start working on FreeBSD again. One thing I've had on my list to examine is using FreeBSD with coreboot, so I wanted to put out a call for anyone who has done work on this, or knows anything about it. Here is what I know: *

Re: Building freebsd on another OS

ys2 to get it to compile on Windows. I'll go see if I'm allowed to use Hyper-V on my company-issued laptop... - Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

Re: Building freebsd on another OS

On Sun, Mar 17, 2019 at 6:35 AM Hans Petter Selasky wrote: > > See the freebsd-build utils package for Linux. > > --HPS > > Is there anything for Windows? - Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.or

Re: problem building dev/e1000

lib is now explicitly a module that needs to be included in your kernel config if you want to use a driver that depends on it. It's already in the GENERIC kernel for amd64; are you using a kernel config file that doesn't inherit from GENERIC? - Eric ___ freeb

Re: problem building dev/e1000

more general update since it looks like it's out of date). Though, there is at least a mention of it using iflib near the bottom. - Eric On Fri, Feb 15, 2019 at 10:53 AM Enji Cooper wrote: > > > On Feb 15, 2019, at 10:46, Eric Joyner wrote: > > > > ifdi_if.h is a system gene

Re: Networking panic on 12 - found the cause

switch (pfil_run_hooks(V_link_pfil_head, , ifp, PFIL_OUT, 0x80ce5321 <+81>:mov%gs:0x0,%rax 0x80ce532a <+90>:mov0x500(%rax),%rax => 0x80ce5331 <+97>:mov0x28(%rax),%rax I think this is part of the V_link_pfil_head. I'm not very

toolchain(s) for universe kernels

I want to make MAKE_JUST_KERNELS=1 universe but it seems that I need a toolchain first. There are multiple toolchain-ish make targets. If I start with an empty obj, which toolchain target(s) should I build? Eric ___ freebsd-current

Re: 12-BETA1 contains warning about non-PNP ISA device

rboard has a PS/2 connector, so I could actually use this driver someday. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Hyper-V FreeBSD-CURRENT Guest and SR-IOV Pass Through

None of the Intel networking drivers on FreeBSD support Hyper-V. Could you try "Discrete Device Assignment" instead? Create the VFs on the host somehow, then pass them through to the VMs? That looks like it might work for the FreeBSD VF drivers. - Eric On Mon, Oct 22, 2018 at 12:11

Re: OpenSSL 1.1.1 Update report (ongoing)

* gnome-vfs: C compile errors related to openssl, no viable mitigation Almost done now, though ptlib and gnome-vfs may cause runtime trouble On 10/14/18 7:13 PM, Eric McCorkle wrote: > * ptlib; Fails to build, due to C compiler errors arising from > source-level incompatibilities. Thi

Re: OpenSSL 1.1.1 Update report (ongoing)

of opal. * ffmpeg: autoconf fails to detect openssl. Probably easily fixable, but the trivial workaround is to tick the GNUTLS option (emacs ends up dragging in GNUTLS anyway, so it doesn't add more packages) On 10/14/18 1:31 PM, Eric McCorkle wrote: > More: > > * ImageMagick (

Re: OpenSSL 1.1.1 Update report (ongoing)

. Currently a little over halfway through. On 10/14/18 9:18 AM, Eric McCorkle wrote: > I'm currently in the process of updating my laptop, rebuilding world, > then rebuilding *all* ports. I have a large number of ports installed > (around 1200), and I tend to select a lot of buil

OpenSSL 1.1.1 Update report (ongoing)

I'm currently in the process of updating my laptop, rebuilding world, then rebuilding *all* ports. I have a large number of ports installed (around 1200), and I tend to select a lot of build options. This report is intended to help shake out issues relating to OpenSSL 1.1.1. I'll be adding to

iflib_timer hits hung label; never recovers

to test this code path. :) Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: r339289 buildworld stopped in /usr/src/secure/lib/libcrypto

I'm seeing this one, and am dead in the water from it :( On 10/11/18 3:07 PM, Glen Barber wrote: > On Thu, Oct 11, 2018 at 09:05:52AM +0200, Raúl wrote: >> Maybe related to recent Glen's Heads-UP? >> >> https://lists.freebsd.org/pipermail/freebsd-current/2018-October/071581.html >> > > No, this

Re: Trouble building world

I'm not sure why nobody else is seeing this, but the files are indeed missing includes of string.h. I have a small patch that adds them, but I'm having unrelated build issues stemming from OpenSSL 1.1.1 On 10/10/18 7:09 AM, Eric McCorkle wrote: > make.conf: > > CPUTYPE?=native > KER

Re: Good motherboard for Ryzen (first-gen)

On 9/21/18 9:53 PM, Eric van Gyzen wrote: I would like to build a Ryzen desktop.  Can anyone recommend a good motherboard? I'm planning on a first-gen, because the second-gen has similar stability problems as the first-gen had, and AMD hasn't released errata for the second-gen yet (as far

Re: Trouble building world

WITHOUT_NCP=1 WITHOUT_NIS=1 WITHOUT_OFED=1 WITHOUT_PPP=1 WITHOUT_RADIUS_SUPPORT=1 WITHOUT_RBOOTD=1 WITHOUT_RCMDS=1 WITHOUT_TALK=1 WITHOUT_TELNET=1 WITHOUT_VI=1 I'm doing the standard "make buildworld" On 10/8/18 1:43 AM, Dimitry Andric wrote: > On 7 Oct 2018, at 23:28, Eric McCorkle wro

Trouble building world

I'm having some trouble building world from current. The problem looks to be various tools' c++ files not including string.h, and therefore missing defs. Is there some critical update step I missed somewhere? signature.asc Description: OpenPGP digital signature

Re: Sound issues with Dell Latitude 7490 (kabylake)

t, I wish I had just committed them. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Good motherboard for Ryzen (first-gen)

would like to be a cool kid with a Threadripper, but I can't justify the cost, so I'm thinking maybe a Ryzen 7 with /only/ 8 cores.  :) Ideally, I want an Intel NIC, ECC memory support, and a 3-year warranty. Thanks in advance, Eric ___ freebsd-current

Re: Bad DHCP Checksums over VLANs

that only DHCP traffic has this problem. If I assign an address manually, all traffic flows normally. Maybe the problem is in the BPF send path. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current

Bad DHCP Checksums over VLANs

/ This happens for /all/ clients. This is a new setup, so I don't know when it got broken, and I can't bisect. The server NIC is common (I211), so maybe it's easy to reproduce. I'll help as much as I can, of course. Eric ___ freebsd-current@freebsd.org mailing

Re: ntpd user and group missing when upgrading from sources from 11-stable to 12-current

? Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: arc_reclaim_thread running hot

On 9/13/18 8:18 AM, Eric van Gyzen wrote: This morning, I found the arc_reclaim_thread running hot on my laptop running 12.0-ALPHA5 r338572. vfs.zfs.arc_max="4294967296"  <-- 4 GiB last pid: 13288;  load averages:  1.32,  1.26,  1.16 Mem: 456M Active, 3837M Inact, 743M Laundry

arc_reclaim_thread running hot

in `jot 1000`; do procstat -kk 100101; done | grep 100101 and put the results here: https://people.freebsd.org/~vangyzen/arc_reclaim_thread_stacks.txt I'm happy to help debug this. Just let me know what you need. Eric ___ freebsd-current@freebsd.org

Re: Request for Review: Generate /etc/services from the IANA registry

much more complex if it supported local additions and overrides, which are unfortunately necessary in our case. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "f

Re: Request for Review: Generate /etc/services from the IANA registry

On 9/10/18 12:04 PM, Eric van Gyzen wrote: Would anyone like to review this change to generate /etc/services from the IANA registry? https://reviews.freebsd.org/D17106 If that review made your browser unhappy, try this one instead: https://reviews.freebsd.org/D17115 Eric

Request for Review: Generate /etc/services from the IANA registry

Would anyone like to review this change to generate /etc/services from the IANA registry? https://reviews.freebsd.org/D17106 Thanks, Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current

Re: Celeron J3160 with enabled Turbo mode stays at 480MHz (lowestsetting) forever and can not lower frequency without Tuebo mode

80/225 120/150 60/75 1601 is not the actual frequency. That is just how it is reported. It is almost certainly running much higher than 1601. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freeb

Re: Make drm drivers use MTRR write-combine

UC RUNTIME MemoryMappedIO fec0 0xfec0 0001 UC RUNTIME MemoryMappedIO fee0 0xfee0 0001 UC WT WB WP RUNTIME MemoryMappedIO ff00 0xff00 1000 UC WT WB WP RUNTIME Eric ___ freebsd-current@freebsd.org

Re: Status of OpenSSL 1.1.1

On 08/03/2018 04:44, Warner Losh wrote: > > > On Thu, Aug 2, 2018 at 5:45 PM, Benjamin Kaduk <mailto:ka...@mit.edu>> wrote: > > On Wed, Aug 01, 2018 at 10:05:28AM -0400, Eric McCorkle wrote: > > On 08/01/2018 09:02, Warner Losh wrote: > > >

Re: Status of OpenSSL 1.1.1

On 08/01/2018 09:02, Warner Losh wrote: > > > On Wed, Aug 1, 2018, 12:31 PM Eric McCorkle <mailto:e...@metricspace.net>> wrote: > > Hi folks, > > I'm wondering what's the status of OpenSSL 1.1.1 integration into base? > More specifically, is there

Status of OpenSSL 1.1.1

Hi folks, I'm wondering what's the status of OpenSSL 1.1.1 integration into base? More specifically, is there a repo or a branch that's started the integration? I'm aware of the wiki page and the list of port build issues, but that seems to be based on replacing the base OpenSSL with a port

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

PM EDT, Ian Lepore wrote: >On Sun, 2018-07-08 at 21:08 +0200, Oliver Pinter wrote: >> Hi! >> >> Have you or Warner any update on this code? >> >> On Thursday, April 12, 2018, Eric McCorkle >> wrote: >> > >Are you aware of https://reviews.fr

mount_smbfs stack overflow issue with long hostnames

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228354 Can someone look at fixing this for 12? Non-gracefully handling long names is a pretty bad bug. - Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo

Re: Ryzen public erratas

s indicate the errata > number for the workarounds. > > Please report the results. If the script helps, I will code the kernel > change to apply the workarounds. Kostik: This thread on the -stable list has a lot of positive feedback: https://lists.freebsd.org/pipermail/

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

> very constrained. > > Warner > > On Wed, Apr 11, 2018 at 6:02 PM, Eric McCorkle <e...@metricspace.net > <mailto:e...@metricspace.net>> wrote: > > I think the thing to do at this point is to wait for the current work on > loader.efi to land, then adapt

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

ng the rebase or the inclusion to base > system? > On 3/28/18, Eric McCorkle <e...@metricspace.net > <mailto:e...@metricspace.net>> wrote: > > I'll do another rebase from head just to be sure > > > > On March 28, 2018 3:23:23 PM EDT, W

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

gt;> Awesome, thanks for the update and the work that you have done! >> >> Now we just need some more reviewers eyes on the code :) >> >> Br, >> >> Tommi >> >> On Thu, 22 Feb 2018 at 2.03, Eric McCorkle <e...@metricspace.net> >wrote: >>

Realtek RTS525A SD card reader

this driver, or would someone recommend a different approach? Thanks in advance for any advice. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-cu

System76 Galago Pro with 8th gen CPU

Has anyone tried -CURRENT on the latest System76 Galago Pro with an 8th gen Kaby Lake R?  All the reports I've heard, including the Laptops page on the wiki, concern systems with a 7th gen Kaby Lake. Eric ___ freebsd-current@freebsd.org mailing list

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

FYI, I just IFC'ed everything, and the current patches are still fine. Also, the full GELI + standalone loader has been deployed on one of my laptops for some time now. On 02/21/2018 18:15, Eric McCorkle wrote: > The GELI work could be merged at this point, though it won't be usable > w

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

loader.efi to function when installed directly to the ESP: https://reviews.freebsd.org/D13497 On 02/20/2018 22:56, Tommi Pernila wrote: > Hi Eric, > > could you provide a brief update how the work is going? > > > Br, > > Tommi > > > On Nov 16, 2017 04:29, &quo

Re: td_swvoltick

On 01/12/2018 13:36, Konstantin Belousov wrote: > On Fri, Jan 12, 2018 at 01:31:41PM -0600, Eric van Gyzen wrote: >> should_yield() compares thread::td_swvoltick to 'ticks' to determine >> whether a thread is hogging and should yield. Since td_swvoltick >> records 'ticks

td_swvoltick

assignment after the call to sched_switch(). That way, db_show_thread will still show useful data for sleeping threads. I would do the same for td_swinvolticks. I'll be happy to make the change myself. I just want a sanity check before I bother. Thanks in advance, Eric

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

Right, so basically, the remaining GELI patches are against loader, and most of them can go in independently of the work on removing boot1. There's a unanimous consensus on getting rid of boot1 which includes its original author, so that's going to happen. For GELI, we have the following (not

Re: GELI with UEFI supporting Boot Environments goes to HEAD when?

I'll reply in more detail later on, when I'm not on a phone On November 15, 2017 9:47:54 AM EST, Warner Losh wrote: >On Wed, Nov 15, 2017 at 3:28 AM, Tommi Pernila > >wrote: > >> Hi All, >> >> Anyone have an idea when the GELI with UEFI supporting Boot

Re: should MINIMAL boot?

"Michael W. Lucas" writes: Hi, > Should a MINIMAL kernel boot and run? Seems this is not the case. You have to load storage related modules (disk controller, cam, geom classes required to taste disks), for example, to boot MINIMAL in a VMWare VM with scsi attached,

Re: r320358 panics immediately on boot / AMD64-GENERIC kernel

e contents of /usr/obj and rebuilding fixed it for him. Apparently, some of the objects didn't get rebuilt, as needed. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: The futur of the roff toolchain

I like all of this. Thanks for your very thorough research and effort. Eric On 05/21/2017 07:57, Baptiste Daroussin wrote: > Hi all, > > I have been working for a while to try to import a modern roff toolchain into > base. > > I didn't like the initial approach that c

Re: more default uid/gid for NFS in mountd

e lookup could be useful in heterogeneous networks. You might consider adding a CLI flag to mountd to let the admin choose the user by UID/GID, and possibly by username/groupname. That would be a reasonable workaround for networks that often hit the lookup problem. Eric _

Re: List test, please ignore.

Never! On Tue, Apr 11, 2017 at 3:18 PM Sean Bruno wrote: > ignore > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: PCI slot and function number for ARI enabled devices

, and this breaks lspci(1). Is it a behavior by design or not? It is by design. See section 6.13 of the PCIe specification. I imagine lspci will need to be fixed. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo

Re: start-up failure at SVN r314889

ke proc filesystem support (requires COMPAT_LINUX >># and PSEUDOFS) >> --- 373,379 >># Enable Linux ABI emulation >>#options COMPAT_LINUX32 >># Enable Linux KPI >> ! options COMPAT_LINUXKPI >> >># Enable the linux-lik

Re: start-up failure at SVN r314889

r314906M/314906:1200024: Wed Mar 8 06:05:49 PST > 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 > > Sorry it's not more help. > > Peace, > david > -- > David H. Wolfskill da...@catwhisker.org > How could

Re: panic: invalid bcd xxx

If someone can test it, I'll gladly commit it. The real-time clock will likely be wrong, but it won't panic with INVARIANTS. Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

Re: panic: invalid bcd xxx

On 02/28/2017 16:57, Conrad Meyer wrote: On Tue, Feb 28, 2017 at 2:31 PM, Eric van Gyzen <vangy...@freebsd.org> wrote: Your system's real-time clock is returning garbage. r312702 added some input validation a few weeks ago. Previously, the kernel was reading beyond the end of an

Re: panic: invalid bcd xxx

n", bcd); + return (0); + } return (bcd2bin_data[bcd]); } Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Does someone keep track of how long it takes to buildworld/kernel?

^ Message ^ It takes forever, but I keep on forgetting to time how long it takes, so I don't know how long "forever" is. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

Re: How many CPU cores does FreeBSD support?

Eric Joyner <e...@freebsd.org> wrote: > Ok; I will try that and will report back. > > - Eric > > On Wed, Jan 4, 2017 at 11:59 AM Konstantin Belousov <kostik...@gmail.com> > wrote: > > On Wed, Jan 04, 2017 at 06:53:23PM +, Eric Joyner wrote: > > Adding f

  1   2   3   4   5   6   >