review: kernel GDB: do not reboot the target

I would like to call attention to this change to prevent accidentally rebooting the target of remote kernel GDB. The code is mundane, but the default could be controversial. https://reviews.freebsd.org/D35473 Please comment on the review, not on this thread. If you need an account on

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

There was a recent discussion about a terminal database update and the new Alternate Screen behavior. I'm curious about the resolution, but I can't find that discussion. Would someone kindly send a clue-by-four via overnight express? Ultimately, I'd like to know how to get the old behavior

top ARC stats are wrong

I would love to have 2 TB of RAM, but alas, I have a paltry 32 GB, and only 200 GB of disk used by ZFS: ARC: 1860M Total, 612G MFU, K MRU, 1921G Anon, 12M Header, 157M Other NAME SIZE ALLOC FREE .. 230G 178G 51.7G .. 298G 12.6G 285G This is on

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

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

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

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 llvm. Eric

spurious(?) userland malloc/mmap failure

While running head r356494, my buildworld just failed due to an apparently spurious userland malloc/mmap failure. ===> usr.bin/finger (all) objcopy: elf_update() failed: I/O error: Cannot allocate memory --- all_subdir_usr.bin/finger --- *** [all_subdir_usr.bin/finger] Error code 2 I ran

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

Re: dtrace not working on bhyve VM without invariant_tsc

> On Dec 9, 2019, at 8:27 PM, Ryan Stone wrote: > > I have a bhyve VM guest on my laptop where dtrace just constantly > aborts whenever I try to use it: > > [rstone@ebpf dtrace]sudo dtrace -s fdcopy.d > Assertion failed: (buf->dtbd_timestamp >= first_timestamp), file >

Re: Networking panic on 12 - found the cause

On 2/12/19 8:53 AM, Pete French wrote: > I found my panic. If I take everything out of rc.conf and loader.conf > and sysctl.conf and boot the system it works fine when I add an IP > address. If I add this one line to sysctl.conf > > net.link.ether.inet.garp_rexmit_count=2 > > Then I get a

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 ___

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

On 10/25/18 6:57 AM, Rodney W. Grimes wrote: I noticed a warning on a new AMD system running 12-BETA1: non-PNP ISA device will be removed from GENERIC in FreeBSD 12. Can you please reply with the specific device. If you have seen one it may be an issue to removing it, especially if this is on

iflib_timer hits hung label; never recovers

My firewall is running head at r338402 (30 Aug). It has three I211 NICs (PCI dev 0x1539). About 24 hours ago, it said: Oct 11 22:29:03 asbestos kernel: igb1: TX(1) desc avail = 42, pidx = 524 Oct 11 22:29:03 asbestos kernel: Link state changed to down Oct 11 22:29:03 asbestos kernel: core:

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: Sound issues with Dell Latitude 7490 (kabylake)

Thanks. So if you try this: sysctl dev.hdaa.0.nid24_config="as=4 seq=15" sysctl dev.hdaa.0.nid21_config="as=1 seq=15" sysctl dev.hdaa.0.reconfig=1 Works, thank you! Dude that's some serious shit ! Jacob, is this documented somewhere ? I haven't read the driver code but what does as/seq

Good motherboard for Ryzen (first-gen)

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 as I know...I would love to be wrong). I

Re: Bad DHCP Checksums over VLANs

On 9/15/18 1:06 AM, Kurt Jaeger wrote: Can you disable all the options of the NIC ? ifconfig igb0 -rxcsum -txcsum -wol -tso4 -vlanmtu -vlanhwtag -vlanhwcsum -vlanhwtso Try to disable everything that can be disabled, e.g. LRO etc. Disabling vlanhwtag works around the problem. Also note that

Bad DHCP Checksums over VLANs

Folks, I'm running head (ALPHA4-ish) on a DHCP server and a client. DHCP works fine on the physical interfaces, but when I run it on a VLAN, I get 5 bad udp checksums in 5 packets from dhclient. Full details here: https://people.freebsd.org/~vangyzen/dhcp_vlan/ This

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

On 9/13/18 4:07 PM, Marek Zarychta wrote: Dear subscribers, stable/12 hasn't been branched yet, so it could be not a bug. Since r336525 make installworld fails on 11-stable when installing world for 12-current without ntpd user/group added. Of course, as a workaround user and group could be

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

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, 2563M Wired, 167M Free ARC: 1131M Total, 304M MFU,

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

