On Wed, Jul 31, 2024 at 10:48:15AM -0400, John Baldwin wrote:
> On 7/31/24 08:15, void wrote:
> > Hi,
> >
> > Looking at man 4 aesni it appears this pertains to intel and AMD only?
> > is its prescence on arm64 a bug?
> >
> > It seems to be added to /boot/loader.conf by default.
> >
> > The meth
On Fri, Mar 29, 2024 at 04:52:55PM +0100, Alexander Leidinger wrote:
> Hi,
>
> sources from 2024-03-11 work. Sources from 2024-03-25 and today don't work
> (see below for the issue). As the monthly stabilisation pass didn't find
> obvious issues, it is something related to my setup:
> - not a gen
On Wed, Mar 06, 2024 at 10:51:05AM -0700, John Nielsen wrote:
> Getting a set but not used warning for “td” in sys/kern/kern_condvar.c when
> doing a buildkernel for a config file without “options KTRACE”. I failed to
> copy the full error message/line numbers but I will reproduce this evening if
On Wed, Feb 21, 2024 at 09:52:23AM +, hartmut.bra...@dlr.de wrote:
> Hi,
>
> I updated yesterday and now event a minimal program with
>
> cc -fsanitize=address
>
> produces
>
> ld: error: undefined symbol: __elf_aux_vector
> >>> referenced by sanitizer_linux_libcdep.cpp:950
> >>> (/usr/src
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
> and I've had two nvme-triggered panics in the last day.
>
> nvme is be
On Fri, Feb 09, 2024 at 10:11:14PM +, Matthew L. Dailey wrote:
> On 2/9/24 4:18 PM, Mark Johnston wrote:
> > [You don't often get email from ma...@freebsd.org. Learn why this is
> > important at https://aka.ms/LearnAboutSenderIdentification ]
> >
> > On Fri,
On Fri, Feb 09, 2024 at 06:23:08PM +, Matthew L. Dailey wrote:
> I had my first kernel panic with a KASAN kernel after only 01:27. This
> first panic was a "double fault," which isn't anything we've seen
> previously - usually we've seen trap 9 or trap 12, but sometimes others.
> Based on th
On Thu, Feb 08, 2024 at 03:34:52PM +, Matthew L. Dailey wrote:
> Good morning all,
>
> Per Rick Macklem's suggestion, I'm posting this query here in the hopes
> that other may have ideas.
>
> We did do some minimal testing with ufs around this problem back in
> August, but hadn't narrowed t
On Thu, Nov 16, 2023 at 10:21:38PM +, Bjoern A. Zeeb wrote:
> Hi,
>
> I seem to remember changes related to that a while ago but my cache
> is miss for the actual change. Are we suppoed to handle this case?
>
> It would be nice if "reset" would reset again the first time ...
We should perha
Yes. I've been traveling for the past couple of weeks and so haven't been
committing patches, but I'll be home tomorrow and plan to commit and merge
D41883.
On Mon., Sep. 25, 2023, 06:59 cglogic, wrote:
> Any chance that https://reviews.freebsd.org/D41883 will be merged into
> 14.0 before releas
On Mon, Sep 18, 2023 at 07:31:46AM +0200, Martin Matuska wrote:
> I vote for enabling block cloning on main :-)
Have you or anyone else run through the test suite with block cloning
enabled?
> On 16. 9. 2023 19:14, Alexander Motin wrote:
> > On 16.09.2023 01:25, Graham Perrin wrote:
> > > On 16/0
On Tue, Aug 29, 2023 at 07:08:35PM -0700, Cy Schubert wrote:
> Hi
>
> Just got the following panic on an and64 machine running poudriere building
> i386 packages.
>
> panic: vm_page_dequeue_deferred: page 0xfe000b222808 has unexpected
> queue state^M
> [...]
>
> uname reports,
>
> FreeBSD
On Mon, Aug 21, 2023 at 10:44:28AM -0700, Pete Wright wrote:
> hey there,
> i've got a kabylake laptop that i've been using with drm-kmod for several
> years without much hassle. after upgrading to a new CURRENT this weekend
> I've found that when loading either the 510 or 515 drm-kmod kernel modu
On Wed, Jun 21, 2023 at 11:53:44AM +0200, Peter Holm wrote:
> Just got this panic:
>
> 20230621 11:15:23 all (37/912): linux.sh
> panic: ASan: Invalid access, 1-byte read at 0xfe020bd78e9f,
> RedZonePartial(2)
> cpuid = 1
> time = 1687338930
> KDB: stack backtrace:
> db_trace_self_wrapper() a
On Wed, May 24, 2023 at 01:39:26PM +0200, Dimitry Andric wrote:
> On 24 May 2023, at 13:25, David Wolfskill wrote:
> >
> > This is from an in-place source update from main-n263073-634a770a5e16 to
> > main-n263112-ad513b4dba3e:
> >
> > ...
> > Building /common/S4/obj/usr/src/amd64.amd64/lib/libc/
On Sun, Apr 23, 2023 at 09:47:01PM +1000, Peter Jeremy wrote:
> Somewhere between c283016-g607bc91d90a3 and c283077-g7f658f99f7ed,
> some change in the kernel has made ntpd stop working on my arm64 test
> box. (My amd64 test box is a couple of days behind so I'm not sure if
> it's arm-specific).
>
On Sun, Apr 23, 2023 at 07:34:45AM -0500, Mike Karels wrote:
> On 23 Apr 2023, at 6:47, Peter Jeremy wrote:
>
> > Somewhere between c283016-g607bc91d90a3 and c283077-g7f658f99f7ed,
> > some change in the kernel has made ntpd stop working on my arm64 test
> > box. (My amd64 test box is a couple of
On Fri, Nov 18, 2022 at 05:47:58AM +0100, Hans Petter Selasky wrote:
> Hi,
>
> I'm doing some work with audio and have noticed some problems with the
> ULE scheduler. I have a program that generate audio based on
> key-presses. When no keys are pressed, the load is near 0%, but as soon
> as you
On Fri, Sep 23, 2022 at 09:46:08AM -0700, Steve Kargl wrote:
> On Thu, Sep 22, 2022 at 03:00:53PM -0400, Mark Johnston wrote:
> >
> > I think this untested patch will address the panics. The bug was there
> > for a long time but some recent restructuring added an assertio
On Thu, Sep 22, 2022 at 11:31:40AM -0700, Steve Kargl wrote:
> All,
>
> I updated my kernel/world/all ports on Sept 19 2022.
> Since then, I have had daily panics and hard lock-up
> (no panic, keyboard, mouse, network, ...). The one
> panic I did witness sent text scolling off the screen.
> There
On Mon, Sep 05, 2022 at 08:41:58AM -0600, Alan Somers wrote:
> On Sat, Sep 3, 2022 at 11:10 PM Konstantin Belousov
> wrote:
> >
> > On Sat, Sep 03, 2022 at 10:19:12AM -0600, Alan Somers wrote:
> > > Our /usr/include headers define a lot of symbols that are used by
> > > critical utilities in the
On Sun, Jul 24, 2022 at 10:07:19AM -0700, Cy Schubert wrote:
> In message <20220724030857.b57f...@slippy.cwsent.com>, Cy Schubert writes:
> > In message <20220723185533.9ea7d...@slippy.cwsent.com>, Cy Schubert writes:
> > > In message , Mark Johnston writes:
> &g
On Sat, Jul 23, 2022 at 07:14:44AM -0700, Cy Schubert wrote:
> In message <20220723035223.57cd...@slippy.cwsent.com>, Cy Schubert writes:
> > I'm not sure if this is because my obj tree needs a fresh rebuild and
> > reinstall or if this is a legitimate problem. Regardless of the dtrace
> > comman
On Fri, Jul 15, 2022 at 05:26:09PM -0500, Larry Rosenman wrote:
> On 07/15/2022 5:24 pm, Mark Johnston wrote:
> > On Fri, Jul 15, 2022 at 05:21:27PM -0500, Larry Rosenman wrote:
> >> On 07/15/2022 5:18 pm, Mark Johnston wrote:
> >> > On Fri, Jul 15, 2022 at 05:04:18
On Fri, Jul 15, 2022 at 05:21:27PM -0500, Larry Rosenman wrote:
> On 07/15/2022 5:18 pm, Mark Johnston wrote:
> > On Fri, Jul 15, 2022 at 05:04:18PM -0500, Larry Rosenman wrote:
> >> I'm using the following kernel config:
> >> [...]
> >> and the followi
On Fri, Jul 15, 2022 at 05:04:18PM -0500, Larry Rosenman wrote:
> I'm using the following kernel config:
> [...]
> and the following login.conf:
> [...]
> bacula_dir:\
> :stacksize-max=68719476736:\
> :stacksize-cur=68719476736:\
> :tc=daemon:
> [...]
> I've updated my (ler) passw
On Thu, Jun 09, 2022 at 07:49:53PM +, Rick Macklem wrote:
> Mark Johnston wrote:
> >
> > On Thu, Jun 09, 2022 at 07:30:47PM +, Rick Macklem wrote:
> > > I just tried to MFC a commit done to fix my commit by imp@
> > > and it won't let be push the che
On Thu, Jun 09, 2022 at 07:30:47PM +, Rick Macklem wrote:
> I just tried to MFC a commit done to fix my commit by imp@
> and it won't let be push the cherry-pick.
>
> What's the trick to doing this?
You need to add --push-option=confirm-author to the git push invocation.
> Or do I need to ge
ter/src/logerr.c#L187
>
> 3. next event received, vfprintf is called on stderr and crashes
> https://github.com/NetworkConfiguration/dhcpcd/blob/master/src/logerr.c#L186
>
>
> Simple program that eventually crashes:
Thanks for the reproducer. The bug is akin to that fixed
On Mon, Mar 07, 2022 at 09:54:26PM +0100, Ronald Klop wrote:
>
> Van: Mark Johnston
> Datum: maandag, 7 maart 2022 16:13
> Aan: Ronald Klop
> CC: bob prohaska , Mark Millard ,
> freebsd-...@freebsd.org, freebsd-current
> > I haven't been able to reproduce any cr
On Mon, Mar 07, 2022 at 10:03:51AM -0800, Mark Millard wrote:
>
>
> On 2022-Mar-7, at 08:45, Mark Johnston wrote:
>
> > On Mon, Mar 07, 2022 at 04:25:22PM +, Andrew Turner wrote:
> >>
> >>> On 7 Mar 2022, at 15:13, Mark Johnston wrote:
>
On Mon, Mar 07, 2022 at 04:25:22PM +, Andrew Turner wrote:
>
> > On 7 Mar 2022, at 15:13, Mark Johnston wrote:
> > ...
> > A (the?) problem is that the compiler is treating "pc" as an alias
> > for x18, but the rmlock code assumes that the pcpu pointer i
On Mon, Mar 07, 2022 at 02:46:09PM +0100, Ronald Klop wrote:
> Dear Mark Johnston,
>
> I did some binary search in the kernels and came to the conclusion that
> https://cgit.freebsd.org/src/commit/?id=1517b8d5a7f58897200497811de1b18809c07d3e
> still works and
> https://cg
On Sun, Feb 27, 2022 at 01:16:44PM -0600, Larry Rosenman wrote:
> On 02/26/2022 11:08 am, Larry Rosenman wrote:
> > On 02/26/2022 10:57 am, Larry Rosenman wrote:
> >> On 02/26/2022 10:37 am, Juraj Lutter wrote:
> On 26 Feb 2022, at 03:03, Larry Rosenman wrote:
> I'm running this script:
On Fri, Jan 14, 2022 at 09:38:56PM -0800, Mark Millard wrote:
> Thanks. This will allow me to remove part of my personal additions
> in this area --and my having to explain the misnomer when trying
> to help someone analyze why they end up with OOM activity so they
> can figure out what to do about
On Thu, Jan 06, 2022 at 03:06:14PM +0100, FreeBSD User wrote:
> With mergin a recent commit today involving /usr/src/sys/x86/x86/tsc.c of
> FreeBSD
> 13-STABLE, compiling the kernel results in the error shown below:
>
> [...]
> cc -target x86_64-unknown-freebsd13.0
> --sysroot=/usr/obj/usr/src/a
On Fri, Dec 10, 2021 at 10:43:19AM -0600, Larry Rosenman wrote:
> 14-2021_12_07-1217 - - 1.87G 2021-12-07 12:17
> 14-2021_12_09-1957 NR / 121G 2021-12-09 19:57
>
> If that's any help
I can't tell what this is saying. A kernel built on the 7th d
On Fri, Dec 10, 2021 at 06:35:47PM +0100, Marcin Wojtas wrote:
> Hi Daniel
>
>
> pt., 10 gru 2021 o 10:16 Daniel O'Connor napisał(a):
> >
> >
> >
> > > On 17 Nov 2021, at 09:00, Marcin Wojtas wrote:
> > > As of b014e0f15bc7 the ASLR (Address Space Layout
> > > Randomization) feature becomes ena
On Thu, Dec 09, 2021 at 07:37:18PM +0100, Kirill Ponomarev wrote:
> On 12/08, Mark Johnston wrote:
> > On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote:
> > > Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD
> > > 14.0-CURRENT
> > &
On Thu, Dec 09, 2021 at 10:20:10AM -0500, Shawn Webb wrote:
> Hey all,
>
> It looks like there's a potential deadlock in some networking code,
> specifically with ipv4 jails. I can reproduce by running Poudriere on
> 14-CURRENT.
>
> I am using HardenedBSD 14-CURRENT, but we don't have any changes
On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote:
> Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD 14.0-CURRENT
> #7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET 2021 amd64) fails with
> the
> linker error shown below.
>
> Due to this error, no FreeBSD pkg base
On Mon, Nov 29, 2021 at 06:45:19PM -0800, Mark Millard via freebsd-arm wrote:
> For:
>
> uname -apKU
> FreeBSD CA72_4c8G_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #22
> main-n250972-319e9fc642a1-dirty: Tue Nov 23 12:25:36 PST 2021
> root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/ma
On Fri, Nov 26, 2021 at 02:48:03PM -0500, Mark Johnston wrote:
> On Fri, Nov 26, 2021 at 02:00:27PM -0500, Mark Johnston wrote:
> > On Fri, Nov 26, 2021 at 06:12:49PM +0200, Andriy Gapon wrote:
> > > On 26/11/2021 18:06, Mark Johnston wrote:
> > > > On Thu, Nov 25, 20
On Fri, Nov 26, 2021 at 02:00:27PM -0500, Mark Johnston wrote:
> On Fri, Nov 26, 2021 at 06:12:49PM +0200, Andriy Gapon wrote:
> > On 26/11/2021 18:06, Mark Johnston wrote:
> > > On Thu, Nov 25, 2021 at 10:48:36PM +0200, Andriy Gapon wrote:
> > >>
> > >>
On Fri, Nov 26, 2021 at 06:12:49PM +0200, Andriy Gapon wrote:
> On 26/11/2021 18:06, Mark Johnston wrote:
> > On Thu, Nov 25, 2021 at 10:48:36PM +0200, Andriy Gapon wrote:
> >>
> >> I've just finished builds of yesterday's CURRENT / main for arm and arm
On Thu, Nov 25, 2021 at 10:48:36PM +0200, Andriy Gapon wrote:
>
> I've just finished builds of yesterday's CURRENT / main for arm and arm64.
> In both builds I got lots of messages from ctfconvert:
>ctfconvert: rc = 1 Unsupported version [_dwarf_info_load(229)]
>
> I got an impression that th
On Fri, Nov 12, 2021 at 09:04:47PM +0100, Herbert J. Skuhra wrote:
> On Fri, 12 Nov 2021 20:22:38 +0100, "Herbert J. Skuhra" wrote:
> >
> > Hi!
> >
> > # uname -rms
> > FreeBSD 12.2-RELEASE-p10 amd64
> >
> > # cd tmp
> > # fetch
> > https://download.freebsd.org/ftp/releases/amd64/13.0-RELEASE/b
On Mon, Oct 25, 2021 at 11:46:49AM -0400, Michael Butler via freebsd-current
wrote:
> This seems to have gone away after
> https://freshbsd.org/freebsd/src/commit/70f51f0e474ffe1fb74cb427423a2fba3637544d
>
> Not sure if the bug that commit fixes was the underlying cause,
Yes, that commit fixes
On Tue, Oct 12, 2021 at 08:39:55PM +0200, Peter Eriksson wrote:
> I just noticed that a couple of my 12.2-RELEASE-p4 running servers have…
> 8263, 14474 and 3831 defunct subprocesses from syslogd and also seems to have
> stopped writing to the log files… When I tried to kill syslogd on a fourth
On Thu., Oct. 7, 2021, 17:11 Konstantin Belousov,
wrote:
> On Thu, Oct 07, 2021 at 04:52:52PM -0400, Mark Johnston wrote:
> > On Thu, Oct 07, 2021 at 04:18:28PM -0400, Michael Butler via
> freebsd-current wrote:
> > > On 10/7/21 15:39, Konstantin Belousov wrote:
> >
On Thu, Oct 07, 2021 at 04:18:28PM -0400, Michael Butler via freebsd-current
wrote:
> On 10/7/21 15:39, Konstantin Belousov wrote:
> > On Thu, Oct 07, 2021 at 03:28:44PM -0400, Michael Butler via
> > freebsd-current wrote:
> >> While building a local release bundle, I sometimes get bsdtar failing
On Thu, Aug 05, 2021 at 10:54:19AM -0500, Alan Somers wrote:
> There's this:
> https://openzfs.github.io/openzfs-docs/man/8/zpool-reguid.8.html . I
> haven't used it myself.
Would it be useful to have an rc.d script that can run this, probably
just on the root pool? It could be configured to run
On Fri, Aug 27, 2021 at 05:29:34PM +0200, Tijl Coosemans wrote:
> On Fri, 27 Aug 2021 17:24:58 +0300 Konstantin Belousov
> wrote:
> > On Fri, Aug 27, 2021 at 03:41:30PM +0200, Tijl Coosemans wrote:
> >> I use devel/llvm* to build base and just switched to llvm12. It seems
> >> that on i386 clang12
On Tue, Jul 20, 2021 at 10:13:20AM -0700, Steve Kargl wrote:
> On Tue, Jul 20, 2021 at 12:15:58PM -0400, Mark Johnston wrote:
> > On Tue, Jul 20, 2021 at 09:07:04AM -0700, Steve Kargl wrote:
> > > On Mon, Jul 19, 2021 at 07:05:03PM -0700, Steve Kargl wrote:
> > > >
On Tue, Jul 20, 2021 at 09:07:04AM -0700, Steve Kargl wrote:
> On Mon, Jul 19, 2021 at 07:05:03PM -0700, Steve Kargl wrote:
> > On Mon, Jul 19, 2021 at 07:55:07PM -0400, Mark Johnston wrote:
> > > On Mon, Jul 19, 2021 at 03:02:19PM -0700, Steve Kargl wrote:
> > > >
On Mon, Jul 19, 2021 at 03:02:19PM -0700, Steve Kargl wrote:
> While reading files from a UDF filesystem, I
> received the following panic. I have the core
> file and kernel if anyone is interested.
>
>
> Unread portion of the kernel message buffer:
> panic: vm_domainset_iter_first: Unknown pol
On Wed, Jun 16, 2021 at 10:16:56PM -0700, Neel Chauhan wrote:
> Hi Mark,
>
> Thank you so much for your response!
>
> On 2021-06-16 14:05, Mark Johnston wrote:
> >
> > The function in question appears to implement a device page fault
> > handler. In FreeBSD, s
On Tue, Jun 15, 2021 at 08:36:07PM -0700, Neel Chauhan wrote:
> Hi current@,
>
> First off, sorry if I spammed developers@ and other mailing lists with
> my previous message, and to bz@/hselasky@/manu@ sent so many duplicate
> emails.
>
> Right now, I am attempting to update the drm-kmod driver
On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jennejohn wrote:
> I've seen this panic three times in the last two days:
>
> [first panic]
> Unread portion of the kernel message buffer:
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 3; apic id = 03
> fault virtual address = 0x8
On Wed, Apr 14, 2021 at 02:21:44PM +0300, Andriy Gapon wrote:
> On 14/04/2021 00:18, Mark Johnston wrote:
> > fbt::vm_page_unwire:entry
> > /args[0]->oflags & 0x4/
> > {
> > @unwire[stack()] = count();
> > }
>
> Unrelated report, dtrace com
On Tue, Apr 13, 2021 at 05:01:49PM +0300, Andriy Gapon wrote:
> On 07/04/2021 23:56, Mark Johnston wrote:
> > I don't know what might be causing it then. It could be a page leak.
> > The kernel allocates wired pages without adjusting the v_wire_count
> > counter in some
On Wed, Apr 07, 2021 at 11:22:41PM +0300, Andriy Gapon wrote:
> On 07/04/2021 22:54, Mark Johnston wrote:
> > On Wed, Apr 07, 2021 at 10:42:57PM +0300, Andriy Gapon wrote:
> >>
> >> I regularly see that the top's memory line does not add up (and by a lot).
> &
On Wed, Apr 07, 2021 at 10:42:57PM +0300, Andriy Gapon wrote:
>
> I regularly see that the top's memory line does not add up (and by a lot).
> That can be seen with vm.stats as well.
>
> For example:
> $ sysctl vm.stats | fgrep count
> vm.stats.vm.v_cache_count: 0
> vm.stats.vm.v_user_wire_count:
On Thu, Mar 11, 2021 at 06:32:13PM +0100, Peter Holm wrote:
> I just got this panic:
>
> panic: malloc(M_WAITOK) with sleeping prohibited
> cpuid = 0
> time = 1615472733
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00e49748b0
> vpanic() at vpanic+0x
On Tue, Mar 02, 2021 at 09:31:22AM -0800, Chuck Tuffli wrote:
> I'm porting some code to bhyve and am getting a failure I don't
> understand. This is git as of af11c2029006 FWIW.
>
> The code in question is for an emulated device and looks like:
> dbg = fopen("/tmp/bhyve_ata.log", "w+");
>
On Sat, Jan 23, 2021 at 03:25:59PM +, Rick Macklem wrote:
> Ronald Klop wrote:
> >On Wed, 20 Jan 2021 21:21:15 +0100, Neel Chauhan wrote:
> >
> >> Hi freebsd-current@,
> >>
> >> I know that In-Kernel TLS was merged into the FreeBSD HEAD tree a while
> >> back.
> >>
> >> With 13.0-RELEASE aroun
On Wed, Jan 20, 2021 at 03:12:27PM +0200, Konstantin Belousov wrote:
> On Wed, Jan 20, 2021 at 01:56:57PM +0100, Rainer Hurling wrote:
> > Am 20.01.21 um 13:34 schrieb Konstantin Belousov:
> > > On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote:
> > >> Am 20.01.21 um 11:18 schrieb Kons
emory shortage which
could be responsible for UMA allocation failures.
>
> On 1/20/21 2:30 PM, Mark Johnston wrote:
> > On Wed, Jan 20, 2021 at 02:24:59PM +, Santiago Martinez wrote:
> >> Hi Mark,
> >>
> >> To the DRM question, indeed I am using drm-devel
On Wed, Jan 20, 2021 at 02:24:59PM +, Santiago Martinez wrote:
> Hi Mark,
>
> To the DRM question, indeed I am using drm-devel with amdgpu.
Have you updated to commit 4af932354260 or later? That helps address a
memory reclamation bug triggered by amdgpu.
> Here is the vmstat -s output.
I g
On Tue, Jan 19, 2021 at 12:44:14PM +, Santiago Martinez wrote:
> Hi there, sorry to ask this as it might be a silly question...
>
> Since a few weeks im seeing random locks on application and sometimes
> when using truss it show resource temporally unavailable.
>
> Now, checking random things,
On Tue, Dec 08, 2020 at 04:40:16PM +0100, Mateusz Guzik wrote:
> I think this is a long standing bug against exiting processes.
>
> filedesc_out only increments *hold* count, but that does not prevent
> fdescfree_fds from progressing and freeing everything without any
> locks held.
I think it is
On Tue, Dec 08, 2020 at 09:39:05AM -0600, Kyle Evans wrote:
> On Tue, Dec 8, 2020 at 9:30 AM Mark Johnston wrote:
> > kern_proc_filedesc_out() holds the fdtable shared lock thoughout all of
> > this, which is supposed to prevent the table entry from being freed
> > si
On Tue, Dec 08, 2020 at 12:47:18PM +0100, Peter Holm wrote:
> I just got this panic:
>
> Fatal trap 9: general protection fault while in kernel mode
> cpuid = 9; apic id = 09
> instruction pointer = 0x20:0x80bc6e22
> stack pointer = 0x28:0xfe0698887630
> frame pointer =
On Thu, Dec 03, 2020 at 03:42:40PM -0800, Chuck Tuffli wrote:
> On Thu, Dec 3, 2020 at 3:18 PM Mark Johnston wrote:
> >
> > On Thu, Dec 03, 2020 at 01:08:52PM -0800, Chuck Tuffli wrote:
> > > Hi
> > >
> > > I'm trying to fix the build of qemu-util
On Thu, Dec 03, 2020 at 01:08:52PM -0800, Chuck Tuffli wrote:
> Hi
>
> I'm trying to fix the build of qemu-utils but am seeing failures on
> CURRENT (13.0-HEAD-9e082d278b9) like:
>
> In file included from util/oslib-posix.c:50:
> In file included from /usr/include/sys/user.h:51:
> In file include
On Mon, Nov 30, 2020 at 03:50:53PM +0200, Andriy Gapon wrote:
> On 19/11/2020 16:57, Mark Johnston wrote:
> > On Thu, Nov 19, 2020 at 01:28:56PM +0200, Andriy Gapon wrote:
> >>
> >> what do people think about adding
> >> setlocale(LC_NUMERIC, "");
On Thu, Nov 19, 2020 at 01:28:56PM +0200, Andriy Gapon wrote:
>
> what do people think about adding
> setlocale(LC_NUMERIC, "");
> to dtrace's main function?
That seems reasonable to me.
> My primary interest is to (pretty-)print some numbers with a thousands
> separator.
>
> Not sure if a
On Tue, Nov 17, 2020 at 08:19:12PM +0200, Konstantin Belousov wrote:
> On Tue, Nov 17, 2020 at 06:20:31PM +0100, Johan Hendriks wrote:
> > Hello all after updating FreeBSD13 from r367724 to r367755 my samba server
> > craches the server.
> > I did rebuild samba 4.11 but that does not help.
> >
> >
Hi,
df(1) has the ability to mount character devices in order to collect
usage information. This functionality has been deprecated for the past
couple of years, since r329092, and is buggy per PR 237368. I propose
removing it in 13.0: https://reviews.freebsd.org/D27197
__
On Fri, Oct 23, 2020 at 06:32:25PM +0200, Michal Meloun wrote:
>
>
> On 19.10.2020 22:39, Mark Johnston wrote:
> > On Fri, Oct 16, 2020 at 11:53:56AM +0200, Michal Meloun wrote:
> >>
> >>
> >> On 06.10.2020 15:37, Mark Johnston wrote:
> >>>
On Tue, Oct 20, 2020 at 11:55:30AM -0700, bob prohaska wrote:
> On Tue, Oct 20, 2020 at 12:30:05PM -0400, Mark Johnston wrote:
> >
> > I set up a RPi3 to try and repro this and have so far managed to trigger
> > it once using Peter Holm's stress2 suite, so I'll ke
On Mon, Oct 19, 2020 at 04:09:09PM -0700, bob prohaska wrote:
> On Mon, Oct 19, 2020 at 04:39:54PM -0400, Mark Johnston wrote:
> >
> > I think vmspace_exit() should issue a release fence with the cmpset and
> > an acquire fence when handling the refcnt == 1 case, but I d
On Fri, Oct 16, 2020 at 11:53:56AM +0200, Michal Meloun wrote:
>
>
> On 06.10.2020 15:37, Mark Johnston wrote:
> > On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote:
> >> Still seeing non-current pmap panics on the Pi3, this time a B+ running
> >>
On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote:
> Still seeing non-current pmap panics on the Pi3, this time a B+ running
> 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master)
> during a -j4 buildworld. The backtrace reports
>
> panic: non-current pmap 0xa00020eab8f0
C
On Tue, Sep 29, 2020 at 04:35:47PM +0300, Michael Zhilin wrote:
> Thank you, Kostya and Mark!
> I will update to head. :)
Be sure to pick up r366252 or later: there is a related bug in the
initial OpenZFS import that is fixed by that revision.
> On Tue, Sep 29, 2020 at 4:32 PM Mark
On Tue, Sep 29, 2020 at 04:20:26PM +0300, Konstantin Belousov wrote:
> On Tue, Sep 29, 2020 at 02:59:43PM +0300, Michael Zhilin wrote:
> > Hi,
> >
> > I'm using FreeBSD 13-CURRENT (pre-ZoF, r359724) on my laptop with installed
> > Gnome. Sometimes
> > (once a week/month) gnome hangs and the system
On Tue, Sep 22, 2020 at 06:51:28PM -0400, Mark Johnston wrote:
> On Tue, Sep 22, 2020 at 01:13:29AM +0300, Konstantin Belousov wrote:
> > On Mon, Sep 21, 2020 at 08:57:46PM +0200, Rainer Hurling wrote:
> > > Fatal trap 12: page fault while in kernel mode
> > > cpuid = 3
On Tue, Sep 22, 2020 at 01:13:29AM +0300, Konstantin Belousov wrote:
> On Mon, Sep 21, 2020 at 08:57:46PM +0200, Rainer Hurling wrote:
> > Fatal trap 12: page fault while in kernel mode
> > cpuid = 31; apic id = 1f
> > fault virtual address = 0x25407efa
> This address is very suspicious.
>
> I c
On Tue, Sep 08, 2020 at 07:24:38PM +0200, Guido Falsi wrote:
> On 08/09/20 10:01, Guido Falsi wrote:
> > Hi,
> >
> > I'm trying to update to recent head, but I can't boot my system with the
> > compiled kernel.
> >
> > The system has ZFS on root and was working with previous kernel (before
> > Op
On Fri, Sep 04, 2020 at 09:41:56PM +0300, Ruslan Makhmatkhanov wrote:
> Mark Johnston wrote on 9/4/20 9:34 PM:
> > On Fri, Sep 04, 2020 at 09:27:54PM +0300, Ruslan Makhmatkhanov wrote:
> >> Hello,
> >>
> >> tried to make world and kernel from r365296. Kerne
On Fri, Sep 04, 2020 at 09:27:54PM +0300, Ruslan Makhmatkhanov wrote:
> Hello,
>
> tried to make world and kernel from r365296. Kernel fails at install
> stage in zfs module:
>
> ===> zfs (install)
> install -T release -o root -g wheel -m 555 zfs.ko /boot/kernel/
> install -T dbg -o root -g wh
On Tue, Aug 18, 2020 at 03:55:15PM +0200, Mateusz Guzik wrote:
> On 8/18/20, Mark Johnston wrote:
> > On Tue, Aug 18, 2020 at 03:24:52PM +0200, Mateusz Guzik wrote:
> >> Try this:
> >>
> >> diff --git a/sys/kern/kern_malloc.c b/sys/kern/kern_malloc.c
> &
On Tue, Aug 18, 2020 at 03:24:52PM +0200, Mateusz Guzik wrote:
> Try this:
>
> diff --git a/sys/kern/kern_malloc.c b/sys/kern/kern_malloc.c
> index 46eb1c4347c..7b94ca7b880 100644
> --- a/sys/kern/kern_malloc.c
> +++ b/sys/kern/kern_malloc.c
> @@ -618,8 +618,8 @@ void *
> unsigned long osi
he new test per
my comments in the review.
> -Alan
>
> On Tue, Jul 7, 2020 at 4:24 PM Mark Johnston wrote:
>
> > On Tue, Jul 07, 2020 at 03:18:02PM -0600, alan somers wrote:
> > > I'm working on a change to geli, but I need to test it on a system with a
&g
On Tue, Jul 07, 2020 at 03:18:02PM -0600, alan somers wrote:
> I'm working on a change to geli, but I need to test it on a system with a
> hardware crypto card. Not merely one with AES-NI, but one of the old
> fashioned PCI kind that works with crypto(9). Would anybody who runs
> CURRENT on such
On Thu, Jun 11, 2020 at 10:08:08AM -0700, David Wolfskill wrote:
> On Thu, Jun 11, 2020 at 07:44:21PM +0300, Konstantin Belousov wrote:
> > ...
> > This should fix noexec for modules.
> >
> > diff --git a/sys/x86/x86/mp_x86.c b/sys/x86/x86/mp_x86.c
> > index 81db4d7ca85..cb84fc95691 100644
> > ---
On Thu, Jun 11, 2020 at 09:11:56AM -0700, David Wolfskill wrote:
> On Thu, Jun 11, 2020 at 06:51:43PM +0300, Konstantin Belousov wrote:
> > ...
> > Can you boot into single-user, without loading linux/cuse/nvidia modules.
> > Even, do not load any module at all, and keeping root ro.
> >
> > If boo
On Thu, Jun 11, 2020 at 06:29:24AM -0700, David Wolfskill wrote:
> On Thu, Jun 11, 2020 at 04:21:29PM +0300, Konstantin Belousov wrote:
> > ...
> > The link times out.
>
> Sigh. Sorry about that; I have copied the images to
> freefall:~dhw/head/r362045/ .
>
> > There is not much to access in fut
On Wed, Jun 10, 2020 at 06:41:50PM +0200, Michael Tuexen wrote:
> Dear all,
>
> consider the following program test.c:
>
> #include
> #include
>
> int
> main(void)
> {
> void *p;
>
> p = mmap((void *)0x2000, 0x100, PROT_READ | PROT_WRITE |
> PROT_EXEC, MAP_ANON | M
On Thu, May 14, 2020 at 02:16:15PM +0300, Andriy Gapon wrote:
> On 13/05/2020 17:42, Mark Johnston wrote:
> > On Wed, May 13, 2020 at 10:45:24AM +0300, Andriy Gapon wrote:
> >> On 13/05/2020 10:35, Andriy Gapon wrote:
> >>> In r329363 I re-worked zfs_getpages and
1 - 100 of 292 matches
Mail list logo
