Re: Reducing UFS corruption from unclean shutdowns?

2019-06-21 Thread Conrad Meyer
On Fri, Jun 21, 2019 at 2:55 PM Alan Somers wrote: > I would've thought that immediately following a sync(8), the > filesystem would be consistent. Why do I still see errors after a > panic in files that were written before I sync()ed? > -Alan Hi Alan, Contra the name, sync(2) (sync(8)) isn't

Re: CURRENT >r349150: boot failure in rc.conf.local

2019-06-18 Thread Conrad Meyer
Hi everyone, Please find a proposed fix in https://reviews.freebsd.org/D20686 . I didn't notice this thread because I'm already subscribed to current and CC's don't display any differently in my mail reader. (I don't read every thread on current.) Take care, Conrad On Tue, Jun 18, 2019 at

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

2019-05-27 Thread Conrad Meyer
Hi Rainier, On Mon, May 27, 2019 at 7:47 AM wrote: > I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > department who is technically responsible for the service gets around > redoing that service. Even if this proposal is approved, it would only affect 13+. You could still

Re: Weirdness when writing to pseudofs file

2019-05-22 Thread Conrad Meyer
On Wed, May 22, 2019 at 1:58 PM Johannes Lundberg wrote: > > It seems, a single '>' will cause it to try to create the file (even > > though it already exists) and that fails (kern_openat). > > > I would guess because of > >

Re: random_sources_feed: rs_read for hardware device 'Intel Secure Key RNG' returned no entropy.

2019-05-08 Thread Conrad Meyer
Sorry about that. Please update to r347329. Thanks, Conrad On Wed, May 8, 2019 at 9:16 AM Andrey V. Elsukov wrote: > Hi, > > today I updated one of my test machines and discovered that message from > the subject periodically printed in the console. > > FreeBSD 13.0-CURRENT

Re: Optimization bug with floating-point?

2019-03-13 Thread Conrad Meyer
Hi John, On Wed, Mar 13, 2019 at 10:17 AM John Baldwin wrote: > One issue I'm aware of is that clang does not have any support for the > special arrangement FreeBSD/i386 uses where it uses different precision > for registers vs in-memory for some of the floating point types (GCC has > a special

Re: PMC Sierra SPC SAS-SATA Card + ESXi

2019-03-10 Thread Conrad Meyer
Hi Evgheni, Is it possible to replace the card with a different one? The PMC Sierra driver is not very good. Best, Conrad On Sun, Mar 10, 2019 at 12:24 AM Evgheni Melman wrote: > > So I got this weird setup, where I … a PMC-Sierra PM8003 > card (same as PM8001, but with external QSFP afaik) …

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-02-28 Thread Conrad Meyer
On Thu, Feb 28, 2019 at 10:32 AM Steve Kargl wrote: > This is interesting as well. Does this mean that amd64 is now > the only tier 1 platform and all other architectures are after > thoughts? This has been the de facto truth for years. i386 is mostly only supported by virtue of sharing code

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-02-23 Thread Conrad Meyer
On Sat, Feb 23, 2019 at 12:44 AM Steve Kargl wrote: > Ideas? > ... > +CPU: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz (1995.04-MHz 686-class > CPU) >Origin="GenuineIntel" Id=0x6fd Family=0x6 Model=0xf Stepping=13

Re: r344398 Import ACPICA 20190215: breaks bhyve

2019-02-21 Thread Conrad Meyer
Oops, to the list this time. Hi Oleg, Those look like the ACPI lines bhyve attempts to generate and compile in basl_fwrite_madt(): 272 /* Legacy IRQ0 is connected to pin 2 of the IOAPIC */ 273 EFPRINTF(fp, "[0001]\t\tSubtable Type : 02\n"); 274 EFPRINTF(fp,

Re: sha256 speed

2019-01-06 Thread Conrad Meyer
There is support for the SHA intrinsic in aesni(4) that would be relatively easy to adapt to userspace for libmd, if someone was interested. Especially now that we demand linker ifunc support (on x86 platforms, at least). I posted a patch and some performance comparison in

Re: buildworld falure: truncated or malformed archive

2018-12-31 Thread Conrad Meyer
There's always 'WITHOUT_CLANG=1' in src.conf. Best, Conrad On Mon, Dec 31, 2018 at 12:09 PM Warner Losh wrote: > > On Mon, Dec 31, 2018, 1:36 PM Ryan Stone > > Does this mean that it's currently impossible to build a world with > > debug symbols? > > > > Yes. Clang is simply too big until 64

Re: possible POLA violation for NFS server to make it Linux compatible

2018-12-18 Thread Conrad Meyer
On Tue, Dec 18, 2018 at 5:07 PM Rick Macklem wrote: > The change to make the FreeBSD NFSv4 server use vfs.nfsd.nfs_privport is > trivial > and I think being compatible with Linux is important (I see it as the defacto > standard NFS implementation these days). > > What do others think I should

Re: toolchain(s) for universe kernels

2018-11-19 Thread Conrad Meyer
I use: make -sj${NCPU} tinderbox JFLAG=-j${NCPU} UNIVERSE_TARGET=kernel-toolchain -DNO_CLEAN Best, Conrad On Mon, Nov 19, 2018 at 10:00 AM Eric van Gyzen wrote: > > I want to > > make MAKE_JUST_KERNELS=1 universe > > but it seems that I need a toolchain first. There are multiple >

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

2018-11-13 Thread Conrad Meyer
Perfect! Sounds like we are on the right track, at least. Best, Conrad On Tue, Nov 13, 2018 at 8:55 PM Rebecca Cran wrote: > > On Tuesday, 13 November 2018 21:41:58 MST Conrad Meyer wrote: > > You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL? > > I.e.,

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

2018-11-13 Thread Conrad Meyer
Please try r340426 :-). On Tue, Nov 13, 2018 at 8:41 PM Conrad Meyer wrote: > > You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL? > I.e., sometimes the CPU chooses to report on a range from 0-225C and > sometimes -49C-206C. I think someone else's 2990WX did the

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

