Re: panic: mutex ncnegl not owned at /usr/src/sys/kern/vfs_cache.c:743 in 12.0-CURRENT r308447

Sat, Nov 12, 2016 at 05:11:57PM -0800, Don Lewis wrote: >> This !neg_locked code in cache_negative_remove() looks suspicious to me: >> >> if (!neg_locked) { >> if (ncp->nc_flag & NCF_HOTNEGATIVE) { >> hot_locked = t

Re: panic: mutex ncnegl not owned at /usr/src/sys/kern/vfs_cache.c:743 in 12.0-CURRENT r308447

On 13 Nov, Mateusz Guzik wrote: > On Sat, Nov 12, 2016 at 05:11:57PM -0800, Don Lewis wrote: >> What protects nc_flag, the lock for the list that it resides on? >> > > It is supposed to be the hot list lock and I think this uncovers a bug > here. > > Consider a

malloc() call somehow calling the rtld malloc() implementaion

I've been attempting to get OpenOffice to build properly in a clang400-import poudriere jail and have run into a mystery. The build procedure creates a c++ executable "idlc", which is used to build other stuff. The new operator has been overrriden to call a custom memory allocator, which I have c

Re: malloc() call somehow calling the rtld malloc() implementaion

On 27 Jan, Alexander Kabaev wrote: > On Fri, 27 Jan 2017 00:31:30 -0800 (PST) > Don Lewis wrote: >> If I create a simple test program that calls malloc() and set a >> breakpoint in malloc(), the breakpoint gets set in the rtld version, >> but the the libc version of ma

Re: malloc() call somehow calling the rtld malloc() implementaion

On 27 Jan, Konstantin Belousov wrote: > On Fri, Jan 27, 2017 at 12:19:16PM -0500, Alexander Kabaev wrote: >> On Fri, 27 Jan 2017 00:31:30 -0800 (PST) >> Don Lewis wrote: >> >> > I've been attempting to get OpenOffice to build properly in a >> > clang4

Re: malloc() call somehow calling the rtld malloc() implementaion

On 28 Jan, Jan Mikkelsen wrote: > Hi, > > Are you being affected by this rtld behaviour: > > https://lists.freebsd.org/pipermail/freebsd-hackers/2016-July/049769.html > > > https://lists.freebsd.org/pipermail/freebsd-st

Re: malloc() call somehow calling the rtld malloc() implementaion

On 27 Jan, Konstantin Belousov wrote: > On Fri, Jan 27, 2017 at 12:19:16PM -0500, Alexander Kabaev wrote: >> On Fri, 27 Jan 2017 00:31:30 -0800 (PST) >> Don Lewis wrote: >> > If I create a simple test program that calls malloc() and set a >> > breakpoint in mal

Re: malloc() call somehow calling the rtld malloc() implementaion

On 27 Jan, Alexander Kabaev wrote: > On Fri, 27 Jan 2017 10:47:20 -0800 (PST) > Don Lewis wrote: > >> On 27 Jan, Alexander Kabaev wrote: >> > On Fri, 27 Jan 2017 00:31:30 -0800 (PST) >> > Don Lewis wrote: >> >> >> If I create

Re: I/O semantics of pipe and FIFO.

On 8 Mar, Devin Teske wrote: > Problem we had found was: > > Executing dd with a closed stdout and stderr would cause the summary > messages printed at the end to go into the destination output file. > > For example, > > dd if=/dev/zero of=/tmp/foo bs=1m count=1 > > Works fine, but the followi

Re: ntpd dies nightly on a server with jails

On 16 Mar, O. Hartmann wrote: > Am Wed, 15 Mar 2017 13:12:37 -0700 > Cy Schubert schrieb: >> > >> > When the clock is floating that wild, in all cases ntpd isn't >> > running any mor e. >> > I try to restart with options -g and -G to adjust the time quickly >> > at the beginning, which works fin

Re: ntpd dies nightly on a server with jails

On 17 Mar, O. Hartmann wrote: > Just some strange news: > > I left the server the whole day with ntpd disabled and I didn't watch > a gain of the RTC by one second, even stressing the machine. > > But soon after restarting ntpd, I realised immediately a 30 minutes > off! This morning, the discra

Re: ELF binary type "3" not known.

On 20 Mar, Chris H wrote: > I'm not sure which of the two lists I'm directing > this to is the best/correct one. So I picked both. > > To the point; I received this message during a big > build session. I was only able to catch the one from > x11/nvidia-driver in such a way as to actually get > th

ino64 package fallout

I just upgraded by package build box and its poudriere jail to r318776 and ran into some significant package build fallout. devel/llvm40:build: /usr/bin/c++ -DHAVE_RPC_XDR_H=0 -DHAVE_TIRPC_RPC_XDR_H=0 -O2 -pipe -fstack-protector -isystem /usr/local/include -fno-strict-aliasing -isystem /usr

Re: ino64 package fallout

On 24 May, Konstantin Belousov wrote: > On Wed, May 24, 2017 at 10:05:22AM -0700, Don Lewis wrote: >> I just upgraded by package build box and its poudriere jail to r318776 >> and ran into some significant package build fallout. > > There are several reviews that fix ports

r320183 (rpc.lockd cleanup) breaks virtualbox-ose build

This is a really strange problem ... Last week I upgraded my 12.0-CURRENT package build box from r318774 to r320570. I also upgraded the poudriere jail to match. When I went to build packages, the virtualbox-ose build failed due to ar segfaulting. To debug I created a new 12.0-CURRENT poudriere

jemalloc_arena.c:821: Failed assertion: "nstime_compare(&decay->epoc h, &time) <= 0")

I'm trying to stabilize my new-ish Ryzen package build box. I've run into this error a couple of times: (: jemalloc_arena.c:821: Failed assertion: "nstime_compare(&decay->epoc h, &time) <= 0") most recently today when building llvm40. It seems to happen somewhat randomly. I don't remember seei

Re: jemalloc_arena.c:821: Failed assertion: "nstime_compare(&decay->epoc h, &time) <= 0")

