Re: statd/lockd startup failure

). But what might cause the above errors? -- George Mitchell We have been seeing this too, with the addition of mountd. So I decided to try and track it down. rpc.lockd, rpc.statd or mountd, all share the same code for allocating address/port. I added some more info to be displayed in case

Re: Firefox startup impacted by distributed.net client

have the awful NFS client performance problem (though not as bad as before the Rick Macklem patch).-- George Mitchell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail

Re: Firefox startup impacted by distributed.net client

On 03/23/11 17:57, Matthias Gamsjager wrote: Have you tried 8 stable? The box I tried SCHED_4BSD on was running 8.2_PRERELEASE, which still had the problem described. Has the scheduler changed significantly between 8.2_PRERELEASE and stable? -- George Mitchell On 23 Mar

Re: Firefox startup impacted by distributed.net client

On 03/23/11 18:52, Jeremy Chadwick wrote: On Wed, Mar 23, 2011 at 06:24:05PM -0400, George Mitchell wrote: On 03/23/11 17:57, Matthias Gamsjager wrote: Have you tried 8 stable? The box I tried SCHED_4BSD on was running 8.2_PRERELEASE, which still had the problem described. Has the scheduler

Re: Heads up: you'll need to do a fresh config KERNEL etc

about 8.x at last. (Except for SCHED_ULE, which gives terrible performance on a single-core machine with a compute-bound process running in the background.) Thanks! -- George Mitchell ___ freebsd-stable@freebsd.org mailing list http

Re: Heads up: you'll need to do a fresh config KERNEL etc

.x, and I have a warm, fuzzy feeling about 8.x at last. (Except for SCHED_ULE, which gives terrible performance on a single-core machine with a compute-bound process running in the background.) Thanks! -- George Mitchell There's a weird (and you need to have a weird sense of humour to enjoy

Statistics?

/mail from this server, were shut down. Notwithstanding, I've had a very warm, fuzzy feeling about 7.1-RELEASE for a long time now! -- George Mitchell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable

Re: TCP Reassembly Issues

? -- George Mitchell P.S. A lot of other 9.0 features look very nice indeed! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: TCP Reassembly Issues

On 11/26/11 00:23, Lawrence Stewart wrote: [...] Could those who have reported the bug and are able to recompile their kernel to test a patch please try the following and report back to the list: http://people.freebsd.org/~lstewart/patches/misctcp/tcp_reass_plugzoneleak_10.x.r227986.patch [...]

Re: TCP Reassembly Issues

= 0x4101 umass0:2:0:-1: Attached to scbus2 (probe0:umass-sim0:0:0:0): AutoSense failed (da0:umass-sim0:0:0:0): got CAM status 0x4 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device - 0 outstanding (da0:umass-sim0:0:0:0): removing device entry -- George

SCHED_ULE should not be the default

will be mightily displeased with their FreeBSD systems when they do. Is there some case where SCHED_ULE exhibits significantly better performance than SCHED_4BSD? If not, I think SCHED-4BSD should remain the default GENERIC configuration until this is fixed. -- George Mitchell

Re: SCHED_ULE should not be the default

with: # ktrdump -ctf ktr-ule-problem.out It's 44MB, so it's at http://www.m5p.com/~george/ktr-ule-problem.out and send the file to this mailing list. Thanks, Attilio I hope this helps.-- George Mitchell ___ freebsd

Re: SCHED_ULE should not be the default

On 12/09/11 19:59, Attilio Rao wrote: [...] What svn revision did you use for it? What is the CPUs frequencies of machines generating this? Attilio Hope the attached helps. -- George Mitchell Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980

Re: SCHED_ULE should not be the default

AN ORDER OF MAGNITUDE worse performance[1], making ULE the default seems like a bad choice. -- George Mitchell [1] http://lists.freebsd.org/pipermail/freebsd-stable/2011-December/064773.html ___ freebsd-stable@freebsd.org

Re: SCHED_ULE should not be the default

