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

Re: Not sure if this is the correct place.... (laptop, dual-boot EFI)

> > I'd like to repartition it to be able to dual boot it much as I do with > my X220 (I wish I could ditch Windows entirely, but that is just not > going to happen), but I'm not sure how to accomplish that in the EFI > world -- or if it reasonably CAN be done in the EFI world. Fortunately > the

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 11/26/18 10:25 AM, Pete French wrote: > Foolwing up an old thread I know, but my ssystem ahs been pretty stable > until recently, when it started locking up about one a week at least. > This co-incided with me doing two things to it: > > 1) Doubling the amount of RAM in it to 16 gig, using RAM

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

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

On 8/21/18 1:30 PM, Mike Tancsa wrote: There are 3 of these disks I found. Unfortunately, they all seem a little different from the revision stamps on the board. They are all from PCEngines who generally seem to source quality products. This is in an APU3 I have an APU2.  My disk is exactly

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 06/18/2018 09:34, Pete French wrote: > Preseumably in the slightly longer term these workarounds go into the > actual kernel if it detects Ryzen ? Yes, Kostik said he would code this into the kernel after he gets enough feedback. Eric ___

Re: KBI unexpexted change in stable/11 ?

On 03/28/2018 10:35, Slawa Olhovchenkov wrote: > On Wed, Mar 28, 2018 at 10:29:10AM -0500, Eric van Gyzen wrote: > >> On 03/28/2018 08:09, Slawa Olhovchenkov wrote: >>> I am upgrade system to latest -STABLE and now see kernel crash: >>> >>> - loading virt

Re: KBI unexpexted change in stable/11 ?

On 03/28/2018 08:09, Slawa Olhovchenkov wrote: > I am upgrade system to latest -STABLE and now see kernel crash: > > - loading virtualbox modules build on 11.1-RELEASE-p6 > - loading nvidia module build on 11.1-RELEASE-p6 and start xdm > > Is this expected? I am mean about loading modules

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 02/12/2018 21:54, Peter Moody wrote: >> I'm having really good luck with the kernel patch attached to this >> message: >> https://docs.freebsd.org/cgi/getmsg.cgi?fetch=417183+0+archive/2018/freebsd-hackers/20180211.freebsd-hackers > > I'm new to this; what are the chances that this gets into

Re: i386 with 4GB RAM: less than 2GB available on A2SAV (Intel Atom E3940)

On 01/28/2018 10:05, Dimitry Andric wrote: > On 28 Jan 2018, at 15:57, Andre Albsmeier wrote: >> I have a lot of machines running with 4 GB physical RAM and, for >> some reasons, I still have to use a 32 bits OS. >> >> All of them show something between 3 and 3.5 GB

Re: Compile-time check for clock_nanosleep()

On 07/03/2017 15:28, Chris Ross wrote: > >> On Jul 3, 2017, at 14:46, Kurt Jaeger wrote: >> >> Use __FreeBSD_version from sys/param.h: >> >> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/versions.html > > Thanks. That looks great. Also, for my specific

Re: if_iwm crashes kernel when loaded from /boot/loader.conf

On 04/07/2017 09:38, Tommi Pernila wrote: > On Fri, 7 Apr 2017 at 16.27, Tomasz CEDRO wrote: > >> Hello, >> >> I noticed a problem when loading if_iwm from /boot/loader.conf kernel >> crashes as it cannot load module firmware dead loop occurs. Adding >> iwm8000Cfw before if_iwm

Re: Kernel panic on production system - what now?

On 03/24/2017 03:28, Patrick M. Hausen wrote: > Hi all, > > Mar 24 02:39:36 ph001 kernel: kernel trap 12 with interrupts disabled > Mar 24 02:39:36 ph001 kernel: > Mar 24 02:39:36 ph001 kernel: > Mar 24 02:39:36 ph001 kernel: Fatal trap 12: page fault while in kernel mode > Mar 24 02:39:37

Re: net.inet.udp.log_in_vain strange syslog reports