On 12 Jul, Jason Evans wrote: > On Tue, 11 Jul 2017 18:12:58 -0700 (PDT) > Don Lewis wrote: >> I'm trying to stabilize my new-ish Ryzen package build box. I've run >> into this error a couple of times: >> (: jemalloc_arena.c:821: Failed assertion: >> &qu

Re: r320183 (rpc.lockd cleanup) breaks virtualbox-ose build

On 21 Jul, Ed Maste wrote: > On 11 July 2017 at 12:44, Don Lewis wrote: >> This is a really strange problem ... >> >> Last week I upgraded my 12.0-CURRENT package build box from r318774 to >> r320570. I also upgraded the poudriere jail to match. When I went to >&g

Re: dogfooding over in clusteradm land

On 14 Dec, Poul-Henning Kamp wrote: > In message <1323868832.5283.9.ca...@hitfishpass-lx.corp.yahoo.com>, Sean > Bruno > writes: > >>We're seeing what looks like a syncher/ufs resource starvation on 9.0 on >>the cvs2svn ports conversion box. I'm not sure what resource is tapped >>out. > > Sear

Re: dogfooding over in clusteradm land

On 2 Jan, Florian Smeets wrote: > On 29.12.11 01:04, Kirk McKusick wrote: >> Rather than changing BKVASIZE, I would try running the cvs2svn >> conversion on a 16K/2K filesystem and see if that sorts out the >> problem. If it does, it tells us that doubling the main block >> size and reducing the n

Re: dogfooding over in clusteradm land

On 2 Jan, Don Lewis wrote: > On 2 Jan, Florian Smeets wrote: >> This does not make a difference. I tried on 32K/4K with/without journal >> and on 16K/2K all exhibit the same problem. At some point during the >> cvs2svn conversion the sycer starts to use 100% CPU. The whol

Re: dogfooding over in clusteradm land

On 2 Jan, Don Lewis wrote: > On 2 Jan, Don Lewis wrote: >> On 2 Jan, Florian Smeets wrote: > >>> This does not make a difference. I tried on 32K/4K with/without journal >>> and on 16K/2K all exhibit the same problem. At some point during the >>> cvs2svn

Re: dogfooding over in clusteradm land

On 3 Jan, Kostik Belousov wrote: > This sounds very plausible. I think that there is no sense in restarting > the scan if it is requested in async mode at all. See below. > > Would be thrilled if this finally solves the svn2cvs issues. > > commit 41aaafe5e3be5387949f303b8766da64ee4a521f > Autho

Re: dogfooding over in clusteradm land

On 3 Jan, Kostik Belousov wrote: > On Tue, Jan 03, 2012 at 01:45:26AM -0800, Don Lewis wrote: >> On 3 Jan, Kostik Belousov wrote: >> >> > This sounds very plausible. I think that there is no sense in restarting >> > the scan if it is requested in async mode at

Re: dogfooding over in clusteradm land

On 3 Jan, Kostik Belousov wrote: >> With your change above, the code will skip the busy page after sleeping >> if it is running in async mode. It won't make another attempt to write >> this page because it no longer attempts to rescan. > Why would it skip it ? Please note the call to vm_page_fin

couldn't log on to my -CURRENT machine after upgrade to latest PAM

I just upgraded my -CURRENT machine for the first time since mid-November. When I rebooted, I was surprised that I was unable to log in via either ssh or directly on the console. The diagnostics printed to the console indicated that pam_skey.so was missing. Since that was nuked a long time ago,

Re: CD9660/md(4)/UFS22 silly behaviour

On 8 Jan, Poul-Henning Kamp wrote: > > I'm doing som data-mining on a pile of ISO images right now. > > I stuck the ISOs on a UFS2 on a flash-disk for speed, and mdconfig(8)'d > them so I could mount them. > > The traffic pattern his "interesting": > > dT: 1.003s w: 1.000s > L(q) ops/sr

Re: couldn't log on to my -CURRENT machine after upgrade to latest PAM

On 9 Jan, Dag-Erling Smørgrav wrote: > Don Lewis writes: >> The documentation says that /etc/pam.conf is only used if >> /etc/pam.d/service-name isn't found, and the code appears to agree >> with that, however this doesn't seem to be working as expected af

Re: couldn't log on to my -CURRENT machine after upgrade to latest PAM

On 9 Jan, Dag-Erling Smørgrav wrote: > Don Lewis writes: >> Dag-Erling Smørgrav writes: >> > The culprit was this commit: >> > >> > http://trac.des.no/openpam/changeset/487/trunk/lib/openpam_configure.c >> > >> > However, I'm not co

Re: couldn't log on to my -CURRENT machine after upgrade to latest PAM

On 9 Jan, Dag-Erling Smørgrav wrote: > Don Lewis writes: >> After staring at the code a lot more, I see your point about the loss of >> information. The problem is that openpam_parse_chain() returns >> PAM_SUCCESS whether or not if found anything, but we want the loop

Re: couldn't log on to my -CURRENT machine after upgrade to latest PAM

On 10 Jan, Dag-Erling Smørgrav wrote: > If at any point in this conversation I seemed to make _no sense at all_, > it was because I conflated it with a completely different OpenPAM issue > (error reporting in openpam_dynamic.c) which has been on my mind lately. > Sorry about that. I will attempt t

Re: couldn't log on to my -CURRENT machine after upgrade to latest PAM

On 11 Jan, Dag-Erling Smørgrav wrote: > Could you please try this: > > # cd /usr/src/contrib > # mv openpam openpam.orig > # svn export svn://svn.des.no/openpam/trunk@526 openpam > # cd ../lib/libpam > # make depend && make all && make install [snip] building shared library libpam.so.5 make: don'

Re: Panic in ffs_valloc (Was: Unexpected SU+J inconsistency AGAIN -- please, don't shift topic to ZFS!)

On 28 Feb, Lev Serebryakov wrote: > Hello, Lev. > You wrote 28 февраля 2013 г., 14:13:23: > > LS>>> My server runs 9.1-STABLE and have 8Tb UFS2 SU+J FS. > LS>>> It crashed a several minutes ago (I don't know reason yet) and fsck > LS>>> says "Unexpected SU+J inconsistency" (Inode mode/directory

Re: panic td->td_lock == NULL in scheduler(), csup'd 2011-02-19

On 13 Jun, Attilio Rao wrote: > 2012/6/13, Svatopluk Kraus : >> Hi, >> >> it looks similar to >> http://lists.freebsd.org/pipermail/freebsd-current/2011-March/023829.html > > Yes, that is likely the problem. > However, I would really love to workaround the pid allocation race in > another way tha

uniq busted?

I justed updated my 10.0-CURRENT box and ran into major problems with port building. I tracked the problem down to uniq not working. # wc -l /etc/termcap 4666 /etc/termcap # cat /etc/termcap | uniq uniq: unable to limit ioctls for stdout: Capabilities insufficient It complains about capabili

Re: uniq busted?

On 11 Sep, To: freebsd-current@freebsd.org wrote: > I justed updated my 10.0-CURRENT box and ran into major problems with > port building. I tracked the problem down to uniq not working. > > # wc -l /etc/termcap > 4666 /etc/termcap > # cat /etc/termcap | uniq > uniq: unable to limit ioctls fo

CAM panic with tethered Virgin Mobile Mifi 2200

I've had a Virgin Mobile MiFi 2200 CDMA modem for a few years that I've successfully been using in tethered mode on my 8-STABLE laptop. The only issue is that I have to do a camcontrol eject to get it to switch from being a umass device to being a modem. Today I decided to try to add this device

Re: CAM panic with tethered Virgin Mobile Mifi 2200

On 13 Nov, To: freebsd-current@freebsd.org wrote: > I've had a Virgin Mobile MiFi 2200 CDMA modem for a few years that I've > successfully been using in tethered mode on my 8-STABLE laptop. The > only issue is that I have to do a camcontrol eject to get it to switch > from being a umass device to

Re: Anyone else seeing uma_zalloc_arg panics?

On 23 Nov, Mark Robert Vaughan Murray wrote: > Hi * > > Anyone else seeing panics like this? > > This is CURRENT, amd64, 2 CPUs, source synced on Thursday 21st Nov evening > GMT sometime. > > +panic: uma_zalloc_arg: Returning an empty bucket. > +cpuid = 1 > +KDB: stack backtrace: > +db_trace_se

panic: uma_zalloc_arg: Returning an empty bucket.

I just got this panic on my 11.0-CURRENT machine while building ports: panic: uma_zalloc_arg: Returning an empty bucket. cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper(c113330c,2,1000,ee3fd850,ee3fd848,...) at db_trace_self_wrapper+0x2d/frame 0xee3fd810 kdb_backtrace(c12f131f,0,c116b40

panic: double fault with 11.0-CURRENT r258504

I upgraded my 11.0-CURRENT machine to r258504 to get past the uma panic that I stumbled across earlier. Now I got this when I started upgrading ports: Unread portion of the kernel message buffer: Fatal double fault: eip = 0xc0b158e0 esp = 0xe4f62000 ebp = 0xe4f62010 cpuid = 0; apic id = 00 panic

Re: panic: double fault with 11.0-CURRENT r258504

On 25 Nov, Konstantin Belousov wrote: > On Sat, Nov 23, 2013 at 11:43:30PM -0800, Don Lewis wrote: >> I upgraded my 11.0-CURRENT machine to r258504 to get past the uma panic >> that I stumbled across earlier. Now I got this when I started upgrading >> ports: >> >

Re: panic: double fault with 11.0-CURRENT r258504

On 25 Nov, Konstantin Belousov wrote: > On Sat, Nov 23, 2013 at 11:43:30PM -0800, Don Lewis wrote: >> I upgraded my 11.0-CURRENT machine to r258504 to get past the uma panic >> that I stumbled across earlier. Now I got this when I started upgrading >> ports: >> >

Re: panic: double fault with 11.0-CURRENT r258504

On 27 Nov, Konstantin Belousov wrote: > On Wed, Nov 27, 2013 at 12:22:27AM -0800, Don Lewis wrote: >> It took a while, but I just got another double fault, though this one is >> somewhat different. This time it trapped in cpu_switch(), which >> resulted in calls

Re: panic: double fault with 11.0-CURRENT r258504

On 27 Nov, Konstantin Belousov wrote: > On Wed, Nov 27, 2013 at 01:13:41AM -0800, Don Lewis wrote: >> On 27 Nov, Konstantin Belousov wrote: >> > On Wed, Nov 27, 2013 at 12:22:27AM -0800, Don Lewis wrote: >> >> It took a while, but I just got another double fault, tho

Re: panic: double fault with 11.0-CURRENT r258504

On 27 Nov, I wrote: > On 27 Nov, Konstantin Belousov wrote: >> On Wed, Nov 27, 2013 at 01:13:41AM -0800, Don Lewis wrote: >>> On 27 Nov, Konstantin Belousov wrote: >>> > On Wed, Nov 27, 2013 at 12:22:27AM -0800, Don Lewis wrote: >>> >> It took a while

Re: panic: double fault with 11.0-CURRENT r258504

On 27 Nov, Konstantin Belousov wrote: > On Wed, Nov 27, 2013 at 02:49:12AM -0800, Don Lewis wrote: >> <http://people.freebsd.org/~truckman/doublefault2.JPG> > > What is the instruction at cpu_switch+0x9b ? movl 0x8(%edx),%eax This machine is

Re: panic: double fault with 11.0-CURRENT r258504

On 27 Nov, Konstantin Belousov wrote: > On Wed, Nov 27, 2013 at 09:41:36AM -0800, Don Lewis wrote: >> On 27 Nov, Konstantin Belousov wrote: >> > On Wed, Nov 27, 2013 at 02:49:12AM -0800, Don Lewis wrote: >> >> <http://people.freebsd.org/~truckman/doublef

Re: panic: double fault with 11.0-CURRENT r258504

On 27 Nov, Konstantin Belousov wrote: > On Wed, Nov 27, 2013 at 10:33:30AM -0800, Don Lewis wrote: >> On 27 Nov, Konstantin Belousov wrote: >> > On Wed, Nov 27, 2013 at 09:41:36AM -0800, Don Lewis wrote: >> >> On 27 Nov, Konstantin Belousov wrote: >> >>

Re: panic: double fault with 11.0-CURRENT r258504

On 27 Nov, Konstantin Belousov wrote: > On Wed, Nov 27, 2013 at 11:02:57AM -0800, Don Lewis wrote: >> On 27 Nov, Konstantin Belousov wrote: >> > On Wed, Nov 27, 2013 at 10:33:30AM -0800, Don Lewis wrote: >> >> On 27 Nov, Konstantin Belousov wrote: >> >>

Re: panic: double fault with 11.0-CURRENT r258504

On 27 Nov, Konstantin Belousov wrote: > On Wed, Nov 27, 2013 at 11:35:19AM -0800, Don Lewis wrote: >> On 27 Nov, Konstantin Belousov wrote: >> > On Wed, Nov 27, 2013 at 11:02:57AM -0800, Don Lewis wrote: >> >> On 27 Nov, Konstantin Belousov wrote: >> >>

Re: panic: double fault with 11.0-CURRENT r258504

On 27 Nov, Konstantin Belousov wrote: > And, as the last resort, I do understand that this sounds as giving up, > do you monitor the temperature of the CPUs ? BTW, which CPUs are that, > please show the cpu identification lines from the boot dmesg. Idle temps: hw.acpi.thermal.tz0.temperature: 38

Re: panic: double fault with 11.0-CURRENT r258504

On 28 Nov, Konstantin Belousov wrote: > On Wed, Nov 27, 2013 at 01:11:35PM -0800, Don Lewis wrote: >> On 27 Nov, Konstantin Belousov wrote: >> > On Wed, Nov 27, 2013 at 11:35:19AM -0800, Don Lewis wrote: >> >> On 27 Nov, Konstantin Belousov wrote: >> >>

Re: panic: double fault with 11.0-CURRENT r258504

On 28 Nov, Konstantin Belousov wrote: > On Thu, Nov 28, 2013 at 12:56:37AM -0800, Don Lewis wrote: >> I haven't figured out how to find the currently installed BIOS version. >> The motherboard is Abit, which is no more, but I found an archive of all >> of their downlo

Re: panic: double fault with 11.0-CURRENT r258504

On 30 Nov, Konstantin Belousov wrote: > On Sat, Nov 30, 2013 at 01:02:16PM +0100, Peter Holm wrote: >> On Thu, Nov 28, 2013 at 09:56:10AM +0200, Konstantin Belousov wrote: >> > Peter, could you, please, try to reproduce the issue ? It does not look >> > like a random hardware failure, since in all

Re: panic: double fault with 11.0-CURRENT r258504

On 30 Nov, To: kostik...@gmail.com wrote: > On 30 Nov, Konstantin Belousov wrote: >> On Sat, Nov 30, 2013 at 01:02:16PM +0100, Peter Holm wrote: >>> On Thu, Nov 28, 2013 at 09:56:10AM +0200, Konstantin Belousov wrote: >>> > Peter, could you, please, try to reproduce the issue ? It does not look >>

Re: panic: double fault with 11.0-CURRENT r258504

On 30 Nov, To: kostik...@gmail.com wrote: > On 30 Nov, Konstantin Belousov wrote: >> On Sat, Nov 30, 2013 at 01:02:16PM +0100, Peter Holm wrote: >>> On Thu, Nov 28, 2013 at 09:56:10AM +0200, Konstantin Belousov wrote: >>> > Peter, could you, please, try to reproduce the issue ? It does not look >>

Re: SVN commit 259045 breaks -CURRENT

On 15 Dec, Konstantin Belousov wrote: > On Sun, Dec 15, 2013 at 05:28:14PM +0100, Marc UBM wrote: >> On Sun, 15 Dec 2013 08:43:22 +0200 >> Konstantin Belousov wrote: >> >> > On Sat, Dec 14, 2013 at 09:56:04PM -0800, Steve Kargl wrote: >> > > On Sun, Dec 15, 2013 at 07:47:22AM +0200, Konstantin Be

Re: netstat: sysctl: net.route.0.0.dump.0: Cannot allocate memory

On 21 Feb, Ian FREISLICH wrote: > Hiroki Sato wrote: >> ia> While recieving my routing table I used to be able to check how far >> ia> it got by counting the output netstat -rn. It takes about 2 seconds >> ia> to recieve the routes from my route-server, but over a minute to >> ia> update the kerne

Re: libinit idea

On 23 Feb, Lucius Rizzo wrote: > * Andreas Nilsson [2014-02-23 09:33]: >> Imho, the replacement to init and rc-scripts I sometimes think about >> would be to import SMF from opensolaris/illumos. There one can at >> least get the commands run and config used without looking at the >> source code. >

Re: libinit idea

On 24 Feb, Thomas Mueller wrote: > from Don Lewis: > >> I've got a Fedora server here that has systemd and I've come to >> dislike it. It seems to be one of those "Do not open. No user >> serviceable parts inside." sorts of things. > >

Re: libinit idea

On 23 Feb, David Chisnall wrote: > 5) In a world where we're moving towards sandboxing services via > Capsicum, the service launcher needs to be able to create services > with a potentially large set of initial file descriptors (including a > socket to Casper), based on the configuration policy.

Re: Import of DragonFly Mail Agent

On 25 Feb, Peter Jeremy wrote: > On 2014-Feb-24 10:44:30 -0600, Bryan Drewery wrote: >> >>I have the Oreilly sendmail book here and it's thicker than The Design >>and Implementation of the FreeBSD Operating System. That's quite an >>application! > > More impressively, ISTR it's thicker than "The

Re: firebox build fails post clang-3.4 merge

On 26 Feb, Michael Butler wrote: > On 02/18/14 12:10, Michael Butler wrote: >> Is anyone else seeing firefox failing to install after the clang-3.4 >> merge? As in xpcshell dumping core .. > > An update .. > > Recompiling with GCC48 on -current yields the same result. Seems to run > correctly whe

Re: firebox build fails post clang-3.4 merge

On 26 Feb, Benjamin Kaduk wrote: > On Wed, 26 Feb 2014, Don Lewis wrote: > >> On 26 Feb, Michael Butler wrote: >>> On 02/18/14 12:10, Michael Butler wrote: >>>> Is anyone else seeing firefox failing to install after the clang-3.4 >>>> merge? As

Re: firebox build fails post clang-3.4 merge

On 28 Feb, Dimitry Andric wrote: > On 27 Feb 2014, at 01:57, Don Lewis wrote: >> On 26 Feb, Michael Butler wrote: >>> On 02/18/14 12:10, Michael Butler wrote: >>>> Is anyone else seeing firefox failing to install after the clang-3.4 >>>> merge? As in x

Re: nvi: can't be used in the context of substitute

On 2 Mar, Zhihao Yuan wrote: > On Sun, Mar 2, 2014 at 6:04 AM, Xin Li wrote: >> It looks like the new nvi version don't accept in the context of >> substitute. A minimal use case would be to replace all leading 8 >> spaces with tabs, what one would do on older version of nvi would be: >> >> : 1

Re: Status of llvm/clang 3.4?

On 4 Mar, Ed Maste wrote: > On 4 March 2014 12:22, Steve Kargl wrote: >> >> On Tue, Mar 04, 2014 at 12:17:18PM +, Thomas Mueller wrote: >> > What is the current status of clang, regarding known bugs, on >> > FreeBSD-current? >> > >> > There were reports of www/firefox failing to build becaus

ports/INDEX building broken on 11.0-CURRENT

Please excuse the crosspost. I'm not sure if this is a ports problem or a CURRENT problem. I just updated my 11.0-CURRENT machine to r265940 and can no longer build ports/INDEX-11. My ports tree is r353903. I think this problem is being caused by the recent changes to /usr/share/mk/*. # make i

Re: ports/INDEX building broken on 11.0-CURRENT

On 13 May, To: po...@freebsd.org wrote: > Please excuse the crosspost. I'm not sure if this is a ports problem or > a CURRENT problem. > > I just updated my 11.0-CURRENT machine to r265940 and can no longer > build ports/INDEX-11. My ports tree is r353903. I think this problem > is being caused

Re: access to hard drives is "blocked" by writes to a flash drive

On 3 Mar, Poul-Henning Kamp wrote: > For various reasons (see: Lemming-syncer) FreeBSD will block all I/O > traffic to other disks too, when these pileups gets too bad. The Lemming-syncer problem should have mostly been fixed by 231160 in head (231952 in stable/9 and 231967 in stable/8) a little

Re: access to hard drives is "blocked" by writes to a flash drive

On 4 Mar, Konstantin Belousov wrote: > On Sun, Mar 03, 2013 at 07:01:27PM -0800, Don Lewis wrote: >> On 3 Mar, Poul-Henning Kamp wrote: >> >> > For various reasons (see: Lemming-syncer) FreeBSD will block all I/O >> > traffic to other disks too, when these

Re: access to hard drives is "blocked" by writes to a flash drive

On 4 Mar, Peter Jeremy wrote: > On 2013-Mar-03 23:12:40 -0800, Don Lewis wrote: >>On 4 Mar, Konstantin Belousov wrote: >>> It could be argued that the current typical value of 16MB for the >>> hirunningbufspace is too low, but experiments with increasing it did >&

Re: access to hard drives is "blocked" by writes to a flash drive

On 4 Mar, Poul-Henning Kamp wrote: > Content-Type: text/plain; charset=ISO-8859-1 > > In message <201303040712.r247cejp008...@gw.catspoiler.org>, Don Lewis writes: > >>Prior to 231160, the syncer thread would call sync_vnode() for the >>syncer vnode of ea

Re: access to hard drives is "blocked" by writes to a flash drive

On 4 Mar, Ian Lepore wrote: > On Sun, 2013-03-03 at 19:01 -0800, Don Lewis wrote: >> On 3 Mar, Poul-Henning Kamp wrote: >> >> > For various reasons (see: Lemming-syncer) FreeBSD will block all I/O >> > traffic to other disks too, when these pileups gets t

Re: access to hard drives is "blocked" by writes to a flash drive

On 4 Mar, Ian Lepore wrote: > On Sun, 2013-03-03 at 20:28 +, Steven Hartland wrote: >> - Original Message - >> From: "Ian Lepore" >> To: "Poul-Henning Kamp" >> Cc: "deeptech71" ; ; >> "Peter Jeremy" >> Sent: Sunday, March 03, 2013 1:54 PM >> Subject: Re: access to hard drives is "

Re: access to hard drives is "blocked" by writes to a flash drive

On 5 Mar, Poul-Henning Kamp wrote: > Content-Type: text/plain; charset=ISO-8859-1 > > In message <201303050519.r255jbau012...@gw.catspoiler.org>, Don Lewis writes: > >>That's been my opinion for a long time as well, though I think it would >>be bett

Re: access to hard drives is "blocked" by writes to a flash drive

On 5 Mar, Poul-Henning Kamp wrote: > In message <201303050840.r258egag012...@gw.catspoiler.org>, Don Lewis writes: > >>For composite devices such as mirrors, using the first underlying device >>is probably a reasonable choice. For more complicated cases, or to >>ov

Re: access to hard drives is "blocked" by writes to a flash drive

On 5 Mar, Ian Lepore wrote: > I've debated playing with the bio work loop in mmcsd to see if moving > reads ahead of writes was helpful, but that seems like a dangerous path > to go down without some mitigation strategy to ensure that writes go > through eventually. That seems especially importa

nvme controller reset failures on recent -CURRENT

I just upgraded my package build machine to: FreeBSD 15.0-CURRENT #110 main-n268161-4015c064200e from: FreeBSD 15.0-CURRENT #106 main-n265953-a5ed6a815e38 and I've had two nvme-triggered panics in the last day. nvme is being used for swap and L2ARC. I'm not able to get a crash dump, probably

Re: nvme controller reset failures on recent -CURRENT

On 12 Feb, Mark Johnston wrote: > On Mon, Feb 12, 2024 at 04:28:10PM -0800, Don Lewis wrote: >> I just upgraded my package build machine to: >> FreeBSD 15.0-CURRENT #110 main-n268161-4015c064200e >> from: >> FreeBSD 15.0-CURRENT #106 main-n265953-a5ed6a815e38 >>

Re: nvme controller reset failures on recent -CURRENT

e a while. > On Mon, Feb 12, 2024, 4:28 PM Don Lewis wrote: > >> I just upgraded my package build machine to: >> FreeBSD 15.0-CURRENT #110 main-n268161-4015c064200e >> from: >> FreeBSD 15.0-CURRENT #106 main-n265953-a5ed6a815e38 >> and I've had two n

Re: nvme controller reset failures on recent -CURRENT

On 12 Feb, Warner Losh wrote: > On Mon, Feb 12, 2024 at 9:15 PM Don Lewis wrote: > >> On 12 Feb, Maxim Sobolev wrote: >> > Might be an overheating. Today's nvme drives are notoriously flaky if you >> > run them without proper heat sink attached to it. >>

more fallout from removal of lint

Since lint was removed from 12.0-CURRENT, it is not possible to build 11.1-STABLE on a 12.0-CURRENT host, but I was able to work around that by copying /usr/bin/true to /usr/bin/lint. Unfortunately, that trick doesn't work when updating a 11.1-STABLE poudriere jail on a 12.0-CURRENT host. ===> us

Re: 11.1-jail on CURRENT: sh: lint: not found *** [llib-lposix.ln] Error code 127

Put the following in /usr/local/etc/poudriere.d/src.conf: LINT=/usr/bin/false That skips the attempt to build the lint library because of this: .if ${LINT} == "lint" _llib= llib .else _llib= .endif SUBDIR= lint1 lint2 xlint ${_llib} in /usr/src/usr.bin/xlint/Makefile On 8 Jan, O

Re: 11.1-jail on CURRENT: sh: lint: not found *** [llib-lposix.ln] Error code 127

There doesn't appear to be a knob to disable building lint for FreeBSD 11.x. Linking or copying /usr/bin/true to /usr/bin/lint works for cross building 11 on on a 12.0-CURRENT machine, but I was not able to get it to work when rebuilding a poudriere jail. On 8 Jan, Warner Losh wrote: > Does buil

Re: Strange ARC/Swap/CPU on yesterday's -CURRENT

On 27 Mar, Andriy Gapon wrote: > On 24/03/2018 01:21, Bryan Drewery wrote: >> On 3/20/2018 12:07 AM, Peter Jeremy wrote: >>> >>> On 2018-Mar-11 10:43:58 -1000, Jeff Roberson >>> wrote: Also, if you could try going back to r328953 or r326346 and let me know if the problem exists in eith

Re: Strange ARC/Swap/CPU on yesterday's -CURRENT

On 1 Apr, Don Lewis wrote: > On 27 Mar, Andriy Gapon wrote: >> On 24/03/2018 01:21, Bryan Drewery wrote: >>> On 3/20/2018 12:07 AM, Peter Jeremy wrote: >>>> >>>> On 2018-Mar-11 10:43:58 -1000, Jeff Roberson >>>> wrote: >>>>&g

Re: Strange ARC/Swap/CPU on yesterday's -CURRENT

On 3 Apr, Don Lewis wrote: > On 1 Apr, Don Lewis wrote: >> On 27 Mar, Andriy Gapon wrote: >>> On 24/03/2018 01:21, Bryan Drewery wrote: >>>> On 3/20/2018 12:07 AM, Peter Jeremy wrote: >>>>> >>>>> On 2018-Mar-11 10:43:58 -1000, Jeff Robe

Re: Strange ARC/Swap/CPU on yesterday's -CURRENT

On 3 Apr, Cy Schubert wrote: > Try arbitrarily reducing arc_max through sysctl. ARC is immediately > reduced and free memory increased however wired pages remains the > same. One thing that I've noticed is that with r329844 and earlier is that there can be a difference of multiple GB between the

Re: Strange ARC/Swap/CPU on yesterday's -CURRENT

On 4 Apr, Mark Johnston wrote: > On Tue, Apr 03, 2018 at 09:42:48PM -0700, Don Lewis wrote: >> On 3 Apr, Don Lewis wrote: >> > I reconfigured my Ryzen box to be more similar to my default package >> > builder by disabling SMT and half of the RAM, to limit it to 8 co

Re: Strange ARC/Swap/CPU on yesterday's -CURRENT

On 4 Apr, Don Lewis wrote: > On 4 Apr, Mark Johnston wrote: >> On Tue, Apr 03, 2018 at 09:42:48PM -0700, Don Lewis wrote: >>> On 3 Apr, Don Lewis wrote: >>> > I reconfigured my Ryzen box to be more similar to my default package >>> > builder by disabli

Re: Strange ARC/Swap/CPU on yesterday's -CURRENT

On 4 Apr, Mark Johnston wrote: > On Tue, Apr 03, 2018 at 09:42:48PM -0700, Don Lewis wrote: >> On 3 Apr, Don Lewis wrote: >> > I reconfigured my Ryzen box to be more similar to my default package >> > builder by disabling SMT and half of the RAM, to limit it to 8 co

Re: Strange ARC/Swap/CPU on yesterday's -CURRENT

On 7 Apr, Justin Hibbits wrote: > On Fri, Apr 6, 2018 at 10:25 AM, Justin Hibbits wrote: >> On Fri, Apr 6, 2018 at 10:08 AM, Mark Johnston wrote: >>> On Fri, Apr 06, 2018 at 12:47:14AM +, Justin Hibbits wrote: My powerpc64 embedded machine is virtually unusable since these vm changes. >

Re: [RFC] Deprecation and removal of the drm2 driver

On 18 May, Warner Losh wrote: > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > >> On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: >> > On Fri, May 18, 2018, 20:00 Niclas Zeising wrote: >> > >> > > I propose that we remove the old drm2

Re: rndc: connect failed: 127.0.0.1#953: permission denied

On 2 Jun, O. Hartmann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On CURRENT, running on an APU as router/firewall service, out of the blue > after an update > I receive this weird message when trying to restart "named" (BIND 9.12, > latest from the > ports): > > service nam

Re: Is kern.sched.preempt_thresh=0 a sensible default?

On 9 Jun, Stefan Esser wrote: > 3) Programs that evenly split the load on all available cores have been >suffering from sub-optimal assignment of threads to cores. E.g. on a >CPU with 8 (virtual) cores, this resulted in 6 cores running the load >in nominal time, 1 core taking twice as

Re: review of nfsd rc.d script patch

On 15 Jun, Rick Macklem wrote: > Hi, > > For the pNFS service MDS machine, the nfsd can't be started until all nfs > mounts > in /etc/fstab are done. > I think that adding "mountcritremote" to the "# REQUIRE:" line is sufficient > to do this? > > I don't think delaying the startup of the nfsd d

Re: MRSAS Panic during Install.

On 9 Jun, Andriy Gapon wrote: > On 09/06/2020 03:42, Santiago Martinez wrote: >> Hi Everyone, today I tested with 12.1 and it works without any issues (at >> least >> for now). >> >> I will sync against current and see if it fails. >> >> Santiago >> >> On 2020-06-08 17:41, Santiago Martinez wr

Re: Getting /usr/src to match specific git hash?

On 24 Jan, Yasuhiro Kimura wrote: > From: Steve Kargl > Subject: Getting /usr/src to match specific git hash? > Date: Sat, 23 Jan 2021 19:58:52 -0800 > >> Suppose one has an empty /usr/src. >> >> Suppose further that one had to re-install a 32-bit >> i386-*-freebsd with the 24 Dec 2020 image ava

<    1   2   3   4   5   >