don't increment scatterlist length twice
this occurs as sg_dma_len() returns the length member of struct scatterlist
where as on x86 linux it returns a dma_length member of the struct
Problem reported by Ryan Fahy in FreeBSD drm-kmod PR 468.
Avoids a 'Data modified on freelist' panic on boot when using discrete
Intel cards (DG2). DG2 has other issues, so remains disabled for now.
revert scatterlist dma_length changes
deraadt reports this caused 'flip_done timed out', 'commit wait timed out'
and a black screen when starting X on meteor lake
cpp: no longer default to -traditional
calendar(1) and xrdb(1) that use cpp as a generic macro processor
already call "/usr/libexec/cpp -traditional".
ok jsg@ deraadt@
update to crystal-1.20.1 and shards-0.20.0
switch to llvm 22
use kqueue backend since libevent backend hangs while compiling
remove myself as maintainer
sys/vfs: discard buffers after vclean error
vclean() ignored vinvalbuf(V_SAVE) failures and continued into
VOP_RECLAIM(). If dirty buffer writeback failed, the vnode could be
reclaimed and later reused while old buffers still referenced the same
struct vnode identity.
Report the failed flush, then force buffer invalidation before reclaim
proceeds. vclean() has no failure channel; discarding dirty buffers may
lose data, but reusing the vnode with stale buffers is worse, and a
panic would risk unrelated dirty state.
OK claudio@