(n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-01-29 Thread Hartmann, O.
We recently updated to FreeBSD 14.0-CURRENT #9 main-n244517-f17fc5439f5: Fri Jan 29 16:29:50 CET 2021 amd64. After make delete-oldfiles/delete-old-libs, the command make update issued in /usr/ports on those 14-CURRENT boxes remains stuck forever or it is working like a snail! Hitting Ctrl-t

(n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-01-29 Thread Hartmann, O.
We recently updated to FreeBSD 14.0-CURRENT #9 main-n244517-f17fc5439f5: Fri Jan 29 16:29:50 CET 2021 amd64. After make delete-oldfiles/delete-old-libs, the command make update issued in /usr/ports on those 14-CURRENT boxes remains stuck forever or it is working like a snail! Hitting Ctrl-t

Re: zpool upgrade to draid feature: does it require updated zfs boot code ?

2021-01-29 Thread Xin Li via freebsd-current
On 1/28/21 11:00, Kurt Jaeger wrote: > Hi! > > Short question: > > Does a zpool upgrade on 14.0 (current) for the draid feature > require a boot code update ? > > Long version of the same question: [...] > With the draid update, no message was displayed. > > Does it require the bootcode update

Re: Waiting for bufdaemon

2021-01-29 Thread Yasuhiro Kimura
From: Yasuhiro Kimura Subject: Re: Waiting for bufdaemon Date: Thu, 28 Jan 2021 05:02:42 +0900 (JST) > It took for a while to investigate, but according to the result of > bisect following commit is the source of problem in my case. > > ---

Re: i915kms and chip resets on rsc0?

2021-01-29 Thread Mark Linimon
On Thu, Jan 28, 2021 at 02:20:40PM -0800, Steve Kargl wrote: > This is all likely academic as I just saw John Baldwin's email > that stated i386 support is being dropped in FreeBSD-current. s/dropped/downgraded/ The only difference seems to be that security upgrades that _only_ affect i386 will n

Re: drm-fbsd13-kmod pkg-descr

2021-01-29 Thread monochrome
heh I got worried because my ryzen vega needs 4.17 and up On 1/29/21 5:05 AM, Emmanuel Vadot wrote: On Fri, 29 Jan 2021 04:59:27 -0500 monochrome wrote: correct me if I'm wrong, but shouldn't it say: Currently corresponding to Linux 5.4.62 DRM. instead of: Currently corresponding to Linux

Re: drm-fbsd13-kmod pkg-descr

2021-01-29 Thread Emmanuel Vadot
On Fri, 29 Jan 2021 04:59:27 -0500 monochrome wrote: > correct me if I'm wrong, but shouldn't it say: > > Currently corresponding to Linux 5.4.62 DRM. > > instead of: > > Currently corresponding to Linux 4.16 DRM. > > got caught by this while trying to update drm-devel-kmod from ports on > s

drm-fbsd13-kmod pkg-descr

2021-01-29 Thread monochrome
correct me if I'm wrong, but shouldn't it say: Currently corresponding to Linux 5.4.62 DRM. instead of: Currently corresponding to Linux 4.16 DRM. got caught by this while trying to update drm-devel-kmod from ports on stable/13, and took a chance that it was just an oversight :)