bxe overnight (compared to getting to netgragh with the default kern.sched.preempt_thresh setting). -- George Mitchell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail

Re: SCHED_ULE should not be the default

problems tried to set sysctl kern.sched.steal_thresh=1 ? [...] 1 appears to be the default value for kern.sched.steal_thresh. -- George Mitchell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable

Re: SCHED_ULE should not be the default

On 12/09/11 19:57, George Mitchell wrote: On 12/09/11 10:17, Attilio Rao wrote: [...] More precisely I'd be interested in KTR traces. To be even more precise: With a completely stable GENERIC configuration (or otherwise please post your kernel config) please add the following: options KTR

Re: SCHED_ULE should not be the default

.-- George Mitchell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: SCHED_ULE should not be the default

On 12/14/11 21:05, Oliver Pinter wrote: [...] Hi! Can you try with this settings: op@opn ~ sysctl kern.sched. kern.sched.cpusetsize: 8 kern.sched.preemption: 0 kern.sched.name: ULE kern.sched.slice: 13 kern.sched.interact: 30 kern.sched.preempt_thresh: 224 kern.sched.static_boost: 152

Re: SCHED_ULE should not be the default

don't know how to analyze them myself. What do all of us do next? -- George Mitchell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr

9.0-RC3 umass quirks?

I have a USB compact flash reader-writer which is normally connected to my computer all the time but rarely contains a compact flash card. Here is a snippet from a verbose dmesg with FreeBSD 9.0-RC3: ugen0.5: vendor 0x05e3 at usbus0 umass0: vendor 0x05e3 USB TO IDE, class 0/0, rev 2.00/0.32,

Re: 9.0-RC3 umass quirks?

On 01/-10/63 14:59, George Mitchell wrote: I have a USB compact flash reader-writer which is normally connected to my computer all the time but rarely contains a compact flash card. Here is a snippet from a verbose dmesg with FreeBSD 9.0-RC3: ugen0.5: vendor 0x05e3 at usbus0 umass0: vendor

Re: [releng_8_2 tinderbox] failure on powerpc/powerpc

not completely commit their changes, and then absconded to a place where they fail to receive these emails about the problems. Can someone please either diagnose these errors or else revert the deficient commits? -- George Mitchell ___ freebsd

ata_controlcmd undefined

I csupped my 9.0-STABLE kernel on Sunday and now get this message at the beginning of booting up: link-elf-obj: symbol ata_controlcmd undefined KLD file atapicat.ko - could not finalize loading Kernel configuration is GENERIC (except scheduler is SCHED_4BSD). -- George Mitchell

Re: ata_controlcmd undefined

On 06/05/12 11:20, Oliver Fromme wrote: George Mitchell wrote: I csupped my 9.0-STABLE kernel on Sunday and now get this message at the beginning of booting up: link-elf-obj: symbol ata_controlcmd undefined KLD file atapicat.ko - could not finalize loading The same happened

9.0-STABLE: Can't umount umass device

changed) da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 # mount -t msdosfs /dev/da0s1 /flash # umount /flash umount: unmount of /flash failed: Device busy -- George Mitchell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman

Re: 9.0-STABLE: Can't umount umass device

/flash Thanks for the tip, But, AARGH! Everything in the world seems to depend on this gamin thing. What's the recommended course of action?-- George On Tue, Jul 03, 2012 at 08:42:55PM -0400, George Mitchell wrote: uname -a: FreeBSD

Re: 9.0-STABLE: Can't umount umass device

On 07/04/12 00:42, Ian Lepore wrote: On Tue, 2012-07-03 at 20:42 -0400, George Mitchell wrote: uname -a: FreeBSD wonderland.m5p.com 9.0-STABLE FreeBSD 9.0-STABLE #9: Sun Jun 3 10:01:09 EDT 2012 geo...@wonderland.m5p.com:/usr/obj/usr/src/sys/WONDERLAND amd64 dmesg | grep umass: umass0:Bulk

Odd ttyvN TERM settings

