On Fri, Oct 06, 2017 at 09:02:09PM +0200, Johannes Hirte wrote:
> 19001011
> 19001011
> 19001011
> 19001011
After you boot, do
wrmsr -a 0xc0010015 0x19001019
as root.
It should fix it temporarily and until the next boot, until we've fixed
it upstream properly.
--
Regards/Gruss,
Boris.
Go
On 2017 Sep 30, Borislav Petkov wrote:
> On Sat, Sep 30, 2017 at 02:47:11PM +0200, Markus Trippelsdorf wrote:
> > Changing the TLB code so late might not be a good idea...
>
> The new lazy code is too risky to keep as we don't know what else will
> break. The conservative and thus safe thing to do
On 2017 Okt 06, Borislav Petkov wrote:
> On Fri, Oct 06, 2017 at 08:49:33PM +0200, Johannes Hirte wrote:
> > I see the same behaviour on Carizzo. Is Excavator an old machine too?
>
> Do
>
> # rdmsr -a 0xc0010015
>
> as root and paste it here.
>
> Thx.
19001011
19001011
19001011
19001011
--
Re
On Fri, Oct 06, 2017 at 08:49:33PM +0200, Johannes Hirte wrote:
> I see the same behaviour on Carizzo. Is Excavator an old machine too?
Do
# rdmsr -a 0xc0010015
as root and paste it here.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
On Sat, Sep 30, 2017 at 01:53:02PM +0200, Borislav Petkov wrote:
> On Sat, Sep 30, 2017 at 01:29:03PM +0200, Adam Borowski wrote:
> > On Sat, Sep 30, 2017 at 01:11:37PM +0200, Borislav Petkov wrote:
> > > On Sat, Sep 30, 2017 at 04:05:16AM +0200, Adam Borowski wrote:
> Boot into -rc2+ and do as ro
On Sat, Sep 30, 2017 at 8:50 AM, Borislav Petkov wrote:
> On Sat, Sep 30, 2017 at 02:47:11PM +0200, Markus Trippelsdorf wrote:
>> Changing the TLB code so late might not be a good idea...
>
> The new lazy code is too risky to keep as we don't know what else will
> break. The conservative and thus
On Sat, Sep 30, 2017 at 02:47:11PM +0200, Markus Trippelsdorf wrote:
> Changing the TLB code so late might not be a good idea...
The new lazy code is too risky to keep as we don't know what else will
break. The conservative and thus safe thing to do is to revert to the
old behavior for old machine
On Sat, Sep 30, 2017 at 08:11:51AM -0700, Andy Lutomirski wrote:
> Yeah, working on it. It's not a straightforward revert.
Thanks. At least you have testers :-)
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
On 2017.09.30 at 10:20 -0400, Brian Gerst wrote:
> On Sat, Sep 30, 2017 at 8:47 AM, Markus Trippelsdorf
> wrote:
> > On 2017.09.30 at 13:53 +0200, Borislav Petkov wrote:
> >> On Sat, Sep 30, 2017 at 01:29:03PM +0200, Adam Borowski wrote:
> >> > On Sat, Sep 30, 2017 at 01:11:37PM +0200, Borislav Pe
> On Sep 30, 2017, at 4:53 AM, Borislav Petkov wrote:
>
>> On Sat, Sep 30, 2017 at 01:29:03PM +0200, Adam Borowski wrote:
>>> On Sat, Sep 30, 2017 at 01:11:37PM +0200, Borislav Petkov wrote:
On Sat, Sep 30, 2017 at 04:05:16AM +0200, Adam Borowski wrote:
Any hints how to debug this?
>>
On Sat, Sep 30, 2017 at 8:47 AM, Markus Trippelsdorf
wrote:
> On 2017.09.30 at 13:53 +0200, Borislav Petkov wrote:
>> On Sat, Sep 30, 2017 at 01:29:03PM +0200, Adam Borowski wrote:
>> > On Sat, Sep 30, 2017 at 01:11:37PM +0200, Borislav Petkov wrote:
>> > > On Sat, Sep 30, 2017 at 04:05:16AM +0200
On 2017.09.30 at 13:53 +0200, Borislav Petkov wrote:
> On Sat, Sep 30, 2017 at 01:29:03PM +0200, Adam Borowski wrote:
> > On Sat, Sep 30, 2017 at 01:11:37PM +0200, Borislav Petkov wrote:
> > > On Sat, Sep 30, 2017 at 04:05:16AM +0200, Adam Borowski wrote:
> > > > Any hints how to debug this?
> > >
On Sat, Sep 30, 2017 at 01:29:03PM +0200, Adam Borowski wrote:
> On Sat, Sep 30, 2017 at 01:11:37PM +0200, Borislav Petkov wrote:
> > On Sat, Sep 30, 2017 at 04:05:16AM +0200, Adam Borowski wrote:
> > > Any hints how to debug this?
> >
> > Do
> > rdmsr -a 0xc0010015
> > as root and paste it here.
On Sat, Sep 30, 2017 at 01:11:37PM +0200, Borislav Petkov wrote:
> On Sat, Sep 30, 2017 at 04:05:16AM +0200, Adam Borowski wrote:
> > Any hints how to debug this?
>
> Do
> rdmsr -a 0xc0010015
> as root and paste it here.
110
110
110
110
110
110
on both 4.13.4 and 4.14-rc2
On Sat, Sep 30, 2017 at 04:05:16AM +0200, Adam Borowski wrote:
> Any hints how to debug this?
Do
rdmsr -a 0xc0010015
as root and paste it here.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Hi!
I'm afraid I see random instant reboots on current -rc, approximately
once per day, only under CPU load. There's nothing on serial/etc -- just
an immediate reboot. 4.13 works perfectly; last kernel I've tried is
v4.14-rc2-165-g770b782f555d. gcc 7.2.0-7 (Debian).
CPU is AMD Phenom II X6 1055
16 matches
Mail list logo