On 9/11/18 10:04 AM, Steffen Nurpmeso wrote: Alan Somers wrote in : |Don't worry Steffen.  Python won't be a build requirement for FreeBSD \ |even after Eric's patch.  His Python script will only need to be run \ |whenever IANA |updates its database, and the results will be checked into

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

On 9/5/18 4:35 AM, Lev Serebryakov wrote: BTW, these four settings in rc.conf(5) performance_cx_lowest performance_cpu_freq economy_cx_lowest economy_cpu_freq do NOTHING. They are not used ANYWHERE but rc.conf and rc.conf.5! They are used by /etc/rc.d/power_profile, but not in

Re: Make drm drivers use MTRR write-combine

On 8/14/18 4:12 AM, Johannes Lundberg wrote: Hi Something that we have seen for a long time on FreeBSD is the boot message Failed to add WC MTRR for [0xd000-0xdfff]: -22; performance may suffer Taking a closer look at this with memcontrol I can see that the 256 MB region that DRM

Re: Ryzen public erratas

On 06/13/2018 05:35, Konstantin Belousov wrote: > Today I noted that AMD published the public errata document for Ryzens, > https://developer.amd.com/wp-content/resources/55449_1.12.pdf > > Some of the issues listed there looks quite relevant to the potential > hangs that some people still

Realtek RTS525A SD card reader

Is anyone working on a FreeBSD driver for the Realtek RTS525A SD card reader?  My new Dell XPS 13 has one: none7@pci0:59:0:0: class=0xff card=0x075b1028 chip=0x525a10ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTS525A PCI Express Card Reader' I see that the

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: 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

should_yield() compares thread::td_swvoltick to 'ticks' to determine whether a thread is hogging and should yield. Since td_swvoltick records 'ticks' /before/ the actual context switch, the calculation in should_yield() includes any time that the thread was switched out. It seems that

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

On 06/27/2017 11:09, Michael Jung wrote: > Screen image with backtrace > > https://pasteboard.co/dZRVG5Uo.jpg > > > After upgrading from 318959 to 320358 I immediately get the attached panic. > > This is AMD64 / GENERIC kernel. > > /boot/loader.conf is empty. > > The system boots off a UFS2

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 consisted in simply

Re: more default uid/gid for NFS in mountd

On 05/08/2017 06:45, Rick Macklem wrote: > Hi, > > Five years ago (yea, it slipped through a crack;-), Slawa reported that files > created by root would end up owned by uid 2**32-2 (-2 as uint32_t). > This happens if there is no "-maproot=" in the /etc/exports line. > > The cause is obvious. The

Re: PCI slot and function number for ARI enabled devices

On 03/14/2017 01:37, Mu Lichao wrote: Hi, I am trying to enable Intel 82599 10GbE SR-IOV VFs on FreeBSD 12-CURRENT, and after enabled, the SR-IOV VFs can be seen by pciconf(1), but can not be seen by lspci(1), which is installed from ports/sysutils/pciutils: # pciconf -l | tail -2

Re: panic: invalid bcd xxx

On 03/04/2017 11:44, Oleksandr Tymoshenko wrote: Adrian Chadd (adrian.ch...@gmail.com) wrote: We're not; we need to cope with crappy BIOS emulations and not crash :) What's Linux doing instead? Ignoring the RTC? I believe I saw the same problem on either my NUC or Minnowboard. I just hacked

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

On 02/28/2017 15:47, Michael Gmelin wrote: Booting r313561[0] I get the following panic: mountroot: waiting for device /dev/ufs/FreeBSD_install panic: invalid bcd 177 (also 254, 255 etc.) cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper... vpanic()... kassert_panic()... atrtc_gettime()...

Re: Log spam: Limiting * response from 1 to 200 packets/sec

On 12/13/2016 09:24, Michael Butler wrote: > Any hints as to why all of my -current equipment is complaining like below. Is > there a sysctl to moderate/turn this off? > > Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200 > packets/sec > Dec 13 10:00:21 archive last

Re: Import rcorder-visualize.sh from NetBSD?

On 12/05/2016 15:13, Brooks Davis wrote: > On Mon, Dec 05, 2016 at 01:16:49PM -0600, Eric van Gyzen wrote: >> Would anyone object to me importing this script from NetBSD? >> >> http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/sbin/rcorder/rcorder-visualize.sh?rev=1.5=t

Import rcorder-visualize.sh from NetBSD?

