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),
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
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
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
>
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
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
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,
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
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) …
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
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
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
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
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
>
>
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
This is super cool, thank you! Is it feasible to integrate other
out-of-tree kmods in a similar way, e.g., nvidia-driver?
On Tue, Aug 13, 2019 at 2:58 PM John Baldwin wrote:
>
> With help from zeising@ in particular, I've just committed a change
> to the drm-current-kmod port that makes it
On Mon, Sep 9, 2019 at 8:25 PM Rebecca Cran wrote:
>
> Is building world with gcc still supported? I'm getting an error running
> the following:
>
> make XCC=/usr/local/bin/gcc9 XCXX=/usr/local/bin/g++9 buildworld
Hi Rebecca,
Aspirationally, yes. I did a successful CROSS_TOOLCHAIN=amd64-gcc
On Fri, Sep 13, 2019 at 11:37 AM Mark Johnston wrote:
>
> On Fri, Sep 13, 2019 at 02:12:56PM -0400, Ryan Stone wrote:
> > This gets me a little further but now the wait4 call by the parent
> > never reaps the child and instead blocks forever:
>
> Does it perform a wildcarded wait(), or does it
Thanks for the report Michael, and sorry about the breakage. I
believe this patch should fix the build, and I am testing it now:
--- sys/kern/kern_sysctl.c (revision 350714)
+++ sys/kern/kern_sysctl.c (working copy)
@@ -55,6 +55,7 @@
#include
#include
#include
+#include
This kinda just looks like ddb doesn't know how to disassemble crc32q?
Which might not be too surprising.
Note that it also truncates the qword constant in "add" at +167/+0xa7.
That one isn't corruption; just a DDB bug.
Can you print the faulting %rip and dump a few bytes at that address
in
Hi,
Did you run etcupdate or mergemaster as part of updating your host?
Best,
Conrad
On Sat, Nov 23, 2019 at 1:15 PM Yasuhiro KIMURA wrote:
>
> Hello,
>
> Yesterday I updated my 13-CURRENT host from r354592 to r355028 and
> /etc/os-release symbolic link wasn't created.
>
>
Isn’t rtld’s behavior here correct? It’s really Clang which is doing
something quite odd.
On Fri, Dec 20, 2019 at 13:27 Ryan Stone wrote:
> I've noticed that on head, if I directly execute rtld to run an
> executable, AT_EXECPATH contains the path to rtld on head (on
> 12.0-RELEASE it will
Hi Andrey,
Please try 'hint.hwpstate_intel.0.disabled="1"' as a workaround for now.
I think I have identified at least one problematic piece of code,
although I don't know if it's the root cause. I will go ahead and fix
that, which may not fix the hang, and also add some debug printfs that
can
Yep, amd is deprecated for 13.0:
https://svnweb.freebsd.org/base?view=revision=354902 ,
https://svnweb.freebsd.org/base?view=revision=354997 .
Conrad
On Mon, Feb 3, 2020 at 3:23 PM Bob Willcox wrote:
>
> Hi All,
>
> I've recently installed a 13.0 snapshot on one of my system to get some
>
cannot set or unset that hint from loader prompt;
>>
>> ok> set hint.hwpstate_intel.0.disabled="0"
>> ok> show
>>
>> hint.hwpstate=
>> ...
>>
>> Best regards
>> Andreas
>>
>> On Sat, Feb 1, 2020 at 11:26 PM Andreas
The step size of 1/8 degree C/K is documented in the public BKDG (prior to
17h) and PPR (17h+) documents available on AMD’s website, at least for
relatively recent models. I don’t know about very old models (really
anything older than 17h, although I’ve looked at the 15h docs some).
Best,
Conrad
On Tue, Mar 10, 2020 at 9:24 AM Theron wrote:
> I had previously used powerd to let the CPU underclock to 700MHz when
> idle. Now, I've lost all control over CPU frequency (either by powerd
> or by sysctl) since there is some in-kernel cpufreq driver which I can't
> figure out how to disable.
Hi Matthias,
From personal experience, receiving Zoom video in conferences with
native www/chromium and the web interface works perfectly fine and has
for some time (at least the last year). I think, but don't recall if
I personally tried it, that mic support is fine as well. Audio
playback is
Hi Grzegorz,
If you have another machine connected by network that you can install
and start netdumpd on, and; ipv4 configured on a supported network
device before the machine paniced; and a recent CURRENT; you should be
able to initiate a kernel dump over the network with 'netdump -s
server-ip'
Hi Shawn,
Is it possible to reproduce the issue on FreeBSD? The excerpt you've
linked to is not on FreeBSD.
Conrad
On Sun, Sep 20, 2020 at 5:53 PM Shawn Webb wrote:
>
> From latest HEAD on a Dell Precision 7550 laptop:
>
> https://gist.github.com/lattera/a0803f31f58bcf8ead51ac1ebbc447e2
>
>
The problem identified in Warner's email was fixed in r364030, so an
easy solution is updating from r363678 or earlier directly to r364030
or later.
Best,
Conrad
On Mon, Aug 10, 2020 at 3:20 AM Dennis Clarke wrote:
>
> On 8/5/20 9:19 PM, Warner Losh wrote:
> > If you are upgrading across
Sounds good to me. We don't need a RIP daemon in base, and if needed,
it is just a pkg install away via one of the myrriad maintained
routing daemons.
Thanks,
Conrad
On Sun, Jun 21, 2020 at 4:06 PM Alexander V. Chernikov
wrote:
>
> Hey,
>
> I would like to propose removal of sbin/routed and
r-x 1 root wheel 12 Jun 6 09:24 /dev/gpt/testingeli.eli -> ../md0s1.eli
https://reviews.freebsd.org/D25168
On Sat, Jun 6, 2020 at 8:52 AM Conrad Meyer wrote:
>
> Hi Xin Li,
>
> Thank you for the report and diagnosis. Sorry for the breakage.
>
> I have reverted the ch
time to revive my laptop. TL;DR: if you are
> using /dev/diskid or /dev/gptid labels and GELI, please wait until
> things settled.
>
> ===
>
> On 6/5/20 9:12 AM, Conrad Meyer wrote:
> > Author: cem
> > Date: Fri Jun 5 16:12:21 2020
> > New Revision: 361838
>
Hi Andriy,
Rand(3) is explicitly unsafe to use from concurrent threads without some
external serialization, even after initialization. I’d suggest using a
different API.
Best,
Conrad
On Wed, Dec 2, 2020 at 13:53 Andriy Gapon wrote:
>
> Specifically, concurrent "first" calls to rand().
> There
Hi Andriy,
On Wed, Dec 2, 2020 at 11:34 PM Andriy Gapon wrote:
>
> On 03/12/2020 01:20, Conrad Meyer wrote:
> > Rand(3) is explicitly unsafe to use from concurrent threads without some
> > external serialization, even after initialization. I’d suggest using a
> > diff
med "x-gitbrutec-nonce."
$ git cat-file -p 009
tree 4e778673b8af45ecd4c62e8b1d1438d06db7f440
parent 0080b4fc4c2066fa05641e73d5f0985c15ea
author Conrad Meyer 1590357489 -0700
committer Conrad Meyer 1590357489 -0700
x-gitbrutec-nonce YYZSKGIQCLLXGE
Use 'git update-ref' in post-co
Typo:
On Mon, Jan 4, 2021 at 5:25 PM Conrad Meyer wrote:
> SHA1 has always, by design, been vulnerable to a 2^80 resource attack :-).
2^160 for a specific hash. 2^80 if you're just trying to find any collision.
___
freebsd-current@freebsd.org mail
Hi Chuck,
In capability mode (capsicum sandbox), files like this need to be opened
before bhyve enters sandboxed mode. (That’s ‘cap_enter()’.)
Best,
Conrad
On Tue, Mar 2, 2021 at 09:31 Chuck Tuffli wrote:
> I'm porting some code to bhyve and am getting a failure I don't
> understand. This is
101 - 139 of 139 matches
Mail list logo
