gcc12 just reached 3000 days of uptime, which amounts to a little more than 8 years!
Here is a bit of history on this machine hosted by FSF France:
2007-06-24 gcc11/12/13 installed 2007-07-22 gcc11/12/13 moved to datacenter, gcc01..09 stopped, gcc08 online at a temporary location 2007-11-25 gcc11/12/13 moved to new datacenter, downtime 1700 UTC to 2000 UTC 2008-05-18 gcc11 and gcc12 moved to new datacenter (same IP). 2009-08-14 planned downtime for gcc11/gcc12 at the end of august 2009-08-31 gcc12 is down, please use gcc13 until gcc12 is restored 2009-09-21 gcc11/12 are up in their new FSF France datacenter in Rennes
Since then, the machine (and its hosting facility) has been extremely stable. Of course, since it is still running Debian 5 "lenny" and has limited hardware resources for today's standards, its usage is quite low nowadays.
There were even older machines in the GCC compile farm, see the history of the project.
We are happy to announce that four new x86_64 servers have joined the farm, numbered gcc120 to gcc123. These are Open Compute Project servers from Facebook, with two 8-cores Xeon and 144 GB of RAM. Two of them are running CentOS 7, and the two others are running Debian 9.
Note that these machines are reachable on a non-default SSH port. The SSH ports are displayed in the list of machines, and there is a SSH configuration that you can copy-paste (click on Show SSH config at the top of the page).
Many thanks to OSUOSL for setting up and hosting these servers!
We are happy to announce that 4 new x86_64 virtual machines have joined the farm:
- gcc300 runs NetBSD
- gcc301 runs Alpine Linux
- gcc302 runs OpenBSD
- gcc303 runs FreeBSD
Please note that their resources are quite limited in terms of disk, CPU & memory, so make sure to use them responsibly.
The machines are located in Calgary, Canada. Many thanks to House Gordon Software Company for providing these virtual machines!
We are pleased to announce the availability of two new machines in the compile farm: gcc210 and gcc211 are Solaris zones, hosted on a M3000 server with a SPARC64 CPU. gcc210 runs Solaris 10, while gcc211 runs Solaris 11.
The machines are located in Kiel, Germany. Many thanks to Baltic Online for the hosting, along with the OpenCSW project for the support!
We just upgraded gcc67/68 to the latest BIOS/AGESA, added some settings to BIOS and kernel (see below) and restored ssh access to all accounts.
Please test to see if the ryzen machines are at last stable under cfarm usage patterns.
Note: we had to blacklist ccp kernel module on gcc68 so no kvm there. We'll restore it when new kernel is available with the proper fix for gcc68 processor.
PS: here are the instructions we followed:
https://utcc.utoronto.ca/~cks/space/blog/linux/RyzenApparentlyStable
For a long time these magic kernel command line parameters and similar tricks were the only workarounds available, at least to me. However there had long been rumors of a magic AMD provided magic firmware option that could work around the problem, generally exposed to you and me in a BIOS setting called 'Power Supply Idle Control', which you allegedly wanted to set to 'Typical current idle'. This apparently became available starting with AGESA 1.0.0.2a, which various motherboard vendors rolled into their overall BIOS at very different times. For bonus fun, apparently not all BIOS vendors even expose these AMD firmware settings, although enthusiast motherboards usually do.
https://utcc.utoronto.ca/~cks/space/blog/linux/KernelRcuNocbsMeaning
rcu_nocbs=0-N processor.max_cstate=1
(where N is the number of CPUs you have minus one.)
gcc202, a SPARC64 LDOM running Debian, had been offline since May because of a hardware issue.
The issue has been found and worked around: the machine is back online, but there may remain instabilities.
gcc10, a 24-cores Magny-Cours Opteron, had been offline for almost one year. It was running a very old version of Debian.
The machine has been reinstalled on Debian stretch and is now available again, many thanks to FSF France for the dedicated trip to the datacenter! User data has been preserved while reinstalling the system.
A farm volunteer tried to upgrade gcc70 to a newer NetBSD version, but it failed.
The machine was reinstalled on Debian stretch. From now on, support for NetBSD in the farm will probably only happen as virtual machines.
Not-for-profit ISP tetaneutral.net sponsored a new processor to replace the faulty one on gcc68: a Ryzen 7 2700 8C/16T 3.2/4.1 GHz, it has been installed last friday 20180622.
Thanks to Mehdi and Nicolas for their time on gcc68.
gcc13 and gcc14 have been re-installed with Debian 9 (stretch). They were previously running Debian 5 (lenny), and an attempt to upgrade them failed. We were able to keep user data (/home) for gcc13 but not for gcc14.
gcc117, one of the aarch64 machines that was running OpenSUSE, had a btrfs-related crash a few months ago. We decided to re-install it on Debian, since it now supports aarch64. User data in /home was also preserved.
All users should be able to access these machines again with SSH. Since the SSH host keys have changed, it may be necessary to remove the old host keys with "ssh-keygen -R gccXXX.fsffrance.org" beforehand.
Many thanks to our hosts Smile and OSUOSL for the time they spent helping us to troubleshoot and reinstall the machines!