On 02/15/2017 08:56, Mark Martinec wrote: In a similar vein, I noticed also the following in our logs, with net.inet.tcp.log_in_vain=1. Looks like messages got concatenated somehow: Jan 25 01:37:53 mildred kernel: TCP: [2607:ff10:c5:509a::10]:26459 to [2001:1470:ff80::80:16]:4911 tcpflags 0x2;

Re: HWPMC on SkyLake

On 02/09/2017 14:53, Derrick McKee wrote: > I would like to use hwpmc on my desktop with a SkyLake processor. However, > I get an 'hwpc_core: unknown PMC architecture: 4' error whenever I run > kldload hwpmc command. There was a small thread about this error on the > current mailing list last

Re: GELI with integrity verification on swap

On 02/09/2017 08:51, Mark Martinec wrote: 2) During boot the log shows a short flurry of messages like: kernel: GEOM_ELI: Device gpt/sw1.eli created. kernel: GEOM_ELI: Encryption: AES-XTS 128 kernel: GEOM_ELI: Integrity: HMAC/SHA256 kernel: GEOM_ELI: Crypto: software kernel: GEOM_ELI:

Re: net.inet.udp.log_in_vain strange syslog reports

On 02/06/2017 10:19, Mark Martinec wrote: > > One minor nit: > instead of a hack: > > char src[4*sizeof "123"]; > char dst[4*sizeof "123"]; > > it would be cleaner and in sync with the equivalent code in > sys/netinet6/udp6_usrreq.c > to use the INET_ADDRSTRLEN constant (from

Re: net.inet.udp.log_in_vain strange syslog reports

On 02/02/2017 12:55, Mark Martinec wrote: 11.0-RELEASE-p7, net.inet.udp.log_in_vain=1 The following syslog entries seem to indicate some buffer overruns in the reporting code (not all log lines are broken, just some). (the actual failed connection attempts were indeed there, it's just that the

Re: Upgrading boot from GPT(BIOS) to GPT(UEFI)

On 12/16/2016 11:39, Slawa Olhovchenkov wrote: > On Fri, Dec 16, 2016 at 06:08:34PM +0100, Fernando Herrero Carrón wrote: > >> Hi everyone, >> >> A few months ago I got myself a new box and I have been happily running >> FreeBSD on it ever since. I noticed that the boot was not as fast as I had

Re: Upgrading boot from GPT(BIOS) to GPT(UEFI)

On 12/16/2016 11:08, Fernando Herrero Carrón wrote: > Hi everyone, > > A few months ago I got myself a new box and I have been happily running > FreeBSD on it ever since. I noticed that the boot was not as fast as I had > expected and I've realized that, while my disk is GPT partitioned, the boot

Re: Freebsd 11.0 RELEASE - ZFS deadlock

On 11/09/2016 07:48, Henri Hennebert wrote: > I encounter a strange deadlock on > > FreeBSD avoriaz.restart.bel 11.0-RELEASE-p3 FreeBSD 11.0-RELEASE-p3 #0 > r308260: > Fri Nov 4 02:51:33 CET 2016 > r...@avoriaz.restart.bel:/usr/obj/usr/src/sys/AVORIAZ amd64 > > This system is exclusively

Re: Can't build 11-stable without BPF

On 09/30/2016 16:19, Dave Mischler wrote: > When I remove the "device bpf" from the kernel configuration the > resulting "make buildkernel KERNCONF=XXX" fails to compile in module > lmc, source file if_lmc.c > > The problem seems to be that DEV_BPF is not defined, but this is not > tested for.

Re: Status of PCIe Hotplug?

On 09/27/2016 08:57, Borja Marcos wrote: > >> On 27 Sep 2016, at 15:48, Jan Henrik Sylvester wrote: >> >> On 09/27/2016 12:16, Borja Marcos wrote: >>> I have noticed that the GENERIC kernel in 11-STABLE includes the >>> PCI_HP option, and the hotplug bits seem to be present in the

Re: Problem with nsswitch.conf

On 09/21/2016 12:21, Shawn Bakhtiar wrote: > Good morning All, > > I'm trying to configure my server as an LDAP client. I installed the nslcd > service and it's working great. > > My problem is when I issue the command getent passwd it only returns the LDAP > user not the local users. > > # > #

Re: [Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot

On 08/10/16 10:19 AM, Kubilay Kocak wrote: >> Furthermore, it's a new regression that will go into 11.0-RELEASE, so >> getting some attention is a good thing. I imagine this is why koobs@ >> CC'd stable@. > > It was the original reporter CC'd, I added mfc-stable{10,11} flags in > case the issue

Re: [Bug 211491] System hangs after "Uptime" on reboot with iSCSI, zfs, and altroot

On 08/09/16 06:10 PM, bugzilla-nore...@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 > > --- Comment #13 from Ngie Cooper --- > Please don't add -current or -stable to bugs like this; it spams the list > unnecessarily (this issue impacts users of

Re: procstat -kk: Cannot allocate memory

On 03/08/2016 14:17, Garrett Wollman wrote: > Sometimes when running "procstat -kk", I get the following error: > > procstat: sysctl: kern.proc.pid: 1044: Cannot allocate memory > > What is the condition that causes this? Is there a static limit in > procstat, or in the kernel, that needs to be

Re: Dell NVMe issues

On 10/06/2015 11:10, Sean Kelly wrote: > >> On Oct 6, 2015, at 11:06 AM, Eric van Gyzen <e...@vangyzen.net >> <mailto:e...@vangyzen.net>> wrote: >> >> Try this: >> >>sysctl vfs.zfs.vdev.trim_on_init=0 >>zpool create tank mirror

Re: Dell NVMe issues

On 10/06/2015 10:18, Sean Kelly wrote: > Back in May, I posted about issues I was having with a Dell PE R630 with > 4x800GB NVMe SSDs. I would get kernel panics due to the inability to assign > all the interrupts because of > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199321 >

Re: Routing stops working when we create a new vlan

On 08/06/2015 22:09, Marcelo Gondim wrote: PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202144 The output of ifconfig and netstat -nr -f inet, before and after you create the new vlan, would be most helpful. Eric Hi Eric, I put the information you requested in PR. Wow, the

Re: Routing stops working when we create a new vlan

On 8/6/15 5:57 PM, Marcelo Gondim wrote: Hi all, Let me illustrate a network topology, to tell where the problem occurs: PC station: 192.168.8.253/24 (FreeBSD 10.2-PRERELEASE) Router: 192.168.8.177/24 and 10.254.215.1/24 (FreeBSD 10.2-RC2) router(CPE): 10.254.215.188/24 (a customer) From

Re: makefs Sparse Files: NetBSD CLI Compatibility

On 08/14/2013 10:13, Eric van Gyzen wrote: On 08/14/2013 09:53, Glen Barber wrote: On Wed, Aug 14, 2013 at 09:33:01AM -0500, Eric van Gyzen wrote: On 08/14/2013 09:06, Glen Barber wrote: On Wed, Aug 14, 2013 at 08:10:41AM -0500, Eric van Gyzen wrote: NetBSD's makefs has a -Z flag to create

makefs Sparse Files: NetBSD CLI Compatibility

NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the flag is spelled -p. Is there a reason for using a different flag? It would be very nice to preserve CLI compatibility with NetBSD. NetBSD committed first (by one month), and neither change has gone into a

Re: makefs Sparse Files: NetBSD CLI Compatibility

On 08/14/2013 09:06, Glen Barber wrote: On Wed, Aug 14, 2013 at 08:10:41AM -0500, Eric van Gyzen wrote: NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the flag is spelled -p. Is there a reason for using a different flag? It would be very nice to preserve CLI

Re: makefs Sparse Files: NetBSD CLI Compatibility

On 08/14/2013 09:53, Glen Barber wrote: On Wed, Aug 14, 2013 at 09:33:01AM -0500, Eric van Gyzen wrote: On 08/14/2013 09:06, Glen Barber wrote: On Wed, Aug 14, 2013 at 08:10:41AM -0500, Eric van Gyzen wrote: NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD

Re: makefs Sparse Files: NetBSD CLI Compatibility

On 08/14/2013 14:05, Simon J. Gerraty wrote: On Wed, 14 Aug 2013 08:10:41 -0500, Eric van Gyzen writes: NetBSD's makefs has a -Z flag to create the image as a sparse file. In FreeBSD, the flag is spelled -p. Is there a reason for using a different flag? No, the -p should have been dropped

Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1

On 08/06/2013 14:23, J David wrote: On Tue, Aug 6, 2013 at 1:59 PM, Eric van Gyzen e...@vangyzen.net wrote: on an otherwise idle amd64 system with 4 CPUs. The first command in the build.log file: rm -rf /usr/obj/home/freebsd/tmp took over three minutes. It should have taken about

Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1

On 08/08/2013 09:19, Eric van Gyzen wrote: On 08/06/2013 14:23, J David wrote: On Tue, Aug 6, 2013 at 1:59 PM, Eric van Gyzen e...@vangyzen.net wrote: on an otherwise idle amd64 system with 4 CPUs. The first command in the build.log file: rm -rf /usr/obj/home/freebsd/tmp took over

Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1

On 08/07/2013 04:09, Andriy Gapon wrote: on 06/08/2013 00:15 Dave Mischler said the following: I have an i5-2500 machine 8GB RAM now running 9.2-RC1 amd64 with the GENERIC kernel. Today, while still running 9.2-BETA2, I updated my source tree and started building world with idprio 31 and I

Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1

On 08/05/2013 16:15, Dave Mischler wrote: I have an i5-2500 machine 8GB RAM now running 9.2-RC1 amd64 with the GENERIC kernel. Today, while still running 9.2-BETA2, I updated my source tree and started building world with idprio 31 and I looked back a while later and all the CPU cores and disk

Re: unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1

On 08/06/2013 10:31, Eric van Gyzen wrote: On 08/05/2013 16:15, Dave Mischler wrote: I have an i5-2500 machine 8GB RAM now running 9.2-RC1 amd64 with the GENERIC kernel. Today, while still running 9.2-BETA2, I updated my source tree and started building world with idprio 31 and I looked back

[patch] IPMI KCS can drop the lock while servicing a request

At work, we discovered that our application's IPMI thread would often use a lot of CPU time. The KCS thread uses DELAY to wait for the BMC, so it can run without sleeping for a long time with a slow BMC. It also holds the ipmi_softc.ipmi_lock during this time. When using adaptive mutexes,

Re: mfi(4) IO performance regression, post 8.1

On 07/17/12 15:39, Steve McCoy wrote: On 7/13/12 9:39 AM, John Baldwin wrote: On Thursday, July 12, 2012 11:47:28 pm Steve McCoy wrote: On 7/12/12 4:34 PM, Steve McCoy wrote: John Baldwin wrote: Barring that, can you do a binary search of kernels from stable/8 between 8.1 and 8.2 on an 8.1

Re: ath(4) irq and taskq cpu usage

Sam Leffler wrote: Eric van Gyzen wrote: The irq and taskq for my ath(4) card often use excessive amounts of CPU time, even when my network is idle. They are often above 10% and 15%, respectively; occasionally, they are as high as 27% and 44%. The system is an AMD Athlon64 2800+ running

ath(4) irq and taskq cpu usage

The irq and taskq for my ath(4) card often use excessive amounts of CPU time, even when my network is idle. They are often above 10% and 15%, respectively; occasionally, they are as high as 27% and 44%. The system is an AMD Athlon64 2800+ running FreeBSD 6.2-RELEASE i386 with a custom kernel

panic: sleeping thread

I saw a recent thread about a sleeping thread panic. I submitted kern/102654 for one on 6.1-RELEASE-p1: http://www.freebsd.org/cgi/query-pr.cgi?pr=102654 I'll gladly help you debug it. Eric ___ freebsd-stable@freebsd.org mailing list

panic sbdrop on 6.0-RELEASE-p4 i386

I recently had two sbdrop panics on 6.0-RELEASE-p4 i386. Following are the stack traces and the kernel configuration. Of course, I still have the crash dumps, and I'll gladly help anyone who wants more informaion. --Eric