/var/log/messages: "should not happen" "see local kernel hacker"

2020-01-13 Thread Evilham
Hello, I thought I'd finally ask about these messages that appear on boot on my machine. It's a Lenovo A485, with an AMD Ryzen laptop running CURRENT as of 8 hours ago, in case that's relevant. Are some of these actionable/would it make sense to take a deeper look or are they about something

Re: how to use the ktls

2020-01-13 Thread Rick Macklem
John Baldwin wrote: >On 1/12/20 8:23 PM, Benjamin Kaduk wrote: >> On Thu, Jan 09, 2020 at 10:53:38PM +, Rick Macklem wrote: >>> John Baldwin wrote: On 1/7/20 3:02 PM, Rick Macklem wrote: > Hi, > > Now that I've completed NFSv4.2 I'm on to the next project, which is > makin

Re: FreeBSD-head-amd64-test - Build #13912 (r356671) - Failure

2020-01-13 Thread Li-Wen Hsu
Thanks and all tests are good now: https://ci.freebsd.org/job/FreeBSD-head-i386-test/8056/ https://ci.freebsd.org/job/FreeBSD-head-amd64-test/13917/ On Mon, Jan 13, 2020 at 10:36 PM Mateusz Guzik wrote: > > Fixed in r356683. > > On 1/13/20, Mateusz Guzik wrote: > > On 1/13/20, Li-Wen Hsu wrote

spurious(?) userland malloc/mmap failure

2020-01-13 Thread Eric van Gyzen
While running head r356494, my buildworld just failed due to an apparently spurious userland malloc/mmap failure. ===> usr.bin/finger (all) objcopy: elf_update() failed: I/O error: Cannot allocate memory --- all_subdir_usr.bin/finger --- *** [all_subdir_usr.bin/finger] Error code 2 I ran 'make'

Re: how to use the ktls

2020-01-13 Thread John Baldwin
On 1/12/20 8:23 PM, Benjamin Kaduk wrote: > On Thu, Jan 09, 2020 at 10:53:38PM +, Rick Macklem wrote: >> John Baldwin wrote: >>> On 1/7/20 3:02 PM, Rick Macklem wrote: Hi, Now that I've completed NFSv4.2 I'm on to the next project, which is making NFS work over TLS. >>

Fast sigblock

2020-01-13 Thread Konstantin Belousov
https://reviews.freebsd.org/D12773 I intend to commit this in approximately week timeline. The overview of the feature is provided in the review summary above. Short story is, userspace can mask all maskable asynchronous signals with a single memory write, which allows to greatly speed up rtld for

Re: FreeBSD-head-amd64-test - Build #13912 (r356671) - Failure

2020-01-13 Thread Mateusz Guzik
Fixed in r356683. On 1/13/20, Mateusz Guzik wrote: > On 1/13/20, Li-Wen Hsu wrote: >> On Mon, Jan 13, 2020 at 1:10 PM wrote: >>> >>> FreeBSD-head-amd64-test - Build #13912 (r356671) - Failure >>> >>> Build information: >>> https://ci.freebsd.org/job/FreeBSD-head-amd64-test/13912/ >>> Full chang

Re: FreeBSD-head-amd64-test - Build #13912 (r356671) - Failure

2020-01-13 Thread Mateusz Guzik
On 1/13/20, Li-Wen Hsu wrote: > On Mon, Jan 13, 2020 at 1:10 PM wrote: >> >> FreeBSD-head-amd64-test - Build #13912 (r356671) - Failure >> >> Build information: >> https://ci.freebsd.org/job/FreeBSD-head-amd64-test/13912/ >> Full change log: >> https://ci.freebsd.org/job/FreeBSD-head-amd64-test/1

Re: FreeBSD-head-amd64-test - Build #13912 (r356671) - Failure

2020-01-13 Thread Li-Wen Hsu
On Mon, Jan 13, 2020 at 1:10 PM wrote: > > FreeBSD-head-amd64-test - Build #13912 (r356671) - Failure > > Build information: https://ci.freebsd.org/job/FreeBSD-head-amd64-test/13912/ > Full change log: > https://ci.freebsd.org/job/FreeBSD-head-amd64-test/13912/changes > Full build log: > https:/

Re: M_TEMP trouble in 13.0-CURRENT #0 r355131M

2020-01-13 Thread Poul-Henning Kamp
Just to conclude this: Whatever is in 13.0-CURRENT #1 r356602M has solved the problem. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately