Re: where to upgrade 12-stable now, svn still, or git?

2021-02-17 Thread Mark Millard via freebsd-stable
On 2021-Feb-12, at 23:03, Mark Millard wrote: > Dewayne Geraghty dewayne at heuristicsystems.com.au wrote on > Sat Feb 13 06:04:52 UTC 2021 : > >> The main list we used was: >> >> https://lists.freebsd.org/pipermail/svn-src-stable-12/ >> >> but that appears dead. >> . . . >>

Re: [pf] stable/12: block by OS broken

2021-02-17 Thread Xin Li via freebsd-stable
On 2/17/21 22:35, Kristof Provost wrote: > On 18 Feb 2021, at 6:01, Xin Li wrote: > > Hi, > > It appears that some change between 939430f2377 (December 31) and > b4bf7bdeb70 (today) on stable/12 have broken pf in a way that the > following rule: > > block in quick proto tcp

Re: Microcode update prevents boot

2021-02-17 Thread Leon Christopher Dietrich
>> Could you see >> if the hang persists when boot-time ucode loading is enabled and >> vm.pmap.di_locked=1 is configured? Hi, I can confirm that setting vm.pmap.di_locked=1 and enabling the loading of the cpu microcode at the same time does not cause any trouble. Unfortunately I didn't had

git to svn update frequency ?

2021-02-17 Thread mike tancsa
Hi     I noticed on a box that I update RELENG_12 via git there are more recent commits then if I use svnlite to track.  Are they only periodically updated ? If so, how frequently do they get refreshed ?  e.g. I see the new OpenSSL version in git, but not when I update via svnlite. # svnlite

Re: where to upgrade 12-stable now, svn still, or git?

2021-02-17 Thread Warner Losh
> On Feb 12, 2021, at 5:31 PM, tech-lists wrote: > As subject, where to get sources for 12-stable upgrade now? Is it still > svn or is it git? tl;dr: git is the source of truth, but there’s a bunch of details that might matter. The current source of truth is git repository on

Problems with SDHCI on Denverton SoC on stable/12 and stable/11

2021-02-17 Thread Justin Hibbits
On a Denverton SoC platform with eMMC, under heavy load I see a "Controller timeout" error, followed by a register dump, and then every operation performed after returns a timeout from the MMC (Error indicated: 1 Timeout). The only way to recover is to reboot the machine. This also occurs when

Re: git to svn update frequency ?

2021-02-17 Thread mike tancsa
On 2/17/2021 12:10 PM, Warner Losh wrote: > On Feb 17, 2021, at 6:05 AM, mike tancsa wrote: >> I noticed on a box that I update RELENG_12 via git there are more >> recent commits then if I use svnlite to track. Are they only >> periodically updated ? If so, how frequently do they get

Re: where to upgrade 12-stable now, svn still, or git?

2021-02-17 Thread Ed Maste
On Fri, 12 Feb 2021 at 23:11, tech-lists wrote: > > I saw on cgit that stable/12 was there. These older systems weekly > update their sources via svn till now, in a cron job. At the time I wrote > my message, I saw that svn still works, so was wondering which to use, > which has the latest

Re: git to svn update frequency ?

2021-02-17 Thread Warner Losh
> On Feb 17, 2021, at 6:05 AM, mike tancsa wrote: > I noticed on a box that I update RELENG_12 via git there are more > recent commits then if I use svnlite to track. Are they only > periodically updated ? If so, how frequently do they get refreshed ? > e.g. I see the new OpenSSL version

Re: where to upgrade 12-stable now, svn still, or git?

2021-02-17 Thread Ed Maste
On Sat, 13 Feb 2021 at 01:04, Dewayne Geraghty wrote: > > Is there a timeline when svn for stable-12 /usr/src disappears? stable/11 and stable/12 will exist in svn for at least as long as the branches are supported - stable/12 expected EOL is June 30,2024. If you're tracking stable you don't

Re: where to upgrade 12-stable now, svn still, or git?

2021-02-17 Thread Warner Losh
> On Feb 12, 2021, at 11:03 PM, Dewayne Geraghty > wrote: > As a change management task, I would hope that a mapping between svnlite > and git would've become available for FreeBSD users, similar to the cvs > to svnlite migration. I guess we need to create a test machine to > figure out the

[pf] stable/12: block by OS broken

2021-02-17 Thread Xin Li via freebsd-stable
Hi, It appears that some change between 939430f2377 (December 31) and b4bf7bdeb70 (today) on stable/12 have broken pf in a way that the following rule: block in quick proto tcp from any os "Linux" to any port ssh would get interpreted as: block drop in quick proto tcp from any to any port = 22

Re: [pf] stable/12: block by OS broken

2021-02-17 Thread Kristof Provost
On 18 Feb 2021, at 6:01, Xin Li wrote: Hi, It appears that some change between 939430f2377 (December 31) and b4bf7bdeb70 (today) on stable/12 have broken pf in a way that the following rule: block in quick proto tcp from any os "Linux" to any port ssh would get interpreted as: block drop in

Re: [pf] stable/12: block by OS broken

2021-02-17 Thread Xin Li via freebsd-stable
On 2/17/21 22:57, Xin Li wrote: > On 2/17/21 22:35, Kristof Provost wrote: >> On 18 Feb 2021, at 6:01, Xin Li wrote: >> >> Hi, >> >> It appears that some change between 939430f2377 (December 31) and >> b4bf7bdeb70 (today) on stable/12 have broken pf in a way that the >> following