2018-11-13 Thread Conrad Meyer
, sigh, it never landed: https://reviews.freebsd.org/D16855 Ok I'll go ahead and commit that too. Thanks, Conrad On Tue, Nov 13, 2018 at 8:38 PM Conrad Meyer wrote: > > On Tue, Nov 13, 2018 at 8:29 PM Rebecca Cran wrote: > > > > On Tuesday, 13 November 2018 21:17:59 MST

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

2018-11-13 Thread Conrad Meyer
On Tue, Nov 13, 2018 at 8:29 PM Rebecca Cran wrote: > > On Tuesday, 13 November 2018 21:17:59 MST Conrad Meyer wrote: > > > Maybe it should be -54 instead of +54? 183-(54*2) is the somewhat > > plausible 75?C (still pretty warm even for load). How good is your > >

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

2018-11-13 Thread Conrad Meyer
On Tue, Nov 13, 2018 at 8:05 PM Rebecca Cran wrote: > > On Tuesday, 13 November 2018 16:20:22 MST Stefan Ehmann wrote: > > > The 2700 has an offset of 0 though (2700X has 10). > > And I'm seeing a difference of more than 30 degrees. I guess something > > else must be happening here. > > I had

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

2018-11-13 Thread Conrad Meyer
On Tue, Nov 13, 2018 at 7:16 PM Daniel Eischen wrote: > > On Tue, 13 Nov 2018, Conrad Meyer wrote: > > > On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote: > >> I've attached it. If it gets filtered by the mail list, I'll > >> make it http accessible. > &

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

2018-11-13 Thread Conrad Meyer
Of course, Johannes has already thought of this! See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228480 and https://reviews.freebsd.org/D15567 . On Tue, Nov 13, 2018 at 6:41 PM Conrad Meyer wrote: > > On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote: > > I've attached it.

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

2018-11-13 Thread Conrad Meyer
On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote: > I've attached it. If it gets filtered by the mail list, I'll > make it http accessible. Thanks Daniel. It looks like your hostbridge zero device has a different device id than in my first generation Ryzen system. Would you please try the

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

2018-11-13 Thread Conrad Meyer
On Tue, Nov 13, 2018 at 5:15 PM Rozhuk Ivan wrote: > > On Tue, 13 Nov 2018 19:41:47 -0500 > Daniel Eischen wrote: > > > >> I'm trying to track down a couple of things. amdtemp doesn't > > >> report any temperature sensors, and acpi seems to have some > > >> errors. Not sure if they are

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

2018-11-13 Thread Conrad Meyer
Hi Daniel, On Tue, Nov 13, 2018 at 10:01 AM Daniel Eischen wrote: > > Greetings, > > I'm trying to track down a couple of things. amdtemp doesn't > report any temperature sensors, and acpi seems to have some > errors. Not sure if they are related. Maybe not. If they do not attach, it

Re: Hole-punching, TRIM, etc

2018-11-13 Thread Conrad Meyer
On Tue, Nov 13, 2018 at 2:59 PM Alan Somers wrote: > > On Tue, Nov 13, 2018 at 3:51 PM Conrad Meyer wrote: >> >> On Tue, Nov 13, 2018 at 2:10 PM Alan Somers wrote: >> > ... >> > 8) Add aio_freesp(2), an asynchronous version of fcntl(F_FREESP). >&g

Re: Hole-punching, TRIM, etc

2018-11-13 Thread Conrad Meyer
Hi Alan, On Tue, Nov 13, 2018 at 2:10 PM Alan Somers wrote: > > Hole-punching has been discussed on these lists before[1]. It basically > means to turn a dense file into a sparse file by deallocating storage for > some of the blocks in the middle. There's no standard API for it. Linux > uses

Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G

