Hyper-V Gen2 VM, 8 cores, 8GB RAM. The panic is reproducible while
running `make -j8 buildworld`. Initially installed from
FreeBSD-15.0-CURRENT-amd64-20240926-6a4f0c063718-272495-disc1.iso,
updating the kernel (that I could build) to b35f0aa4952 does not help.
panic: curthread not pinned
cpuid =
Has anything changed in the past two months that might cause wake to
become unreliable?
nvidia-driver-470, if that's relevant. Built from source.
HP ZBook 17 G2.
IIRC the unreliability became noticeable not long after the bump to
1500023. That was around the end of August (with pkgbase).
Pr
On 9/30/24 19:36, Jamie Landeg-Jones wrote:
Kyle Evans wrote:
It might be that the better long-term approach is to teach updatedb.sh
how to drop privileges and push that out of the periodic script to avoid
surprises like this from the different execution environments. This
/feels/ like the ki
Kyle Evans wrote:
> It might be that the better long-term approach is to teach updatedb.sh
> how to drop privileges and push that out of the periodic script to avoid
> surprises like this from the different execution environments. This
> /feels/ like the kind of thing we could take an opinion
On Wed, Aug 21, 2024 at 8:02 AM Matthew L. Dailey
wrote:
>
> Hi Rick,
>
> Done - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280978
Just fyi for everyone, the bugzilla PR now has a patch that has been
committed to main as eb345e05ac66. Early indications are that it
fixes the race that was c
On 9/30/24 16:28, void wrote:
On Mon, Sep 30, 2024 at 02:08:18PM -0700, Gleb Smirnoff wrote:
M> > Manual run of the periodic job doesn't reproduce the problem :(
M>
M> Backing out commit f62c1f3f8e91c78d402e1db4e518e4899a4ba2b9
resolves it for
M> me,
Sorry but I'm quite dense regarding git.
On Mon, Sep 30, 2024 at 02:08:18PM -0700, Gleb Smirnoff wrote:
M> > Manual run of the periodic job doesn't reproduce the problem :(
M>
M> Backing out commit f62c1f3f8e91c78d402e1db4e518e4899a4ba2b9 resolves it for
M> me,
Sorry but I'm quite dense regarding git. Can you describe how exactly
wha
On Mon, Sep 30, 2024 at 02:25:49PM -0400, Michael Butler wrote:
M> On 9/30/24 14:11, Gleb Smirnoff wrote:
M> > On Sat, Sep 28, 2024 at 11:10:57PM +0100, void wrote:
M> > v> I have found that *only* on arm64, locate errors like so:
M> > v>
M> > v> # sh /etc/periodic/weekly/310.locate
M> > v>
M> > v>
On 9/30/24 14:11, Gleb Smirnoff wrote:
On Sat, Sep 28, 2024 at 11:10:57PM +0100, void wrote:
v> I have found that *only* on arm64, locate errors like so:
v>
v> # sh /etc/periodic/weekly/310.locate
v>
v> Rebuilding locate database:
v> install: /var/db/INS@ArwCNx: Permission denied
v>
v> However, i
On Sat, Sep 28, 2024 at 11:10:57PM +0100, void wrote:
v> I have found that *only* on arm64, locate errors like so:
v>
v> # sh /etc/periodic/weekly/310.locate
v>
v> Rebuilding locate database:
v> install: /var/db/INS@ArwCNx: Permission denied
v>
v> However, if it's run like this:
v>
v> # sh /usr
10 matches
Mail list logo