Would anyone object to me importing this script from NetBSD? http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/sbin/rcorder/rcorder-visualize.sh?rev=1.5=text/plain I ask in particular because of the non-BSD license. This seems like a no-brainer, but I'm going to play it safe and ask first.

Re: copyinstr and ENAMETOOLONG

On 11/02/2016 15:33, Jilles Tjoelker wrote: > On Wed, Nov 02, 2016 at 02:24:43PM -0500, Eric van Gyzen wrote: >> Does copyinstr guarantee that it has filled the output buffer when it >> returns ENAMETOOLONG? I usually try to answer my own questions, but I >> don't speak many

Re: Some locale data are broken

On 11/18/2016 02:35, Jean-Sébastien Pédron wrote: > On 17.11.2016 23:33, Eric van Gyzen wrote: >> $ LANG=fr_FR.UTF-8 locale -k thousands_sep >> thousands_sep=" " >> >> lrwxr-xr-x 1 root wheel 25 Nov 2 13:41 >> /usr/share/locale/fr_FR.UTF-8/LC_NUMER

Some locale data are broken

Some locale data seem to be broken on stable/11 and head (r308418 and r308217, respectively). $ LANG=fr_FR.UTF-8 locale -k thousands_sep thousands_sep=" " $ ll /usr/share/locale/fr_FR*/LC_NUMERIC lrwxr-xr-x 1 root wheel 29 Nov 2 13:41 /usr/share/locale/fr_FR.ISO8859-1/LC_NUMERIC ->

copyinstr and ENAMETOOLONG

Does copyinstr guarantee that it has filled the output buffer when it returns ENAMETOOLONG? I usually try to answer my own questions, but I don't speak many dialects of assembly. :) I ask because I'd like to make the following change, and I'd like to know whether I should zero the buffer before

make universe fails with MAKEOBJDIRPREFIX

"make universe" consistently fails in buildworld when I set MAKEOBJDIRPREFIX. I'm running head r306046 on amd64 and building head r306380. There are only comments in /etc/make.conf. My complete command is: make universe JFLAG=-j16 MAKEOBJDIRPREFIX=/work/universe \ >

Re: make universe and /etc/src.conf

On 08/22/2016 17:15, Poul-Henning Kamp wrote: > > In message <ad2f7a3b-21c5-2e2a-2f1b-0625a70e0...@freebsd.org>, Eric van Gyzen > w > rites: >> I just tried a "make universe", and all the kernels failed because they >> couldn't >> find

Re: make universe and /etc/src.conf

On 08/22/2016 11:00, Ngie Cooper wrote: > >> On Aug 22, 2016, at 08:24, Eric van Gyzen <vangy...@freebsd.org> wrote: >> >> I just tried a "make universe", and all the kernels failed because they >> couldn't find the config files. I had for

Re: make universe and /etc/src.conf

On 08/22/2016 10:47, Bryan Drewery wrote: > On 8/22/2016 8:27 AM, Glen Barber wrote: >> On Mon, Aug 22, 2016 at 10:24:25AM -0500, Eric van Gyzen wrote: >>> I just tried a "make universe", and all the kernels failed because they >>> couldn't >>> find

make universe and /etc/src.conf

I just tried a "make universe", and all the kernels failed because they couldn't find the config files. I had forgotten that I have this in /etc/src.conf: KERNCONF=NUMA KERNCONFDIR=/etc Since "make universe" is primarily used for build-testing changes in src, shouldn't it ignore

Re: seldom crashes on Dell E6330 with 12-CURRENT

On 07/23/16 02:21 AM, Matthias Apitz wrote: > > Hello, > > I own since July 15 a new laptop and faced 3 crashes, details see below. > What can I do to gather more information? Thanks > > > notes in general: > - hardware: Dell E6330, amd64, 4 cores i5-3360M, 8 GByte RAM, 250 GByte SSD > w/

Re: Setting sysctl vfs.zfs.arc_max failed: 22

On 07/06/16 03:35 PM, Steven Hartland wrote: > The ARC settings and kmem aren't initialised when tunables are loaded > so the tests fail. > > I've fixed this locally by blindly setting if ARC is not configured. > Request to commit the fix is with re@ > > In the mean time the patch is attached. > >

Setting sysctl vfs.zfs.arc_max failed: 22

Steven and -current: I just updated to r302350 with a GENERIC kernel config. I see this in dmesg: VT(efifb): resolution 1024x768 Setting sysctl vfs.zfs.arc_max failed: 22 CPU: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz (3491.98-MHz K8-class CPU) The relevant parts of

Re: Date formatting with en_US locale