2018-11-13 Thread Conrad Meyer
On Tue, Nov 13, 2018 at 1:04 PM Stefan Ehmann wrote: > After kldload amdtemp I see the following sysctls: > dev.cpu.0.temperature: 77.1C > dev.amdtemp.0.core0.sensor0: 77.1C > > The temperature I see in BIOS is much lower (maybe around 40.0C). Don't > know if just the offset is wrong or the

Re: building head -r338675 with devel/amd64-gcc: /usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored

2018-09-21 Thread Conrad Meyer
One thing that may allow progress is explicitly passing the path to a new enough linker to make. In the past when some I encountered a similar problem (I use amd64-xtoolchain-gcc, amd64-gcc, and binutils for toolchain, and due to some miscommunication the wrong linker was selected automatically),

Re: newfs silently fails if random is not ready (?)

2018-09-05 Thread Conrad Meyer
Differential up here: https://reviews.freebsd.org/D17049 for any lurkers I didn't manage to tag in the review. Best, Conrad On Wed, Sep 5, 2018 at 12:57 AM, Mark R V Murray wrote: > Nice catch! Thanks :-) > > M > > >> On 5 Sep 2018, at 04:13, Conrad Meyer wrote: >&

Re: newfs silently fails if random is not ready (?)

2018-09-04 Thread Conrad Meyer
= EWOULDBLOCK) + error = 0; + KASSERT(error == 0, ("unexpected %d", error)); } if (error == 0) { read_rate_increment((uio->uio_resid + sizeof(uint32_t))/sizeof(uint32_t)); Best, Conrad On Tue, Sep 4, 2018 at 8:13 PM, Conrad Mey

Re: newfs silently fails if random is not ready (?)

2018-09-04 Thread Conrad Meyer
Hi Lev, I took a first attempt at reproducing this problem on a fast desktop-class system. First steps, give us a way to revert back to unseeded status: --- a/sys/dev/random/fortuna.c +++ b/sys/dev/random/fortuna.c @@ -39,6 +39,7 @@ __FBSDID("$FreeBSD$"); #ifdef _KERNEL #include +#include

Re: newfs silently fails if random is not ready (?)

2018-09-04 Thread Conrad Meyer
On Tue, Sep 4, 2018 at 2:10 PM, Lev Serebryakov wrote: > Wednesday, September 5, 2018, 12:05:43 AM, you wrote: >> I think it is tripping on raise/abort() in one of these routines, but >> nothing is printing that information. See below. > > Maybe, it should be fixed? Yes, it should. > One

Re: newfs silently fails if random is not ready (?)

2018-09-04 Thread Conrad Meyer
Hi Lev, On Tue, Sep 4, 2018 at 1:55 PM, Lev Serebryakov wrote: > Tuesday, September 4, 2018, 11:37:59 PM, you wrote: >> Is newfs tripping on a raise()/abort() in arc4random(3) / >> getentropy(3)? > Nope, it is silently does nothing I think it is tripping on raise/abort() in one of these

Re: newfs silently fails if random is not ready (?)

2018-09-04 Thread Conrad Meyer
Hi Lev, Newfs just uses arc4random(3) to generate its FSID and generation numbers. arc4random(3) is seeded from getentropy(3) -> getrandom(2) -> read_random_uio(9), which is what produces the "random: read_random_uio unblock wait" messages. Is newfs tripping on a raise()/abort() in

Re: github freebsd and svn freebsd

2018-09-04 Thread Conrad Meyer
On Tue, Sep 4, 2018 at 3:32 AM, tech-lists wrote: > Hello list, > > What's the difference between github freebsd and svn freebsd, other than one > is on github and the other is on svn? The github repository is read-only mirror -- new additions all come through SVN. > How does one transcode or

Re: ffs_truncate3 panics

2018-08-08 Thread Conrad Meyer
On Wed, Aug 8, 2018 at 5:30 AM, Rick Macklem wrote: > - Oh, and this is an old i386 with 256Mbytes (not one of them new fangled > computers, >where memory is in Gbytes;-) Have you run memtest86+ recently? Best, Conrad ___

Re: acpiconf -s 3 does not call acpi sleep event handlers

2018-08-02 Thread Conrad Meyer
For those not on the bug, this is being followed up in PR 230290. On Wed, Aug 1, 2018 at 10:27 PM, Johannes Lundberg wrote: > > > On Thu, Aug 2, 2018 at 06:20 Andriy Gapon wrote: >> >> On 02/08/2018 01:17, Conrad Meyer wrote: >> > I don't understand the concer

Re: acpiconf -s 3 does not call acpi sleep event handlers

2018-08-01 Thread Conrad Meyer
t; On Wed, Aug 1, 2018 at 22:55 Conrad Meyer wrote: >> >> ReqSleepState is the routine that takes care of suspend, not the >> eventhandler. I'm not sure what difference the proposed change is >> supposed to make. > > > Listeners to acpi_sleep_event don’t get

Re: acpiconf -s 3 does not call acpi sleep event handlers

2018-08-01 Thread Conrad Meyer
ReqSleepState is the routine that takes care of suspend, not the eventhandler. I'm not sure what difference the proposed change is supposed to make. Best, Conrad On Wed, Aug 1, 2018 at 2:48 PM, Johannes Lundberg wrote: > > > On Wed, Aug 1, 2018 at 9:15 PM Conrad Meyer wrote: >&

Re: acpiconf -s 3 does not call acpi sleep event handlers

2018-08-01 Thread Conrad Meyer
It seems deliberate, although the commit message does not call it out and the event is perhaps poorly named. The event currently indicates that the lid was closed. And the final registered eventhandler for the event calls ReqSleepState. The ReqSleepState routine, as well as the userspace ioctl

Re: Changes to sysctl values

2018-07-26 Thread Conrad Meyer
On Thu, Jul 26, 2018 at 8:52 PM, Shane Ambler wrote: > I use devel/py-sysctl in some scripts to get values, using a recent > 12-current (r336728) I see at least two values that get a different > value type than on 11-stable. Same version of python and port. > ... Hi Shane, At some point, new

Re: how do I use the make universe machines?

2018-06-06 Thread Conrad Meyer
On Tue, Jun 5, 2018 at 6:12 PM, Benjamin Kaduk wrote: > On Wed, Jun 06, 2018 at 12:47:17AM +, Rick Macklem wrote: >> I've heard mention of "make universe" machines multiple times, >> but have no idea how to use them? >> Is there doc on this? >> >> Thanks, rick >> ps: I'll admit I haven't

Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64]

