On Sat, Mar 2, 2024 at 7:06 AM Filippo Moretti
wrote:
> -- intel_virtual_output-virtual.o ---
> virtual.c:499:11: error: use of undeclared identifier 'ETIME'
> 499 | return -ETIME;
> | ^
> virtual.c:506:11: error: use of undeclared identifier 'ETIME
Thank you for your explanation,my computer is an old core duo but X is working
anyway even with my older build.SincerelyFilippo
On Sunday, March 3, 2024 at 04:38:32 PM GMT+1, Kevin Oberman
wrote:
On Sat, Mar 2, 2024 at 7:06 AM Filippo Moretti wrote:
-- intel_virtual_output-virtual.o
Hi everyone,
I tried compiling releng/13.2 on a fresh stable/13. That fails with:
--- _bootstrap-tools-usr.sbin/zic ---
/scratch/20240303_162512/stage/usr/src/contrib/tzcode/zic.c:464:8:
error: an attribute list cannot appear here
464 | static ATTRIBUTE_NORETURN void
|^
On Sat, Mar 2, 2024 at 9:25 PM Garrett Wollman wrote:
>
> <
> > I believe this explains why vn_copy_file_range sometimes takes much
> > longer than a second: our servers often have lots of data waiting to
> > be written to disk, and if the file being copied was recently modified
> > (and so is dir
On Sat, Mar 2, 2024 at 8:28 PM Garrett Wollman wrote:
>
>
> I wrote previously:
> > PIDTID COMMTDNAME KSTACK
> > 997 108481 nfsdnfsd: mastermi_switch
> > sleepq_timedwait _sleep nfsv4_lock nfsrvd_dorpc nfssvc_program
> > svc_run_internal s
On Sun, Mar 3, 2024 at 1:17 PM Rick Macklem wrote:
>
> On Sat, Mar 2, 2024 at 8:28 PM Garrett Wollman wrote:
> >
> >
> > I wrote previously:
> > > PIDTID COMMTDNAME KSTACK
> > > 997 108481 nfsdnfsd: mastermi_switch
> > > sleepq_timedwait _
On Sun, Mar 3, 2024 at 3:27 PM Rick Macklem wrote:
>
> On Sun, Mar 3, 2024 at 1:17 PM Rick Macklem wrote:
> >
> > On Sat, Mar 2, 2024 at 8:28 PM Garrett Wollman
> > wrote:
> > >
> > >
> > > I wrote previously:
> > > > PIDTID COMMTDNAME KSTACK
> > > > 997 108481
On Sun, Mar 3, 2024 at 4:28 PM Rick Macklem wrote:
>
> On Sun, Mar 3, 2024 at 3:27 PM Rick Macklem wrote:
> >
> > On Sun, Mar 3, 2024 at 1:17 PM Rick Macklem wrote:
> > >
> > > On Sat, Mar 2, 2024 at 8:28 PM Garrett Wollman
> > > wrote:
> > > >
> > > >
> > > > I wrote previously:
> > > > > PID
< said:
>> [I wrote:]
>> (and so is dirty), this might take several seconds. I've set
>> vfs.zfs.dmu_offset_next_sync=0 on the server that was hurting the most
>> and am watching to see if we have more freezes.
>>
>> If this does the trick, then I can delay deploying a new kernel until
>> April,