On 06/18/16 04:10 AM, Hajimu UMEMOTO wrote: > Does the attached patch fix your issue? > Though there are many locales it should be fixed, I've included only > en_US one, in this time. Yes, it fixes my issue with en_US. Thank you, Umemoto-san. Eric ___

Re: Date formatting with en_US locale

On 05/26/16 10:15 AM, Baptiste Daroussin wrote: > On Thu, May 26, 2016 at 11:55:08AM -0300, Otacílio wrote: >> Em 26/05/2016 11:49, Baptiste Daroussin escreveu: >>> On Thu, May 26, 2016 at 09:44:25AM -0500, Eric van Gyzen wrote: >>>> Baptiste and -current, >

Re: [CFT] ypldap testing against OpenLDAP and Microsoft Active Directory

On 06/ 9/16 05:49 PM, Matthew Seaman wrote: > On 09/06/2016 18:34, Craig Rodrigues wrote: >> There is still value to ypldap as it is now, and getting feedback from >> users (especially Active Directory) would be very useful. >> If someone could document a configuration which uses IPSEC or OpenSSH

buildworld: /usr/bin/ar segfault

My buildworld just failed very early with a segfault from /usr/bin/ar: -- >>> stage 1.1: legacy release compatibility shims -- ... --- libegacy.a ---

No debug info for statically linked stuff

I'm running head from Tuesday (r301045). I just noticed that "ar" is missing the debuginfo for libarchive: $ /usr/local/bin/gdb /usr/bin/ar GNU gdb (GDB) 7.11 [GDB v7.11 for FreeBSD] [...] Reading symbols from /usr/bin/ar...Reading symbols from

Re: [PATCH] microoptimize locking primitives by avoiding unnecessary atomic ops

On 05/27/16 02:17 PM, Mateusz Guzik wrote: > Hello there, > > quite some time ago I posted a trivial patch to locking primitives. What > they do is the inline part tries an atomic op and if that fails the > actual function is called, which immediately tries the same op. > > The obvious

Date formatting with en_US locale

Baptiste and -current, I noticed two annoyances with date formatting on head, and I wonder how we can fix them. I have these settings: LC_ALL=en_US.ISO8859-1 LANG=en_US.ISO8859-1 First, Thunderbird displays the date as, for example: 03/ 6/16 ... The leading space on the day (6)

Re: Strange text on two computers with AMD processors

On 05/20/16 10:41 PM, Alex V. Petrov wrote: > Strange text on two computers with AMD > CPU: AMD FX-8370 Eight-Core Processor (4018.42-MHz K8-class CPU) > and > CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ (2412.41-MHz > K8-class CPU) > > Copyright (c) 1992-2016 The FreeBSD Project. >

Re: HEADS-UP: installworld on r299292 through r299317 will replace master.passwd, passwd, and group files

On 05/10/2016 01:25, Thomas Zander wrote: > On 10 May 2016 at 08:18, O. Hartmann wrote: > >> I haven't figured out so far how far this goes. Lucky for those having >> recent /etc/ backups. A pity FreeBSD doens't backup this by default. > After having shot myself in

Re: Kernel panic from recent build

t's legal by the spec. > > On Mon, May 2, 2016 at 6:17 PM, Eric van Gyzen <vangy...@freebsd.org > <mailto:vangy...@freebsd.org>> wrote: > > On 05/02/2016 16:14, Bill O'Hanlon wrote: > > On Mon, May 2, 2016 at 3:55 PM, John Baldwin <j...@fr

Re: Kernel panic from recent build

On 05/02/2016 16:14, Bill O'Hanlon wrote: > On Mon, May 2, 2016 at 3:55 PM, John Baldwin wrote: > >> On Monday, May 02, 2016 01:35:54 PM Bill O'Hanlon wrote: >>> ​ >>> IMG_20160502_130335.jpg >>> < >>

Re: limits: setrlimit umtxp: Invalid argument

On 03/09/2016 09:49, Brendan Sechter wrote: > I am running an 11.0-CURRENT VM. > After recently updating, the following appears on startup and dhclient fails > to start. > > Starting dhclient. > limits: setrlimit umtxp: Invalid argument > /etc/rc.d/dhclient: WARNING: failed to start dhclient > >

Re: EFI zfs loader and beadm?