2018-05-06 Thread Conrad Meyer
The same change as for powerpc needs to be made for riscv — the (bcopy) trick — to avoid expansion. Best, Conrad P.S., Mark, your email server is misconfigured and most/all of your emails get flagged as spam. I only saw this because I occasionally check the spam folder. On Sat, May 5, 2018 at

Re: Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed)

2018-04-16 Thread Conrad Meyer
Hi Vitalij, On Mon, Apr 16, 2018 at 3:27 AM, Vitalij Satanivskij wrote: > DUMP can be found here http://hell.ukr.net/panic/panic.jpg > or even video record from screen http://hell.ukr.net/panic/recorder.webm Looks like the panic message is printed directly after: "igb0: using 2

Re: clang manual page?

2018-04-05 Thread Conrad Meyer
stent manual page is of little > help. In fact, your 7 word response is an affirmation that > the tools supplied in base should be properly documented. > > -- > steve > > > > On Thu, Apr 05, 2018 at 05:42:58PM -0700, Conrad Meyer wrote: >> I never said it was in base

Re: clang manual page?

2018-04-05 Thread Conrad Meyer
To a first order approximation, the manual page for clang is gcc(1). Conrad On Thu, Apr 5, 2018 at 3:38 PM, Steve Kargl wrote: > Is anyone working on fixing the clang manual to actually > document the available options? > > % man clang > (search for -std=) >

Re: clang manual page?

2018-04-05 Thread Conrad Meyer
C++ standard library to use > > Does == ? > > -- > steve > > On Thu, Apr 05, 2018 at 04:37:38PM -0700, Conrad Meyer wrote: >> To a first order approximation, the manual page for clang is gcc(1). >> >> Conrad >> >> On Thu, Apr 5, 2018 at 3:38 PM, Steve Kargl

Re: FreeBSD has a politics problem

2018-03-03 Thread Conrad Meyer
John, A good portion of your original email happens to be inaccurate or misleading. In the spirit of good faith discussion, I'm going to assume you're just accidentally misinformed, and not willfully misrepresenting things. So, some corrections and clarifications follow. If you have further

Re: Kernel selection in Lua loader

2018-02-21 Thread Conrad Meyer
On Wed, Feb 21, 2018 at 6:11 AM, Kyle Evans wrote: > On Wed, Feb 21, 2018 at 6:36 AM, David Wolfskill wrote: >> >> ... >> kernels="kernel kernel.old kernel.save" >> >> and the Forth loader presented (precisely) those kernels as the >> available options

Re: pkg does not recognize correct kernel version

2018-02-20 Thread Conrad Meyer
On Mon, Feb 19, 2018 at 2:38 PM, Ronald Klop wrote: > On Mon, 19 Feb 2018 22:05:51 +0100, Konstantin Belousov > wrote: > >> Look at the man page. pkg reads version from the /bin/sh ELF FreeBSD > > > Which man page? I can't find it in pkg help update or

Re: Since last week (today) current on my Ryzen box is unstable

