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

[Peter Korsgaard via cfarm-users]

> "Peter" == Peter Korsgaard  writes:

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.

 > Great, but I started an autobuilder for Buildroot on gcc67 and we still
 > see a number of odd crashes, E.G.:

 > malloc: .././dispose_cmd.c:249: assertion botched
 > free: called with unallocated block argument

 > /bin/bash: line 1:  7456 Segmentation fault

 > See this link for the autobuilder results. The errors are not all
 > related to the host, but there's several failures with malloc assertions
 > of bash segfaulting that we don't see on other machines:

 > http://autobuild.buildroot.org/?submitter=Peter+Korsgaard+%28gcc67%29

 > Does anything else needs to be updated? BIOS?

Nobody knows? Anyone having success using gcc67?

-- 
Bye, Peter Korsgaard
___
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?

[Peter Korsgaard via cfarm-users]

> "Laurent" == Laurent GUERBY via cfarm-users 
>  writes:

[resend from the address subscribed to the list]

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.

Great, but I started an autobuilder for Buildroot on gcc67 and we still
see a number of odd crashes, E.G.:

malloc: .././dispose_cmd.c:249: assertion botched
free: called with unallocated block argument

/bin/bash: line 1:  7456 Segmentation fault

See this link for the autobuilder results. The errors are not all
related to the host, but there's several failures with malloc assertions
of bash segfaulting that we don't see on other machines:

http://autobuild.buildroot.org/?submitter=Peter+Korsgaard+%28gcc67%29

Does anything else needs to be updated? BIOS?

-- 
Bye, Peter Korsgaard
___
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