You run -current, this is what you need to expect for being on the bleeding edge. Snapshots are not always built quickly since people also have a live and are not sitting at the computer all the time.
Right now the amd64 snap is from Mon Oct 21 04:30:06 UTC 2024 the revert of the problematic UVM commit happened at Mon Oct 21 06:07:33 2024 UTC. So yes that snap does not contain the fix. So you need to build your own kernel and use that one. You do not need to rebuild all of userland since there was no commit the would require that. If you want to run -current be prepared to build by your own. Also you should keep an eye on the source changes to know when an ABI change happens. So you know when you can just update a kernel or if a full build is needed. -- :wq Claudio On Tue, Oct 22, 2024 at 03:01:46AM -0400, William Thebrand wrote: > After five hours of building from source, and then abandoning the build, > because by that time the snapshot was available. I performed "sysupgrade > - s" for the new snapshot, and rebooted into it. Now, I am exactly back > where I started. The problematic code for UVM was not reverted for the > snapshot build on October the 21st, and is still included. Just for > reference, it was reported in the snapshot for October the 19th. I am > including the photo taken of the screen with trace and the kernel trap > message. > > I was told the problem would be fixed in the next snapshot, so I can only > hope the issue is resolved in the source code. It will take thirty minutes > of filesystem checks, another thirty to build the kernel, and over five > hours to build the system. Which pushes system access to 8 am. > > William > > On Mon, Oct 21, 2024, 1:33 PM William Thebrand <williamthebr...@gmail.com> > wrote: > > > That was a stupid question. The next snapshot release will occur tonight > > around 10pm EST. > > > > I will build from source, by booting from a release cd, mount my hard > > drive, pull from anoncvs, and then build source. > > > > It seems like the "grown-up" thing to do. Been a while since I have had to > > build from source, but relatively easy, and the FAQ is always their as a > > guide. > > > > William > > > > On Mon, Oct 21, 2024, 12:55 PM William Thebrand <williamthebr...@gmail.com> > > wrote: > > > >> Cool beans. When will the next snapshot be out? > >> > >> On Mon, Oct 21, 2024, 6:11 AM Martin Pieuchot <m...@grenadille.net> wrote: > >> > >>> On 21/10/24(Mon) 01:12, William Thebrand wrote: > >>> > I pull the newest snapshot release every sunday, and run a full > >>> upgrade on > >>> > my system. Which means the OS, packages, and even git based projects I > >>> use. > >>> > Four times in a row, the system has crashed without warning, and is > >>> > practically unusable. There is variance on what I was doing when the > >>> system > >>> > decided to crash, so the source of the crash assumedly deals with a > >>> > background process. > >>> > > >>> > I have tried to "tread lightly", and poke around to see if I can find > >>> the > >>> > error, but it just crashes regardless, with little progress. As you > >>> would > >>> > be aware of, with each crash there is a 30min filesystem check, which > >>> makes > >>> > exploration rather time consuming. > >>> > > >>> > This is the most severe bug I have come across in my experience with > >>> > OpenBSD. I can usually work around them, but not this time. It's at a > >>> > rather bad time, because I need my system for work. > >>> > > >>> > There are more photos than Gmail allows me to upload. So I might have > >>> to > >>> > creat a gallery in google photos. > >>> > >>> This is due to a mistake that has been reverted. Please wait for the > >>> next snapshot or build a kernel from sources. > >>> > >>> Cheers, > >>> Martin > >>> > >>