2018-02-17 Thread Conrad Meyer
On Sat, Feb 17, 2018 at 12:52 PM, Andrew Reilly wrote: > I've applied the patch, and the boot process is quiet now, but it's still > loading cc_vegas.ko, seemingly in response to seeing this device: (from > pciconf -l -v) > > none4@pci0:17:0:2: class=0x108000

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

2018-02-13 Thread Conrad Meyer
On Tue, Feb 13, 2018 at 6:02 AM, David Wolfskill wrote: > On Tue, Feb 13, 2018 at 12:48:19PM +0300, Vladimir Zakharov wrote: >> >> > > It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error. >> > > At least, removing it fixes build for me. > > FWIW, I have

Re: multimedia/libvpx cause clang fatal error on CURRENT

2018-01-29 Thread Conrad Meyer
Is this the same issue as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225488 ? That was fixed in r328513. Please try that revision if you're not at it yet. On Mon, Jan 29, 2018 at 7:57 PM, Iblis Lin wrote: > Hi, > > I got this while building multimedia/libvpx > >

Re: To which list should I submit a patch?

2018-01-04 Thread Conrad Meyer
IMO, either is fine. I think documentation may refer to docs outside of the src tree, whereas this is in the src tree. Thanks for the submission. Best, Conrad On Thu, Jan 4, 2018 at 12:42 PM, Leonardo Fogel wrote: > > > Hi, > I have written a short patch that

Re: Intel CPU design flaw - FreeBSD affected? // disabling LDTSC

2018-01-04 Thread Conrad Meyer
Possibly because Xeon 5400 dates to 2007 — it may have less advanced speculative / out-of-order execution and may not have the same branch prediction algorithm as Haswell. On Thu, Jan 4, 2018 at 1:07 PM, Michael Butler wrote: > On 01/04/18 14:59, Klaus P.

Re: Poll: should man(1)'s default pager change to "less -s"?

2017-12-12 Thread Conrad Meyer
nt using a tiny phone keyboard. > Apologies for any typos and autocorrect. > Also, this old phone only supports top post. Apologies. > > Cy Schubert > <cy.schub...@cschubert.com> or <c...@freebsd.org> > The need of the many outweighs the greed of the few. > --- >

Re: Poll: should man(1)'s default pager change to "less -s"?

2017-12-12 Thread Conrad Meyer
On Tue, Dec 12, 2017 at 10:27 AM, Steve Kargl wrote: > There isn't a question. I'm pointing out your poll apparently > is limited to a select few individuals that use FreeBSD. The select few individuals being "literally anyone that wants to participate?"

Re: kernel panic: make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0)

2017-11-15 Thread Conrad Meyer
Hi Wolfram, I believe r305900 broke it. I don't have any patch or workaround, sorry. It wouldn't be too hard for someone interested in virtualization to fix the issue. Please follow up in the bug :-). Best, Conrad On Wed, Nov 15, 2017 at 7:16 AM, Wolfram Schneider wrote:

Re: kernel panic: make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0)

2017-11-15 Thread Conrad Meyer
Hi Wolfram, Looks like the same issue as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531 . Best, Conrad On Wed, Nov 15, 2017 at 1:31 AM, Wolfram Schneider wrote: > Hi, > > I have a virtual machine running with FreeBSD 11-stable at a cloud > provider. It runs fine. I

Re: Encrypted Swap Problem with 12.0-CURRENT r324427

2017-10-10 Thread Conrad Meyer
Thomas, Please try r32. Based on your panic message, "panic: freeing invalid range," it may be the same general swap issue which r32 aimed to address. Best, Conrad On Tue, Oct 10, 2017 at 2:20 PM, Thomas Laus wrote: > Allan Jude [allanj...@freebsd.org] wrote: >> >>

Re: C++ in jemalloc

2017-10-06 Thread Conrad Meyer
On Fri, Oct 6, 2017 at 9:17 AM, Ian Lepore wrote: > It isn't about "a broken port". All C++ code is broken if exceptions > don't work. That means devd is broken. Not to mention clang itself. > It may be that neither of those relies on exceptions for routine > operation and

Re: C++ in jemalloc

2017-10-06 Thread Conrad Meyer
On Thu, Oct 5, 2017 at 9:58 PM, Mark Millard wrote: > Luckily most kernel and world code that I actively use > does not throw C++ exceptions in my use. > > But devel/kyua is majorly broken by the C++ exception > issue: It makes extensive use of C++ exceptions. In my > view

Re: panic in AcpiOsGetTimer during boot.

2017-10-01 Thread Conrad Meyer
Hey Rick, Are you running into the same issue reported on this svn-src thread? https://lists.freebsd.org/pipermail/svn-src-all/2017-September/151775.html I believe jkim has reverted the change in a subsequent revision (r324136). Best, Conrad On Sun, Oct 1, 2017 at 3:12 PM, Rick Macklem

Re: r323694 amd64 - crash in linsysfs: Was: svn commit: r323692 - in head/sys/compat: linsysfs linux