(or other such programs) on ttyv1 through ttyv8, unless you remember to setenv TERM xterm. Why did we change from cons25 to xterm? How can we get all the ttyvNs to get the correct TERM setting? -- George Mitchell ___ freebsd-stable

Re: Odd ttyvN TERM settings

On 07/08/12 10:14, Ronald Klop wrote: On Sun, 08 Jul 2012 16:00:16 +0200, George Mitchell george+free...@m5p.com wrote: Up through FreeBSD 8.x, the ttyvN consoles had a TERM setting of cons25. On FreeBSD 9.n, it appears to be xterm for ttyv0, but it's still cons25 for ttyv1-ttyv8 (even though

Re: FreeBSD 9.1 stability/robustness?

with 8.3 with 4BSD scheduler for now. -- George Mitchell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: SU+J on 9.1-RC2 ISO

On 11/03/12 15:09, Jeremy Chadwick wrote: (Please keep me CC'd, as I'm not subscribed to -stable) I've CC'd Nathan Whitehorn, who according to bsdinstall(8) is the author (not sure if maintainer) of the code. This default has already begun to bite users/SAs in the ass:

Re: [releng_9_1 tinderbox] failure on powerpc64/powerpc

On 11/04/12 14:59, FreeBSD Tinderbox wrote: TB --- 2012-11-04 19:53:34 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-04 19:53:34 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012

boot2 FreeBSD 9.2-RC1 r253913M

boot2 gives me a boot: prompt but will not accept input from the keyboard on an HP CQ61-420US notebook. Fortunately, it times out after a few seconds and boots normally after that. But it's still a bit annoying. -- George

Re: boot2 FreeBSD 9.2-RC1 r253913M

On 08/04/13 15:27, George Mitchell wrote: boot2 gives me a boot: prompt but will not accept input from the keyboard on an HP CQ61-420US notebook. Fortunately, it times out after a few seconds and boots normally after that. But it's still a bit annoying

Re: 9.2-RC2 Now Available

On 08/16/13 22:17, Glen Barber wrote: The second release candidate builds of the 9.2-RELEASE release cycle are now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64, and sparc64 architectures. [...] Glen Has any progress been made on diagnosing this NFS deadlock?

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

Will someone PLEASE remove freebsd-stable from the CC list of this ticket? Thank you. -- George On 08/09/16 19:10, bugzilla-nore...@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211491 > > Ngie Cooper changed: > >

Re: Jenkins build is still unstable: FreeBSD_stable_10 #356

On 08/08/16 18:56, jenkins-ad...@freebsd.org wrote: > See > [...] Can someone please clarify for me the distinction between succeeding vs. failing and being stable vs. unstable? -- George ___

Re: Jenkins build is still unstable: FreeBSD_stable_10 #356

On 08/09/16 05:10, Craig Rodrigues wrote: > > > On Mon, Aug 8, 2016 at 4:26 PM, George Mitchell <george+free...@m5p.com > <mailto:george+free...@m5p.com>> wrote: > [...] > Can someone please clarify for me the distinction between > succeeding vs. fail

Re: 10.3-RELEASE-p13 "unsupported file layout"

On 01/11/17 15:24, George Mitchell wrote: > After today's OpenSSH security message, I [tried a buildworld and] > got to: > > building shared library libc.so.7 > cc (a very long compile line) > ./libc.so.7: unsupported file layout > [...] I never did figure out the cause o

Failing to upgrade from 10.1-RELEASE to 10.3-STABLE

# freebsd-update -r 10.3-STABLE upgrade Looking up update.FreeBSD.org mirrors... 4 mirrors found. Fetching metadata signature for 10.1-RELEASE from update5.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. The following components of FreeBSD seem to be installed:

Re: Benchmarks results for FreeBSD 11

On 08/23/16 02:32, Erich Dollansky wrote: > Hi, > > On Mon, 22 Aug 2016 03:22:35 + > Kubilay Kocak wrote: > >> On Mon, 22 Aug 2016, 11:31 AM Mark Linimon >> wrote: >> >>> On Mon, Aug 22, 2016 at 09:57:24AM +1000, Dewayne Geraghty wrote:

