FreeBSD 12.2-BETA1
As someone who has been using FreeBSD for a long time on various machines of mine, both physical machines in my home and VMs in the cloud, I&#x27;m wondering how many people (both in absolute numbers and in percentages) run the beta releases on their hardware.<p>My general impression, which stems mostly from the description I once read on the FreeBSD downloads page and from elsewhere is that if you want to help find bugs in upcoming releases you run the CURRENT branch and else you run RELEASE. But I expect that there are people running the beta releases as well who make meaningful bug reports that result in fixes prior to release versions being minted – otherwise I think they would not be making beta releases still.<p>I did used to run CURRENT for a while, but eventually found out that personally I wasn&#x27;t making any particularly helpful bug reports based on it anyways so I went back to RELEASE.<p>For the VM server that I have been using for many years now for sending and receiving mail, as well as to host some websites of mine, running FreeBSD RELEASE has been working great for years.<p>Meanwhile, my desktop computer which is currently running FreeBSD 12.1-RELEASE is having issues where it freezes and requires a hard reboot. But I had this same kind of issue when I was running various Linux distros on this same desktop computer over the past years. I am suspecting that either it is a cause of hardware malfunction or possibly of the Nvidia driver for the graphics card, but I don&#x27;t really have any way of finding out what the actual problem is. Not the least because of the fact that it will often run for a week of being powered on perfectly fine (both with FreeBSD and Linux distros) until suddenly it just completely freezes. Doesn&#x27;t react to mouse, doesn&#x27;t react to keyboard, doesn&#x27;t respond to ping.<p>The fact that my desktop computer can run fine for about a week at a time makes it hard to figure out what the actual problem is. Say that I were to pull the graphics card out for example, and it ran fine for two weeks. How do I know at that point that I can really blame the graphics card and it wasn&#x27;t just random chance that made it run for longer than usual this time around?<p>I think in order to isolate the problem I would have to build like 8 different physical machines all with the same hardware, and then say ok four of the machines I will initially run like I do with my current desktop, and four of them I will pull the graphics card out of and then have them running 24x7 for a month or until at least two of the machines with Nvidia graphics cards crashed if sooner. At that point I might conclusively say there is strong evidence of problems with the Nvidia graphics cards or with the drivers for said cards.<p>But if the machines without the Nvidia graphics cards were also crashing then I&#x27;d need to swap out for example all of the motherboards and I&#x27;d run the experiment for another week. An so on.<p>On the flip-side, if all of them ran fine for a month with the initial configuration I would conclude that probably some of the hardware in my current machine is just broken, and that there is no bigger issue at play. But all of that would cost not just a lot of time but also a lot of money. And as-is the next thing I can afford to buy is certainly not such an amount of hardware – the next thing I am going to buy when I can afford it is rather a couple of new hard-drives, as the spinning disks that hold most of my data are getting a few years old and I am getting quite nervous about them suddenly going to fail me. I&#x27;ve had hard-disks fail on me in the past. In particular I used to have a machine with 4x 2TB hard-drives in it to provide me with ZFS storage, and then I moved houses and I accidentally dropped my computer from about 1 meter height and last time I tried to see if the drives were working none of them showed up neither after boot nor in BIOS, neither in the original computer that I had dropped nor in the desktop computer that I have now. Well anyways it don&#x27;t matter too much, none of the data was that important really. And I think said drives were making unusual noises also but I don&#x27;t quite remember as it was a while ago now. But that kind of experience, along with having had some external hard-drives fail me in the past, does feed into the worry that I have for my current hard-drive as it is getting a few years old now.<p>But back to what I was saying about trying to debug the issue with my desktop. In theory I could disconnect basically all but the RAM and the CPU from the motherboard (well, and but the fans of course :P) and boot a minimal kernel from a USB stick and have it run in RAM and let it stay powered on for four weeks and see if it crashed, and then if it doesn&#x27;t to connect the SSD and the HDD to it and run it for another four weeks and see if it crashes, and then to run the regular RELEASE kernel on it for four weeks and see what happens, and after that with the graphics card connected and see what happens for the next four weeks. But all of those weeks man. I just want my desktop to work, I don&#x27;t want to spend weeks with it running on its own without being available for my use.<p>Anyways, that brings me to something else related to the testing that people do and that is the fact that I find it kind of hard to know what hardware to pick for a FreeBSD desktop. There&#x27;s things like <a href="https:&#x2F;&#x2F;www.freebsd.org&#x2F;releases&#x2F;12.1R&#x2F;hardware.html" rel="nofollow">https:&#x2F;&#x2F;www.freebsd.org&#x2F;releases&#x2F;12.1R&#x2F;hardware.html</a> and <a href="https:&#x2F;&#x2F;wiki.freebsd.org&#x2F;Graphics" rel="nofollow">https:&#x2F;&#x2F;wiki.freebsd.org&#x2F;Graphics</a> and <a href="https:&#x2F;&#x2F;wiki.freebsd.org&#x2F;Graphics&#x2F;AMD-GPU-Matrix" rel="nofollow">https:&#x2F;&#x2F;wiki.freebsd.org&#x2F;Graphics&#x2F;AMD-GPU-Matrix</a> but they all seem kind of out of date.<p>If I had the money to buy the hardware for it and to pay the electric bills for it I would gladly be running a bunch of machines in different configurations of current consumer hardware and making notes and filing bug reports and hardware compatibility reports to help other users of FreeBSD and Linux. Maybe someday. Until that day I&#x27;ll just have to accept that every week or so I might have to hit that hard reset button on my desktop, inconvenient as it might be.