[cfarm-users] gcc68: new processor AMD Ryzen 7 2700 8C/16T 3.2/4.1 GHz

[Laurent GUERBY via cfarm-users]

Hi,

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,

Sincerely,

Laurent

___
cfarm-users mailing list
cfarm-users@lists.tetaneutral.net
https://lists.tetaneutral.net/listinfo/cfarm-users

[cfarm-users] gcc67: new processor AMD Ryzen 5 2400G with Radeon Vega Graphics

[Laurent GUERBY via cfarm-users]

Hi,

Not-for-profit ISP tetaneutral.net sponsored a new processor to replace
the faulty one on gcc67: a Ryzen 5 2400G with Radeon Vega Graphics
4C/8T 3.6/3.9 GHz.

Since this processor is fairly recent a 4.16.0-rc4 linux kernel has
been manually compiled and installed. The machine appears to be stable
surviving 48h of kill-ryzen.sh. Only issue so far is that at some
point in the boot process the console screen is frozen and stops
updating.

We didn't try the various GPU drivers yet, if you're interested
in testing code on the Vega GPU let us know what we need to compile and
install.

Thanks to Mehdi and Nicolas for their time on gcc67,

Sincerely,

Laurent

PS: we haven't decided yet what to do with gcc68.

___
cfarm-users mailing list
cfarm-users@lists.tetaneutral.net
https://lists.tetaneutral.net/listinfo/cfarm-users

[cfarm-users] gcc67 and gcc68 are back online

[Laurent GUERBY via cfarm-users]

Hi,

gcc67 now has the latest BIOS P4.60 (which caused a change in the
network interface name from enp10s0 to enp37s0 ...), we kept the
older BIOS P3.00 on gcc68 for now to avoid another trip to the DC.

Both have new Ryzen 7 1700X processors sent to us by AMD to replace the
older ones that had stability issues. We'll likely put a Ryzen 5 in
gcc68 in the near future to keep diversity.

Sincerely,

Laurent

___
cfarm-users mailing list
cfarm-users@lists.tetaneutral.net
https://lists.tetaneutral.net/listinfo/cfarm-users

Re: [cfarm-users] gcc67 back online was: gcc67 down ? was: gcc67 instability?

[Laurent GUERBY via cfarm-users]

On Tue, 2017-12-26 at 12:41 +0100, Nicolas Gonzalez via cfarm-users
wrote:
> Hi,
> 
> gcc67 and gcc68 are not reachable for few days, we sent Ryzen
> processors 
> back to AMD by RMA.
> 
> Sorry for the temporary inconvenience.
> 
> ngonzalez

Hi,

After contacting AMD about our Ryzen freeze issue they immediately sent
us 4 new processors: 2 Ryzen 7 1700X and 2 Ryzen 5 1400 :).

So gcc67 is back online with a new processor, thanks to Nicolas and
Mehdi for their trip to the datacenter.

We ran ryzen-test (1) on it and it didn't freeze the machine.

Unfortunately gcc68 motherboard appears to be dead, our hoster
tetaneutral.net will provide us with a new AM4 motherboard in the
coming weeks so gcc68 should be back online soon.

Many thanks to AMD!

Sincerely,

Laurent

(1) https://github.com/suaefar/ryzen-test

___
cfarm-users mailing list
cfarm-users@lists.tetaneutral.net
https://lists.tetaneutral.net/listinfo/cfarm-users

Re: [cfarm-users] AMD Ryzen issues was: Upgrade status and status on cfarm offline

[Laurent GUERBY via cfarm-users]

On Sat, 2017-08-19 at 13:24 +0200, Torbjörn Granlund via cfarm-users
wrote:
>   It is a CPU bug. The only solution is to RMA the CPU. Just contact
> AMD.
>   They are aware of the issue. All Ryzen CPUs are potentially
> affected.
>   See: https://community.amd.com/thread/215773
> 
> There is a Ryzen CPU bugs which causes random segfaults, no doubt.
> 
> But not all segfaults on Ryzens are due to that bug.  Firmware
> fixable
> DRAM incompatibilities and other firmware fixable Ryzen bugs can also
> cause segfaults.
> 
> Therefore, upgrading the BIOS before RMAing is a quite good
> idea.  After
> all, you might already have a Ryzen with the segfault fix.

Hi,

We plan to upgrade the BIOS of gcc67/68 this monday: we're on P2.60
06/07/2017 and will flash P3.00 7/18/2017 that comes with a
newer AGESA version (Asrock AB350 Gaming K4).

If we have time monday we'll also look at the processors packaging to
get the batch number in case we need to contact AMD.

Our Ryzen notes are here including the crash information we got from
netconsole:

https://pad.tetaneutral.net/p/gcc67

Baptiste upgraded the kernel to 4.12 yesterday on gcc67.

We haven't found out wether there's a watchdog or not on these
platforms (/dev/watchdog isn't present).

Sincerely,

Laurent

___
cfarm-users mailing list
cfarm-users@lists.tetaneutral.net
https://lists.tetaneutral.net/listinfo/cfarm-users

Re: [cfarm-users] New website to manage the GCC compile farm

[Laurent GUERBY via cfarm-users]

On Tue, 2017-08-08 at 19:34 -0500, Don Bright via cfarm-users wrote:
> This is outstanding work. Can the old Wiki have a re-direct or link
> to the new site? The old Wiki is still the first google hit  for 'gnu
> compile farm' and its full of wrong info. 

Hi,

The old wiki already points to the new site for account creation.
At some point there will be a wiki on the new site but that's
not high on the priority list :).

I removed a few obsolete informations on the old wiki.

Sincerely,

Laurent