Re: ath0 associated, wlan0 not associated

On 11/05/16 01:05, Adrian Chadd wrote: > nope, sorry. There's a lot of work in the -11 wifi stack and drivers. > > > -a > > [...] Okay, I downloaded and installed 11.0-RELEASE on a spare slice, and dmesg tells me the following (with regard to ath0): ath0: mem 0xf0a0-0xf0a7 irq 36

Re: ath0 associated, wlan0 not associated

On 11/05/16 13:00, George Mitchell wrote: > On 11/05/16 01:05, Adrian Chadd wrote: >> nope, sorry. There's a lot of work in the -11 wifi stack and drivers. >> >> >> -a >> >> [...] > > Okay, I downloaded and installed 11.0-RELEASE on a spare slice, an

Re: Symbol/library versioning ...

On 11/15/16 11:24, Konstantin Belousov wrote: > On Tue, Nov 15, 2016 at 10:59:57AM -0500, George Mitchell wrote: >> ... is a topic I just marginally understand. But pkg 1.9.3 fails >> on FreeBSD 10.1-RELEASE-p35 because /lib/libc.so.7 contains no >> definition for "open

Symbol/library versioning ...

... is a topic I just marginally understand. But pkg 1.9.3 fails on FreeBSD 10.1-RELEASE-p35 because /lib/libc.so.7 contains no definition for "openat", though /lib/libc.so.7 on 10.3-RELEASE-p11 does define it. I confess to being baffled. How is this supposed to work? 10.1-RELEASE is still

ath0 associated, wlan0 not associated

Originally posted to freebsd-wireless; no solution yet so I thought I'd try here. After booting up, my ath0 interface says it is associated, but my wlan0 says it is not: FreeBSD 10.3-RELEASE-p11 wpa_supplicant v2.0 Copyright (c) 2003-2012, Jouni Malinen and contributors

Re: ath0 associated, wlan0 not associated

it may have improved that device. > > Thanks! > > > -a > > > On 3 November 2016 at 07:09, George Mitchell <george+free...@m5p.com> wrote: >> Originally posted to freebsd-wireless; no solution yet so I thought >> I'd try here. After booting up, my ath0

Re: huge nanosleep variance on 11-stable

On 11/01/16 23:45, Kevin Oberman wrote: > On Tue, Nov 1, 2016 at 2:36 PM, Jason Harmening > wrote: > >> Sorry, that should be ~*30ms* to get 30fps, though the variance is still >> up to 500ms for me either way. >> >> On 11/01/16 14:29, Jason Harmening wrote: >>> repro

Re: Failing to upgrade from 10.1-RELEASE to 10.3-STABLE

On 10/09/16 15:57, Kurt Jaeger wrote: > Hi! > >> What am I doing wrong? (I get the same failure attempting to upgrade >> to 10.1-RELEASE and 10.2-RELEASE.) -- George > > Ah, one thing: > > Please do update to the latest 10.1-REL patch level, first. > After upgrading to

Re: Failing to upgrade from 10.1-RELEASE to 10.3-STABLE

On 10/10/16 03:04, Matthew Seaman wrote: > [...] > Most of the time you should be able to upgrade from any patch level of > release to the latest on any supported release branch using > freebsd-update(8). However there have been a number of occasions where > changes to freebsd-update itself cause

Re: Clandestine USB SD card slot

Whoops, I should send this to freebsd-stable instead of freebsd-usb. Sorry! -- George On 10/16/16 09:22, George Mitchell wrote: > On 10/15/16 23:10, Anthony Jenkins wrote: >> On 10/15/16 18:28, George Mitchell wrote: >>> FreeB

Re: Clandestine USB SD card slot

On 10/16/16 14:16, Warner Losh wrote: > On Sun, Oct 16, 2016 at 12:08 PM, Warren Block <wbl...@wonkity.com> wrote: >> On Sun, 16 Oct 2016, George Mitchell wrote: >> >>>> So not only is it (apparently) recognized, but the sdhci_pci driver >>>> attached t

Re: Clandestine USB SD card slot

On 10/16/16 17:40, George Mitchell wrote: > On 10/16/16 14:16, Warner Losh wrote: >> On Sun, Oct 16, 2016 at 12:08 PM, Warren Block <wbl...@wonkity.com> wrote: >>> On Sun, 16 Oct 2016, George Mitchell wrote: >>> >>>>> So not only is it (

Re: Clandestine USB SD card slot

On 10/17/16 11:02, George Mitchell wrote: > [...] > After setting hw.sdhci.debug=1 and hw.mmc.debug=1 in /etc/sysctl.conf > and doing a verbose boot, then inserting and removing an SD card, all > I get in "dmesg | egrep mmc\|sdhci" is: > > sdhci_pci0: mem 0xf0c6c000

Re: 10.3-RELEASE-p13 "unsupported file layout"

On 01/11/17 17:46, George Mitchell wrote: > On 01/11/17 17:20, Kevin Oberman wrote: >> [...] >> >> While I have no suggestions about the error building libc, your statement >> that you can't use freebsd-update due to your use of a custom kernel is >> incorrec

10.3-RELEASE-p13 "unsupported file layout"

After today's OpenSSH security message, I did: cd /usr rm -rf obj cd src svn update -r311916 make buildworld After a while, I got to: building shared library libc.so.7 cc (a very long compile line) ./libc.so.7: unsupported file layout *** Error code 1 Stop. make[4]: stopped in

Re: 10.3-RELEASE-p13 "unsupported file layout"

On 01/11/17 17:25, Dimitry Andric wrote: > On 11 Jan 2017, at 21:24, George Mitchell <george+free...@m5p.com> wrote: >> >> After today's OpenSSH security message, I did: >> >> cd /usr >> rm -rf obj > > Hmm, not sure if it is wise to completely remov

Re: 10.3-RELEASE-p13 "unsupported file layout"

On 01/11/17 17:40, Dimitry Andric wrote: > On 11 Jan 2017, at 23:35, George Mitchell <george+free...@m5p.com> wrote: >> >> On 01/11/17 17:25, Dimitry Andric wrote: >>> On 11 Jan 2017, at 21:24, George Mitchell <george+free...@m5p.com> wrote: > ... >>

Re: 10.3-RELEASE-p13 "unsupported file layout"

On 01/11/17 17:20, Kevin Oberman wrote: > [...] > > While I have no suggestions about the error building libc, your statement > that you can't use freebsd-update due to your use of a custom kernel is > incorrect. This is a common misconception and, in cases of very limited > disk space, may be

Re: 10.3-RELEASE-p13 "unsupported file layout"

On 01/11/17 15:24, George Mitchell wrote: > After today's OpenSSH security message, I did: > > cd /usr > rm -rf obj > cd src > svn update -r311916 > make buildworld > > After a while, I got to: > > building shared library libc.so.7 > cc (a very long compile l

Re: Freebsd 11 - /usr/bin missing [xl]zgrep/zegrep/zfgrep

On 03/22/17 00:07, Kyle Evans wrote: > [...] > For grep(1) to be GNU grep while xzgrep to secretly be a link to BSD > grep would be quite surprising to me as a user/admin, especially since > there are very real output and argument differences between the two. > [...] It would not surprise me.

fence_wait returned with error -512?

Any idea what this means? Jun 9 19:57:43 haymarket kernel: fence_wait returned with error -512 Jun 9 19:59:52 haymarket kernel: fence_wait returned with error -512 Jun 9 20:00:40 haymarket kernel: fence_wait returned with error -512 Jun 9 20:11:30 haymarket last message repeated 19 times Jun

Re: PRERELEASE back?

On 06/02/18 11:14, Kevin Oberman wrote: > After teh announcement of RC1 I updated my 11-STABLE box, expecting wither > that I would see RC1 or STABLE, depending on whether the 11.2 BRANCH had > been created, but instead I am "back" at 11.2-PRERELEASE #1. > > Is this intentional? At least it is

Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

> On Wed, 30 May 2018 15:50:39 + > Glen Barber wrote: > >> Hi, >> >> Could folks please help boot-test the most recent 12.0-CURRENT amd64 >> memstick images on various hardware? Note, this is not a request to >> install 12.0-CURRENT, only a boot-test with various system knobs >> tweaked. >>

Re: FreeBSD 11.2-RC1 Now Available

On 06/01/18 21:31, Glen Barber wrote: > [...] > If you would like to use SVN to do a source based update of an existing > system, use the "stable/11" branch. > [...] So what's releng/11.2, chopped liver? -- George signature.asc Description: OpenPGP digital signature

Re: Ryzen issues on FreeBSD (can we sum up yet)?

On 02/12/18 16:49, Don Lewis 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 > > Since applying that patch, I did three poudriere runs to

Ryzen consensus

Based on people's recent Ryzen experiences, is it fair to say that FreeBSD 11.2 is now believed to work on Ryzens, if you have a recent enough Ryzen and your motherboard has been updated to the latest BIOS? -- George signature.asc Description: OpenPGP digital signature

Re: Ryzen consensus

Thanks to all who responded! I guess it's off to Microcenter this week. -- George signature.asc Description: OpenPGP digital signature

Re: more data: SCHED_ULE+PREEMPTION is the problem

On 04/07/18 10:18, Peter wrote: > [...] > B. Findings: > > 1. Filesystem > > I could never reproduce this when reading from plain UFS. Only when > reading from ZFS (direct or via l2arc). > [...] My consistent way of reproducing the problem was to run ports/misc/dnetc while trying to

Re: kern.sched.quantum: Creepy, sadistic scheduler

On 04/04/18 06:39, Alban Hertroys wrote: > [...] > That said, SCHED_ULE (the default scheduler for quite a while now) was > designed with multi-CPU configurations in mind and there are claims that > SCHED_4BSD works better for single-CPU configurations. You may give that a > try, if you're not

Re: kern.sched.quantum: Creepy, sadistic scheduler

On 04/04/18 10:34, Peter wrote: > [...] It does not make sense to me if now we state that > we cannot do it anymore because single-CPU is uncommon today. > [...] +1.-- George signature.asc Description: OpenPGP digital signature

Re: kern.sched.quantum: Creepy, sadistic scheduler

On 04/17/18 19:01, George Mitchell wrote: > On 04/17/18 17:20, EBFE via freebsd-stable wrote: >> [...] >> For interactive tasks, there is a "special" tunable: >> % sysctl kern.sched.interact >> kern.sched.interact: 10 # default is 30 >> % sysctl -d

more data: SCHED_ULE+PREEMPTION is the problem

On 04/07/18 10:18, Peter wrote: > Hi all, > [...] Thanks for all the investigation! > 3. kern.sched.preempt_thresh > > I could make the problem disappear by changing kern.sched.preempt_thresh >  from the default 80 to either 11 (i5-3570T) or 7 (p3) or smaller. This > seems to correspond to the

Re: kern.sched.quantum: Creepy, sadistic scheduler

On 04/17/18 17:20, EBFE via freebsd-stable wrote: > On Tue, 17 Apr 2018 09:05:48 -0700 > Freddie Cash wrote: > >> # Tune for desktop usage >> kern.sched.preempt_thresh=224 >> >> ​Works quite nicely on a 4-core AMD Phenom-II X4 960T Processor >> (3010.09-MHz K8-class CPU)

Re: Stability of 11.1S

On 03/21/18 04:51, Eitan Adler wrote: > On 19 March 2018 at 22:59, Dewayne Geraghty > wrote: >> [...] >> PS Normally I would bisect, but we're converting 2 large PROLOG applications >> to erlang... (prayers welcome) > [...] What next, converting a FORTH

Re: DNS Flag Day and freebsd.org problems

On 1/17/19 6:55 PM, David Magda wrote: > Hello, > > On February 1, 2019, there will be some major changes to DNS with regards to > EDNS: > [...] > It turns out that freebsd.org is effected by this: > [...] > Who is the person that should be looking at this for FreeBSD? > [...] According to

Re: Upgrading via source build, 10.4->11.2

On 12/4/18 9:35 PM, Warner Losh wrote: > On Tue, Dec 4, 2018, 7:25 PM George Mitchell [...] >> kldxref /boot/kernel >> kldxref: unknown metadata record 4 in file atacard.ko >> kldxref: unknown metadata record 4 in file atp.ko >> kldxref: unknown metadata record

Re: Upgrading via source build, 10.4->11.2

On 12/5/18 9:31 AM, Miroslav Lachman wrote: > George Mitchell wrote on 2018/12/05 14:24: >> [...] >> But what I really need to know is >> whether to make buildworld under 10.4 or 11.2.  Or do I do it twice? >> And presumably I can't run mergemaster until after buildwor

Upgrading via source build, 10.4->11.2

/usr/src/UPDATING says: To build a kernel - If you are updating from a prior version of FreeBSD (even one just a few days old), you should follow this procedure. It is the most failsafe as it uses a /usr/obj tree with a fresh

Re: Upgrading, 11.4 -> 12.1

On 2020-08-31 15:48, Kurt Jaeger wrote: > Hi! > [...] > > I'm guessing: Do you have the dbus and hald daemon running ? > > hald_enable="YES" > dbus_enable="YES" > > in /etc/rc.conf ? > Yes, I do. Should I disable them, then? -- George signature.asc Description: OpenPGP digital

Re: Upgrading, 11.4 -> 12.1

On 2020-08-31 16:28, Kevin Oberman wrote: > [...] > This question would be both more appropriate and more likely to get a > knowledgeable response if submitted to x11@. [...] While waiting in vain for a response, I resorted to reading /usr/ports/UPDATING and the install message for xorg-server.

Re: Upgrading, 11.4 -> 12.1

On 2020-08-31 15:47, Navdeep Parhar wrote: > On 8/31/20 12:44 PM, George Mitchell wrote: >> 1. Is there a way to shut "make delete-old" up? For most minor >> upgrades, of course, it never says anything. But for an upgrade such >> as this, it forces me to type

Upgrading, 11.4 -> 12.1

1. Is there a way to shut "make delete-old" up? For most minor upgrades, of course, it never says anything. But for an upgrade such as this, it forces me to type "y" upwards of a hundred times. All the things it's deleting look plausible to me and I've never had occasion to tell it NOT to delete

Re: 11.4 sendmail with SASL and ports openssl?

On 2020-08-11 09:49, Bengt Ahlgren wrote: > I have since long compiled sendmail in base with SASL using a src.conf > like this: > > # sendmail with SASL required for outgoing SMTP AUTH, see: > # https://www.freebsd.org/doc/en/books/handbook/SMTP-Auth.html > # depends on port security/cyrus-sasl2

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

On 12/23/20 11:58 AM, Warner Losh wrote: [...] mergemaster and etcupdate can cope without them. Warner [...] Until this moment, I had never heard of etcupdate, and I had mergemaster practically programmed into my fingers for system updates. So I read the man page for etcupdate, and it looks

Re: How do I know if my 13-stable has security patches?

On 2/25/21 3:56 PM, Warner Losh wrote: [...] We should likely just publish the 'v' number in the advisories. It's basically a count back to the start of the project. We put that number in uname already. [] +1 !!! -- George OpenPGP_signature

Re: Deprecating base system ftpd

On 4/10/21 2:58 AM, Scott Bennett via freebsd-stable wrote: [...]I would like something far smaller, namely, a choice of schedulers during/just after installation of a -RELEASE without having to a) download the entire source tree, b) make buildworld, and c) make buildkernel. [...] +1 many