On Tue, 26 Jun 2018 07:05:22 -0700
Eitan Adler wrote:
> On 19 June 2018 at 02:50, Gary Jennejohn wrote:
> > On Mon, 18 Jun 2018 22:44:13 -0700
> > Eitan Adler wrote:
> >
> >> On 13 June 2018 at 04:16, Eitan Adler wrote:
> >> > On 13 June 2018 at 03:35, Konstantin Belousov
> >> > wrote:
On 19 June 2018 at 02:50, Gary Jennejohn wrote:
> On Mon, 18 Jun 2018 22:44:13 -0700
> Eitan Adler wrote:
>
>> On 13 June 2018 at 04:16, Eitan Adler wrote:
>> > On 13 June 2018 at 03:35, Konstantin Belousov wrote:
>> >> Today I noted that AMD published the public errata document for Ryzens,
>>
On Mon, 18 Jun 2018 22:44:13 -0700
Eitan Adler wrote:
> On 13 June 2018 at 04:16, Eitan Adler wrote:
> > On 13 June 2018 at 03:35, Konstantin Belousov wrote:
> >> Today I noted that AMD published the public errata document for Ryzens,
> >>
On 13 June 2018 at 04:16, Eitan Adler wrote:
> On 13 June 2018 at 03:35, Konstantin Belousov wrote:
>> Today I noted that AMD published the public errata document for Ryzens,
>> https://developer.amd.com/wp-content/resources/55449_1.12.pdf
>>
>> Some of the issues listed there looks quite
On 6/13/2018 6:35 AM, Konstantin Belousov wrote:
>
> Please report the results. If the script helps, I will code the kernel
> change to apply the workarounds.
The hard lockups I was seeing on Ryzen and Epyc boxes are now gone with
the microcode and script below.
Not sure if its one or some
On Thursday, June 14, 2018, Mike Tancsa wrote:
> On 6/14/2018 11:03 AM, Konstantin Belousov wrote:
> > I am not sure about only microcode update. Depending on the BIOS
> > vendor and current BIOS, you may need all three: BIOS update, microcode
> > update using cpucontrol/devcpu-data, and
On 6/14/2018 11:03 AM, Konstantin Belousov wrote:
> I am not sure about only microcode update. Depending on the BIOS
> vendor and current BIOS, you may need all three: BIOS update, microcode
> update using cpucontrol/devcpu-data, and running the script I posted.
> In the best case, some of this
On 6/14/2018 11:03 AM, Konstantin Belousov wrote:
> I am not sure about only microcode update. Depending on the BIOS
> vendor and current BIOS, you may need all three: BIOS update, microcode
> update using cpucontrol/devcpu-data, and running the script I posted.
> In the best case, some of this
On Thu, Jun 14, 2018 at 10:24:17AM -0400, Mike Tancsa wrote:
> On 6/14/2018 9:36 AM, Eric van Gyzen wrote:
> > On 06/13/2018 05:35, Konstantin Belousov wrote:
> >> Today I noted that AMD published the public errata document for Ryzens,
> >>
On 6/14/2018 9:36 AM, Eric van Gyzen wrote:
> On 06/13/2018 05:35, Konstantin Belousov wrote:
>> Today I noted that AMD published the public errata document for Ryzens,
>> https://developer.amd.com/wp-content/resources/55449_1.12.pdf
>>
>> Some of the issues listed there looks quite relevant to
On 06/13/2018 05:35, Konstantin Belousov wrote:
> Today I noted that AMD published the public errata document for Ryzens,
> https://developer.amd.com/wp-content/resources/55449_1.12.pdf
>
> Some of the issues listed there looks quite relevant to the potential
> hangs that some people still
On 6/13/2018 6:35 AM, Konstantin Belousov wrote:
> Today I noted that AMD published the public errata document for Ryzens,
> https://developer.amd.com/wp-content/resources/55449_1.12.pdf
>
> Some of the issues listed there looks quite relevant to the potential
> hangs that some people still
On Wed, 13 Jun 2018 14:46:25 +0300
Konstantin Belousov wrote:
> On Wed, Jun 13, 2018 at 12:06:42PM +0100, Johannes Lundberg wrote:
> >
> > Konstantin Belousov writes:
> >
> > > Today I noted that AMD published the public errata document for Ryzens,
> > >
On Wed, Jun 13, 2018 at 12:06:42PM +0100, Johannes Lundberg wrote:
>
> Konstantin Belousov writes:
>
> > Today I noted that AMD published the public errata document for Ryzens,
> > https://developer.amd.com/wp-content/resources/55449_1.12.pdf
> >
> > Some of the issues listed there looks quite
On 13 June 2018 at 03:35, Konstantin Belousov wrote:
> Today I noted that AMD published the public errata document for Ryzens,
> https://developer.amd.com/wp-content/resources/55449_1.12.pdf
>
> Some of the issues listed there looks quite relevant to the potential
> hangs that some people still
Konstantin Belousov writes:
> Today I noted that AMD published the public errata document for Ryzens,
> https://developer.amd.com/wp-content/resources/55449_1.12.pdf
>
> Some of the issues listed there looks quite relevant to the potential
> hangs that some people still experience with the
16 matches
Mail list logo