From: Borislav Petkov <bp@alien8.de>
To: Jeffrin Jose T <jeffrin@rajagiritech.edu.in>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
jpoimboe@redhat.com, mbenes@suse.cz,
"peterz@infradead.org" <peterz@infradead.org>,
shile.zhang@linux.alibaba.com,
lkml <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>
Subject: Re: Fwd: [WARNING AND ERROR] may be system slow and audio and video breaking
Date: Sun, 18 Oct 2020 23:03:23 +0200 [thread overview]
Message-ID: <20201018210323.GD8364@zn.tnic> (raw)
In-Reply-To: <328218dc46c4f883dad44d6fb53746c5f35f055d.camel@rajagiritech.edu.in>
On Mon, Oct 19, 2020 at 01:51:34AM +0530, Jeffrin Jose T wrote:
> On Sun, 2020-10-18 at 19:49 +0200, Borislav Petkov wrote:
> > On Sun, Oct 18, 2020 at 10:42:39PM +0530, Jeffrin Jose T wrote:
> > > smpboot: Scheduler frequency invariance went wobbly, disabling!
> > > [ 1112.592866] unchecked MSR access error: RDMSR from 0x123 at rIP:
> > > 0xffffffffb5c9a184 (native_read_msr+0x4/0x30)
Ok, you forgot to say in your initial mail that this happens when you
suspend your laptop.
Now, this unchecked MSR error thing happens only once because that early
during resume the microcode on CPU1 is not updated yet - and that needs
to be debugged separately and I'll try to reproduce that on my machine -
so the microcode is not updated yet and therefore the 0x123 MSR is not
"emulated" by the microcode, so to speak, thus the warning.
That warning doesn't happen anymore, though, once the microcode is
updated.
But what happens after that is you get a flood of correctable PCIe
errors about a transaction to a device timeoutting:
pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00001000/00002000
pcieport 0000:00:1c.5: [12] Timeout
and it looks like that flood is slowing down the machine because it is
busy logging them.
Do
# lspci -nn -xxx
as root. It'll show us which device that 8086:9d15 is.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-10-18 21:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 14:54 [WARNING AND ERROR] may be system slow and audio and video breaking Jeffrin Jose T
2020-10-18 17:12 ` Fwd: " Jeffrin Jose T
2020-10-18 17:49 ` Borislav Petkov
[not found] ` <328218dc46c4f883dad44d6fb53746c5f35f055d.camel@rajagiritech.edu.in>
2020-10-18 21:03 ` Borislav Petkov [this message]
2020-10-18 21:57 ` Jeffrin Jose T
2020-10-18 22:31 ` Borislav Petkov
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=20201018210323.GD8364@zn.tnic \
--to=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jeffrin@rajagiritech.edu.in \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=shile.zhang@linux.alibaba.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).