2017-09-18 Thread Conrad Meyer
Please try r323710. I believe you're running into the issue Hans noticed here: https://lists.freebsd.org/pipermail/svn-src-all/2017-September/151324.html . It should be addressed in r323710. Sorry, Conrad ___ freebsd-current@freebsd.org mailing list

Re: Panic: @r323525: iflib

2017-09-13 Thread Conrad Meyer
Well, we know it's due to r323516, but unfortunately can't have you bisect from there because it was committed as a giant lump. If it can't be fixed quickly, maybe it should be reverted? Best, Conrad On Wed, Sep 13, 2017 at 6:10 AM, David Wolfskill wrote: > My build

Re: extending the maximum filename length (pointer to patch)[request for input]

2017-09-12 Thread Conrad Meyer
On Tue, Sep 12, 2017 at 2:23 PM, Rainer Duffner wrote: > And there’s also this bug: > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215067 > > "g_dev_taste: make_dev_p() failed on importing pool with snapshots with long > names“ > > > > But maybe that has nothing

Re: extending the maximum filename length (pointer to patch)[request for input]

2017-09-12 Thread Conrad Meyer
On Tue, Sep 12, 2017 at 2:11 PM, Ben RUBSON wrote: > Hi Conrad, > > This patch makes me think about another related bug #184340 : > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184340 > It is about PATH_MAX which in some cases can be too small. > > Not sure if it's the

Re: extending the maximum filename length

2017-09-12 Thread Conrad Meyer
On Sat, Sep 9, 2017 at 9:09 AM, Julian Elischer wrote: > maybe we could get it into -current. > It'd be silly to have to have people re-inventing hte wheel all the time. > How about you put those changes into the reviews.freebsd.org and we can get > some general consensus on

Re: extending the maximum filename length

2017-09-08 Thread Conrad Meyer
On Fri, Sep 8, 2017 at 10:21 AM, David Wolfskill wrote: > On Sat, Sep 09, 2017 at 01:15:31AM +0800, Julian Elischer wrote: >> Has anyone using freeBSD ever increased NAME_MAX (filename maximum >> length) and have any experience with it? >> >> We ($JOB) would recompile the

Re: extending the maximum filename length

2017-09-08 Thread Conrad Meyer
On Fri, Sep 8, 2017 at 10:15 AM, Julian Elischer wrote: > Has anyone using freeBSD ever increased NAME_MAX (filename maximum length) > and have any experience with it? > > We ($JOB) would recompile the entire system so intra-system compatibility > would probably be ok, and we

Re: 64-bit inodes (ino64) Status Update and Call for Testing

2017-05-24 Thread Conrad Meyer
Hi Jilles, Thanks for bringing this up. And of course, thanks to kib@ for including the d_namlen size bump and for his work in driving the rest of this change through to completion. On Sun, May 21, 2017 at 5:14 AM, Jilles Tjoelker wrote: > We have another type in this area

Re: svn commit: r316977 - head/sys/dev/syscons

2017-04-15 Thread Conrad Meyer
On Sat, Apr 15, 2017 at 1:21 PM, O. Hartmann wrote: > Am Sat, 15 Apr 2017 20:03:50 + (UTC) > Bruce Evans schrieb: > >> Author: bde >> Date: Sat Apr 15 20:03:50 2017 >> New Revision: 316977 >> URL: https://svnweb.freebsd.org/changeset/base/316977 > >

Re: panic: invalid bcd xxx

2017-02-28 Thread Conrad Meyer
On Tue, Feb 28, 2017 at 2:31 PM, Eric van Gyzen 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 array and either complaining about the clock or

Re: 'Protocol not supported' on linux socket call ( r313313 amd64 )

2017-02-08 Thread Conrad Meyer
Hi Oleg, It seems likely it is related to r313284. Best, Conrad On Wed, Feb 8, 2017 at 7:44 AM, Oleg V. Nauman wrote: > After upgrading of current on amd64 box to r313313 I noticed that skype has > stopped working. > Below is the end of 'truss' output for skype: > >

Re: ASLR

2017-01-18 Thread Conrad Meyer
On Wed, Jan 18, 2017 at 9:53 AM, Johannes Lundberg wrote: > Hi > > What is the status of ASLR? > > https://reviews.freebsd.org/D5603 > > The thread has been silent for a couple of months. I'm happy to test if > needed. Hi Johannes, I think we were waiting on some review, but

Re: r311674: buildworld failure: iso_rrip.h:64:2: error: unknown type name 'cd_ino_t'

2017-01-08 Thread Conrad Meyer
Please try r311675. Thanks, Conrad On Sun, Jan 8, 2017 at 1:05 AM, O. Hartmann wrote: > It seems, the most recent CURRENT sources are broken (r311674), buildworld > failure occur > at: > > [...] > --- cd9660.o --- > In file included from

Re: Import rcorder-visualize.sh from NetBSD?

