From: Borislav Petkov <bp@alien8.de>
To: Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm ML <kvm@vger.kernel.org>
Subject: Re: Major KVM issues with kernel 4.5 on the host
Date: Sun, 24 Apr 2016 01:57:59 +0200 [thread overview]
Message-ID: <20160423235759.GA25381@pd.tnic> (raw)
In-Reply-To: <20160423184341.GA21755@torres.zugschlus.de>
On Sat, Apr 23, 2016 at 08:43:41PM +0200, Marc Haber wrote:
> Uncorrectable errors would still be identified by the ECC hardware,
Not if the hardware decides to syncflood so that we don't even get to
run the #MC handler...
> and the box wouldn't be perfectly fine with an "old" kernel.
Maybe the "old" kernel is not causing all the required ingredients to
come together for the uncorrectable error to happen. But yeah, I agree,
the fact that 4.4 is fine kinda doesn't fit with the uncorrectable error
theory.
> Yes, that would be in the logs.
Presumably. And see above.
> But we still postulate that the issue does only show on older AMD
> CPUs. Otherwise, I wouldn't be the only one making this experience.
It actually shows only on this one system. At least I'm not aware of any
other report of the same issue. My system with a F10h, rev E is just
fine.
> Do you want me to memtest for 24 hours?
Yeah, that memtest crap never triggers any ECCs. But if you're bored,
why not...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-04-23 23:57 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160317165435.GB3022@torres.zugschlus.de>
2016-03-17 18:11 ` Major KVM issues with kernel 4.5 on the host Borislav Petkov
2016-03-18 10:01 ` Paolo Bonzini
2016-04-13 18:37 ` Marc Haber
2016-04-13 20:36 ` Paolo Bonzini
2016-04-13 20:52 ` Marc Haber
2016-04-13 22:29 ` Marc Haber
2016-04-14 1:16 ` Paolo Bonzini
2016-04-14 5:22 ` Marc Haber
2016-04-21 8:39 ` Marc Haber
2016-04-21 12:37 ` Borislav Petkov
2016-04-21 14:50 ` Marc Haber
2016-04-21 16:51 ` Borislav Petkov
2016-04-21 20:04 ` Marc Haber
2016-04-23 16:04 ` Borislav Petkov
2016-04-23 18:43 ` Marc Haber
2016-04-23 18:52 ` Dr. David Alan Gilbert
2016-05-12 20:20 ` transparent huge pages breaks KVM on AMD Marc Haber
2016-05-12 20:24 ` Kirill A. Shutemov
2016-05-12 20:34 ` Marc Haber
2016-05-12 20:42 ` Kirill A. Shutemov
2016-05-13 5:23 ` Marc Haber
2016-05-13 8:07 ` Borislav Petkov
2016-05-13 8:09 ` Borislav Petkov
2016-05-13 13:21 ` Marc Haber
2016-05-13 16:08 ` Borislav Petkov
2016-05-14 6:19 ` Marc Haber
2016-05-13 9:08 ` Marc Haber
2016-05-13 9:19 ` Borislav Petkov
2016-05-13 14:59 ` Marc Haber
2016-05-13 8:35 ` Dr. David Alan Gilbert
2016-05-13 14:03 ` Marc Haber
2016-04-23 23:57 ` Borislav Petkov [this message]
2016-04-14 6:07 ` Major KVM issues with kernel 4.5 on the host Marc Haber
2016-04-14 16:47 ` Marc Haber
2016-04-14 17:30 ` Paolo Bonzini
2016-04-14 17:47 ` Marc Haber
2016-03-18 18:49 ` Marc Haber
2016-03-18 22:04 ` Borislav Petkov
2016-03-19 0:08 ` Marc Haber
2016-03-20 13:31 ` Borislav Petkov
2016-03-20 17:14 ` Andrey Korolyov
2016-03-20 18:25 ` Borislav Petkov
2016-03-20 18:42 ` Andrey Korolyov
2016-03-20 18:58 ` Borislav Petkov
2016-04-13 18:22 ` Marc Haber
2016-04-13 20:37 ` Paolo Bonzini
2016-04-13 18:20 ` Marc Haber
2016-03-21 9:08 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160423235759.GA25381@pd.tnic \
--to=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mh+linux-kernel@zugschlus.de \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).