> On Fri, Jun 30, 2017 at 6:43 PM, Baptiste Jonglez via cfarm-users
>  wrote:
> > Dear compile farm users,
> > 
> > We are happy to announce the availability of a new website to
> > manage
> > access to the farm!
> > 
> > It currently has three end-users functions:
> > 
> > 1) the ability to add and remove SSH keys yourself;
> > 
> > 2) new users can now request an account directly from the website:
> >    https://cfarm.tetaneutral.net/users/new/
> > 
> > 3) the description of farm machines is generated and updated
> >    automatically: https://cfarm.tetaneutral.net/machines/list/
> > 
> > This should resolve the growing backlog of unhandled requests.  In
> > the
> > near future, a ticket tracker will be added for requests that are
> > not
> > related to accounts or SSH keys.
> > 
> > The site, still in beta status, is available at https://cfarm.tetan
> > eutral.net/
> > 
> > All existing accounts have been imported: to start using the
> > website if
> > you already had access to the farm, please perform the following
> > steps:
> > 
> > 1) Enter your email address at https://cfarm.tetaneutral.net/passwo
> > rd_reset/
> >    You will receive a link, allowing you to choose a password to
> > connect
> >    to the website.  If you don't receive an email after a while,
> > you may
> >    be using a different email address than the one registered in
> >    the system.  In that case, send an email to cfarm-admins AT
> > lists.tetaneutral.net
> >    and provide your Unix login.
> > 
> > 2) Once connected, you can add or remove SSH keys at https://cfarm.
> > tetaneutral.net/sshkey/list/
> >    The new keys may take from a few minutes to several hours to get
> > updated
> >    on all farm machines.
> > 
> > Existing SSH keys have been imported in the new website, with the
> > exception of old-style plain RSA keys (starting with e.g. "1024 35
> > ...").
> > This old key format is not supported anymore: as soon as you change
> > your
> > SSH keys on the website, these old keys will be overwritten on all
> > farm
> > machines.
> > 
> > Regards,
> > Baptiste, for the compile farm admin team
> > 
> > ___
> > cfarm-users mailing list
> > cfarm-users@lists.tetaneutral.net
> > https://lists.tetaneutral.net/listinfo/cfarm-users
> > 
> 
> ___
> cfarm-users mailing list
> cfarm-users@lists.tetaneutral.net
> https://lists.tetaneutral.net/listinfo/cfarm-users
___
cfarm-users mailing list
cfarm-users@lists.tetaneutral.net
https://lists.tetaneutral.net/listinfo/cfarm-users

[cfarm-users] OSL Crowdfunding - Student Sponsorship Campaign

[Laurent GUERBY via cfarm-users]

Hi,

OSUOSL people are hosting a lot of GCC Compile Farm hardware and the
students mentionned below are volunteer sysadmins for our machines,
we see them answer our support tickets when needed.

If you wish to help the compile farm please consider donating to
this campaign :).

Sincerely,

Laurent

 Forwarded Message 
From: Lance Albertson 
Subject: [Hosting] OSL Crowdfunding - Student Sponsorship Campaign
Date: Fri, 28 Jul 2017 10:13:31 -0700

Dear hosted projects,

We launched a student sponsorship crowdfunding campaign [1] with the
OSU Foundation this past Monday that will run for 30 days. Our goal is
to raise $10,000 but if we raise more that would be great. This will go
towards funding students working at the lab along with sending them to
open source conferences in the coming year. Please contribute and pass
the word around to your colleagues and friends if possible!

[1] https://create.osufoundation.org/project/6976

-- 
Lance Albertson
Director
Oregon State University | Open Source Lab 

___
cfarm-users mailing list
cfarm-users@lists.tetaneutral.net
https://lists.tetaneutral.net/listinfo/cfarm-users

[cfarm-users] [Fwd: Re: [Gcc-cfarm-users] gcc67 and gcc68: New AMD donated Ryzen processor machines]

[Laurent GUERBY via cfarm-users]

 Forwarded Message 
From: Alexandre Oliva 
Subject: Re: [Gcc-cfarm-users] gcc67 and gcc68: New AMD donated Ryzen
processor machines
Date: Sun, 21 May 2017 01:09:27 -0300
Mailer: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)

On May 20, 2017, Ineiev  wrote:

> Unfortunately, neither works for me, as well as
> "ssh ine...@gcc10.fsffrance.org"; in all cases it suggests entering
> my password.

It could have to do with the kind of key.  I've personally had issues
with certain key types: the old keys I registered many years ago still
work on some machines, but some newer machines and/or my local hosts
cannot use those key types any more, so I can't get into some of the
newer machines, and I can't find out how to have my newer SSH keys
propagated to the newer machines.

A while ago, I sent an email following the procedure under "How to Get
Involved?" in https://gcc.gnu.org/wiki/CompileFarm in an attempt to have
the keys updated, to no avail: I never got a response.

I didn't think a support request through the web site would have been
workable: how would my account at the support site be tied to the
existing login in the Compile Farm to tell whether the request was
legitimate?  Anyway, I tried that too, but the password I had created at
some point doesn't work any more, and the request to send it by email
seems to go to a void, or to an address I can't get to any more.  And if
I create a new account there, it would be even harder to connect it to
my existing account in the farm, I suppose.

Anyway, it would be nice to have a documented procedure in the wiki
stating how to get SSH keys updated.  It might even be the case that the
procedure to get an initial account needs updating, if the support site
is the preferred way now.

If someone (Laurent?) can tell me what the procedures to update SSH?
keys is, and whether other procedures need updating in the wiki, I will
update it there.

Thanks,

-- 
Alexandre Oliva, freedom fighterhttp://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist|Red Hat Brasil GNU Toolchain Engineer


___
cfarm-users mailing list
cfarm-users@lists.tetaneutral.net
https://lists.tetaneutral.net/listinfo/cfarm-users