On 03/09/2016 09:40, Andrey Fesenko wrote: > Hello, > I'm test EFI boot ZFSroot with BE, this not support now? > svn 2965489 > > If i build simplest system > http://blog.multiplay.co.uk/2015/12/freebsd-10-2-release-efi-zfs-root-boot/ > > # zfs get -r mountpoint efifpool > NAME PROPERTY

Re: continuous stream of writes?

On 03/01/2016 08:45, Michael Butler wrote: > On 03/01/16 09:41, Eric van Gyzen wrote: >> On 03/01/2016 08:22, Michael Butler wrote: >>> On an otherwise idle machine, I now see a continuous stream of writes to >>> disk. I've only noted this ov

Re: continuous stream of writes?

On 03/01/2016 08:22, Michael Butler wrote: > On an otherwise idle machine, I now see a continuous stream of writes to > disk. I've only noted this over the last couple of weeks but this will > not be welcome behaviour on an SSD .. > > How do I find the source of these writes? > > >

Re: CVE-2015-7547: critical bug in libc

On 02/17/2016 08:19, Warren Block wrote: > On Wed, 17 Feb 2016, Kurt Jaeger wrote: > >> A short note on the www.freebsd.org website would probably be helpful, >> as this case will produce a lot of noise. > > Maybe a short article like we did for leap seconds? >

/etc/periodic/weekly/320.whatis: /usr/libexec/makewhatis.local: not found

I just set up a workstation running head. The weekly 320.whatis script always reports: /usr/libexec/makewhatis.local: not found Indeed, it doesn't exist. Does the 320.whatis script need to be updated for r283777? Cheers, Eric ___

Re: Kernel memory leak with x11/nvidia-driver

On 02/ 4/16 08:05 PM, Mark Johnston wrote: On Thu, Feb 04, 2016 at 05:37:24PM -0600, Eric van Gyzen wrote: On 02/ 3/16 10:54 AM, Eric van Gyzen wrote: I just set up a new desktop running head with x11/nvidia-driver. I've discovered a memory leak where pages disappear from the queues, never

Re: Kernel memory leak with x11/nvidia-driver

On 02/ 3/16 10:54 AM, Eric van Gyzen wrote: I just set up a new desktop running head with x11/nvidia-driver. I've discovered a memory leak where pages disappear from the queues, never to return. Specifically, the total of v_active_count v_inactive_count v_wire_count

Kernel memory leak with x11/nvidia-driver

I just set up a new desktop running head with x11/nvidia-driver. I've discovered a memory leak where pages disappear from the queues, never to return. Specifically, the total of v_active_count v_inactive_count v_wire_count v_cache_count v_free_count drops, eventually becoming

Re: Kernel memory leak with x11/nvidia-driver

On 02/03/2016 10:54, Eric van Gyzen wrote: > I just set up a new desktop running head with x11/nvidia-driver. I've > discovered a memory leak where pages disappear from the queues, never to > return. Specifically, the total of > v_active_count > v_inactive_count >

Hot-Plug PCIe Support

FreeBSD Folks: I am currently scoping the effort to add hot-plug PCIe support to FreeBSD. Is anyone else currently working on this or aware of any design, code, or other effort available outside the tree? FYI, here are perhaps the most interesting references I could find:

Re: [HEADSUP] OpenSSL updated to 1.0.2d

On 10/31/15 5:25 AM, O. Hartmann wrote: Am Fri, 30 Oct 2015 16:57:45 -0400 Jung-uk Kim schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OpenSSL on head has been updated to 1.0.2d. Please make sure to recompile all binaries depending on libcrypto.so.7 or

Re: r288951: ifconfig -alias, arp not removed

On 10/29/2015 16:56, Bryan Drewery wrote: > On 10/29/2015 9:46 AM, Bryan Drewery wrote: >> On 10/29/15 9:42 AM, Eric van Gyzen wrote: >>> On 10/29/2015 11:25, Bryan Drewery wrote: >>>> # ifconfig >>>> igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,M

Re: r288951: ifconfig -alias, arp not removed

On 10/29/2015 11:25, Bryan Drewery wrote: > # ifconfig > igb0: flags=8843 metric 0 mtu 1500 > > options=403bb > ether c8:0a:a9:04:39:78 > inet 10.10.0.7

Re: 11-CURRENT build fail with base gcc

On 08/20/2015 14:21, Warner Losh wrote: On Aug 20, 2015, at 10:32 AM, Dimitry Andric d...@freebsd.org wrote: Ah, this should be replaced with the recently introduced CFLAGS_NO_SIMD variable, then? Perhaps. Didn’t know this was a thing. That could use useful many places, though there