2016-12-05 Thread Conrad Meyer
Go ahead. On Mon, Dec 5, 2016 at 11:16 AM, 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=text/plain > > I ask in particular because of the

Re: r308432: Capsicumized `basename` make zsh prompt broken

2016-12-01 Thread Conrad Meyer
Hello Iblis, Please try reinstalling libcapsicum after r309366, rebuilding basename, and then removing the stdout kludge from your shell script. Let me know if there's still a problem! Thanks, Conrad On Sun, Nov 27, 2016 at 11:08 PM, Conrad Meyer <c...@freebsd.org> wrote: > Hi Iblis, &

Re: r308432: Capsicumized `basename` make zsh prompt broken

2016-11-27 Thread Conrad Meyer
Hi Conrad, >Thanks for your reply. > >I revert the basename.c and `< /dev/null` do the trick! >I'm also curious that will `caph_limit_stdio` break lots of program work > with some shell scripts? > > -- > Iblis Lin > > > On 11/28/2016 12:55, Conrad Meyer wrote

Re: r308432: Capsicumized `basename` make zsh prompt broken

2016-11-27 Thread Conrad Meyer
Hi Iblis, I see no such problem running 'basename $HOME' in a normal shell environment: > $ basename $HOME > cmeyer I suppose in your use, perhaps stdin is already closed? I think this is a limitation of caph_limit_stdio() in general. Can you try instead: function set_prompt {

Re: svn commit: r309144 - in head: lib/libipsec sys/net sys/netipsec [-r309174 does not fix everything]

2016-11-27 Thread Conrad Meyer
Hi Mark, I believe this was addressed by Scott Long in r309201. r309174 (an incomplete fix for the same problem) can probably be reverted. Best, Conrad On Sun, Nov 27, 2016 at 6:34 PM, Mark Millard wrote: > key_debug.c is not the only place with problems : The below is >

Re: /head/sys/kern/kern_timeout.c breaks build on current amd64

2016-08-16 Thread Conrad Meyer
Fixed in r304245. Thanks! On Tue, Aug 16, 2016 at 3:52 PM, Manfred Antar wrote: > New commit to current breaks build amd64: > > /usr/local/bin/ccache cc -c -O2 -pipe -fno-strict-aliasing -g -nostdinc -I. > -I../../.. -I../../../contrib/libfdt -D_KERNEL

Re: [FreeBSD-Announce] HEADS-UP: OpenSSH DSA keys are deprecated in 12.0 and 11.0

2016-08-08 Thread Conrad Meyer
The OpenSSH defaults are intentionally sane. RSA 2048 is anticipated to be fine for the next 10 years. It would not be a bad choice. I'm not aware of any reason not to use EC keys, and presumably the openssh authors wouldn't ship them as an option if they knew of any reason to believe they were

Re: SafeStack in base

2016-07-27 Thread Conrad Meyer
On Wed, Jul 27, 2016 at 5:05 PM, Shawn Webb <shawn.w...@hardenedbsd.org> wrote: > On Wed, Jul 27, 2016 at 05:02:07PM -0700, Conrad Meyer wrote: >> The problem appears to be an upstream limitation of >> -fsanitize=safe-stack: "Most programs, static libraries, or individua

Re: SafeStack in base

2016-07-27 Thread Conrad Meyer
On Wed, Jul 27, 2016 at 3:55 PM, Shawn Webb wrote: > Hey All, > > I'm interested in getting SafeStack working in FreeBSD base. Below is a > link to a simplistic (maybe too simplistic?) patch to enable SafeStack. > The patch applies against HardenedBSD's

Re: FreeBSD-11.0-BETA1-amd64-disc1.iso is too big for my 700MB CD-r

2016-07-12 Thread Conrad Meyer
Maybe Tier 2 can deal with just bootonly.iso. Or your machines should be dropped from Tier 2 if they don't support USB and we aren't okay with dropping disc1 support for all of Tier 2. There's lots of aging hardware we don't support in modern FreeBSD, including alpha and ia64. USB is 20 years

Re: FreeBSD-11.0-BETA1-amd64-disc1.iso is too big for my 700MB CD-r

2016-07-11 Thread Conrad Meyer
DVD-R dates to 1997; cheap USB flash devices are now pervasive. Maybe it's time to move on from CD. Best, Conrad On Mon, Jul 11, 2016 at 2:01 PM, Ronald Klop wrote: > Hi, > > Just downloaded the amd64 BETA1 ISO (873MB) and tried to burn a CD on > Windows 10. It complained

Re: clang 3.3/3.4 fails to build items that use stdlib.h because of __alloc_size attribute assigned to posix_memalign

2016-07-05 Thread Conrad Meyer
Whoops, missed reply-all the first time. It seems pretty clear that alloc_size (return value is a memory allocation of size from parameter N) does not apply to posix_memalign, because posix_memalign's allocation is stored via a pointer argument rather than return value.

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-13 Thread Conrad Meyer
I expect it's because: 1. bitstr_size() is just bytes (doesn't round up to sizeof(bitstr_t == unsigned long)) 2. The userspace version of bit_alloc() uses calloc(bitstr_size(), 1) (an array of nmemb=bitstr_size() size=bytes, doesn't have to be 'unsigned long' sized or aligned). 3. Various bit_*

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-13 Thread Conrad Meyer
FYI, this implies the ulong-accessed bitstring change is ABI-breaking for ARM userspace and maybe shouldn't go to stable/10. Best, Conrad On Mon, Jun 13, 2016 at 11:04 AM, Conrad Meyer <c...@freebsd.org> wrote: > I expect it's because: > > 1. bitstr_size() is just bytes (d

Re: thread suspension when dumping core

2016-06-06 Thread Conrad Meyer
On Mon, Jun 6, 2016 at 7:46 PM, Konstantin Belousov wrote: > On Mon, Jun 06, 2016 at 10:13:11AM -0700, Mark Johnston wrote: >> On Sat, Jun 04, 2016 at 12:32:36PM +0300, Konstantin Belousov wrote: >> > Does your fs both set TDF_SBDRY and call lf_advlock()/lf_advlockasync() ?

Re: Interesting error during installworld

2016-05-22 Thread Conrad Meyer
FreeBSD has tail(1). Does HardenedBSD remove it? Or is /usr/bin missing from your PATH? On Sun, May 22, 2016 at 1:21 PM, Shawn Webb wrote: > Hey All, > > I’m getting this error when doing `make installworld` on recent builds of > HEAD. It seems that the error is

Re: r299512 breaks dhclient on some networks

2016-05-18 Thread Conrad Meyer
On Wed, May 18, 2016 at 5:19 PM, Don Lewis wrote: > > It looks to me like r299512 is changing the format of the client > identifier by inserting the struct hardware hlen field into it. Yes. The problem with r299512 is that it assumed the client_id was actually a valid

Re: r299512 breaks dhclient on some networks

2016-05-18 Thread Conrad Meyer
Hey Ian, r299512 incorrectly encoded client identifiers because I misunderstood the intent of the sizeof()-scaled client_id. I reverted that change and replaced it with r300174, which I believe fixes the first overrun more correctly. (Coverity may still complain about CID 1305550, but I don't

Re: CFR: extend use of nitems() macro in the kernel.

2016-04-16 Thread Conrad Meyer
On Sat, Apr 16, 2016 at 11:25 AM, Pedro Giffuni wrote: > Hello; > > Using coccinelle, and some hand re-formatting, I generated a patch to > make use of the nitems() macro in sys, which is too big for > phabricator [1]. > > I was careful to exclude anything from the contrib

Re: Heads up

2016-04-15 Thread Conrad Meyer
Max, If you implement a new IO scheduler you can name it whatever you like. "NG" isn't any more meaningful than "Netflix." Best, Conrad On Fri, Apr 15, 2016 at 9:13 AM, Maxim Sobolev wrote: > Great, work Warner, thanks! Small note, though. The CAM_IOSCHED_NETFLIX > seems

Re: sdhci_pci.ko fails to load

2016-03-20 Thread Conrad Meyer
Try 'kldload mmc' first. 'sdhci_pci' is missing a MODULE_DEPEND on mmc. Best, Conrad On Sun, Mar 20, 2016 at 2:14 PM, Guido Falsi wrote: > Hi, > > I've just noticed a regression. > > I have been using mmc.ko, mmcsd.ko and sdhci.ko to use the integrated > SSD card reader on

Re: boot loaders got fatter in the last few days

2016-03-19 Thread Conrad Meyer
On Fri, Mar 18, 2016 at 10:03 AM, Allan Jude wrote: > On 2016-03-18 12:33, Guido Falsi wrote: >> >> Hi, >> >> I have just update one of my machines and noticed the booloaders files >> got quite fat in the last few days, some by a big margin. >> >> on an updated

Re: Could somebody just commit this patch: The new command line option to set the daemon(8) process title ?

2016-03-02 Thread Conrad Meyer
Committed in r296321, thanks! On Wed, Mar 2, 2016 at 11:02 AM, Yuri <y...@rawbw.com> wrote: > On 02/29/2016 15:05, Conrad Meyer wrote: >> >> I'd be happy to (+ manual page changes) if I don't hear any objection >> in the next few days. I would keep [pid] in the titl

Re: WLAN hardware not recognized

2016-03-01 Thread Conrad Meyer
"[1] iwn0: mem 0xf7b0-0xf7b01fff irq 18 at device 0.0 on pci3" is fine; "module iwn already present!" is fine. What makes you say it isn't recognized or doesn't work? On Tue, Mar 1, 2016 at 1:01 PM, Carsten Kunze <carsten.ku...@arcor.de> wrote: > Conrad M

  1   2   >