Re: freebsd-head: suddenly NMI panics lead to ddb being unable to stop CPUs?

with the pause instruction.. and for N seconds (N being the CPU ID) or something The patch (at the link below) does use the pause instruction. The CPU has to spin as long as any CPU is in the debugger. On 21 August 2015 at 08:19, Eric van Gyzen vangy...@freebsd.org wrote: I mentioned

Re: freebsd-head: suddenly NMI panics lead to ddb being unable to stop CPUs?

having all of the other cores spinning in this case (mostly thermal; the machines get VERY LOUD when the CPUs are spinning..) -a On 21 August 2015 at 08:19, Eric van Gyzen vangy...@freebsd.org wrote: I mentioned this to Adrian, but I'll mention here for everyone else's benefit. Ryan

Re: freebsd-head: suddenly NMI panics lead to ddb being unable to stop CPUs?

I mentioned this to Adrian, but I'll mention here for everyone else's benefit. Ryan is exactly right. There was a thread a while ago, with a proposed patch from Kostik: https://lists.freebsd.org/pipermail/freebsd-arch/2014-July/015584.html As I recall, Scott Long also ran into this a few

Re: 11-CURRENT build fail with base gcc

On 08/20/2015 11:32, Dimitry Andric wrote: On 20 Aug 2015, at 18:24, Warner Losh i...@bsdimp.com wrote: I think you are wrong about the cause. -mno-avx is bogusly listed unconditionally in efi/Makefile.inc. I’m working on a patch now… Ah, this should be replaced with the recently

Re: Segmentation fault running ntpd

WITH_DEBUG_FILES=1 (IIRC) On 7/28/15 6:35 PM, Adrian Chadd wrote: There's some way in stable/10 and -head to get it to install debug symbols for things. Maybe it's only libraries, but you'll at least want that in there so you can get stack traces through libc. -adrian

Re: panic: witness_warn head/amd64 @r285741 on 1 of 2 machines

On 07/21/2015 15:05, David Wolfskill wrote: On Tue, Jul 21, 2015 at 10:28:32PM +0300, Konstantin Belousov wrote: ... Indeed, thank you. ithread_loop() at ithread_loop+0xa6/frame 0xfe083b9c0a70 fork_exit() at fork_exit+0x84/frame 0xfe083b9c0ab0 fork_trampoline() at

Re: panic: witness_warn head/amd64 @r285741 on 1 of 2 machines

On 07/21/2015 15:21, Eric van Gyzen wrote: On 07/21/2015 15:05, David Wolfskill wrote: On Tue, Jul 21, 2015 at 10:28:32PM +0300, Konstantin Belousov wrote: ... Indeed, thank you. ithread_loop() at ithread_loop+0xa6/frame 0xfe083b9c0a70 fork_exit() at fork_exit+0x84/frame

Re: pedantic compiler warnings: double semicolons, function to data pointers

On 05/19/2015 14:42, Luigi Rizzo wrote: While trying to compile some of my (kernel) code in different environments, i noticed a couple of errors that perhaps might be worth fixing - extra semicolons. These come either from explicit repetitions in the code (see the output of a grep at the

Re: SSE in libthr

Below is an updated patch to incorporate everyone's feedback so far. I recognize all of the counter-arguments, and I agree with them in general. Indeed, as applications use more SIMD, this kind of patch goes in the wrong direction. However, there are applications that do not use enough SSE to

Re: [RFC] Add GELI Passphrase: prompt to boot loader

On 04/06/2015 13:39, Devin Teske wrote: On Apr 6, 2015, at 10:24 AM, Eric van Gyzen e...@vangyzen.net wrote: On 04/06/2015 12:58, Devin Teske wrote: Hi -current, I have a pending enhancement to the boot loader that Colin P. and I have been working on together. URL: https

Re: [RFC] Add GELI Passphrase: prompt to boot loader

On 04/06/2015 12:58, Devin Teske wrote: Hi -current, I have a pending enhancement to the boot loader that Colin P. and I have been working on together. URL: https://reviews.freebsd.org/D2105 https://reviews.freebsd.org/D2105 The nature of the patch is to cause the boot loader to prompt for

Re: Early use of log() does not end up in kernel msg buffer

On 03/26/2015 23:20, Eric Badger wrote: Using log(9) when no process is reading the log results in the message going only to the console (contrast with printf(9), which goes to the console and to the kernel message buffer in this case). I believe it is truer to the semantics of logging for

  1   2   >