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>
Subject: Re: Fwd: [WARNING AND ERROR] may be system slow and audio and video breaking
Date: Sun, 18 Oct 2020 19:49:48 +0200 [thread overview]
Message-ID: <20201018174948.GC8364@zn.tnic> (raw)
In-Reply-To: <b4533bcbb095cf11f01d0adfd50912c52242eb02.camel@rajagiritech.edu.in>
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)
> [ 1112.592869] Call Trace:
> [ 1112.592876] update_srbds_msr+0x6f/0xb0
> [ 1112.592880] smp_store_cpu_info+0x8e/0xb0
> [ 1112.592883] start_secondary+0x93/0x200
> [ 1112.592887] ? set_cpu_sibling_map+0xcb0/0xcb0
> [ 1112.592891] secondary_startup_64+0xa4/0xb0
> [ 1112.592898] unchecked MSR access error: WRMSR to 0x123 (tried to
> write 0x0000000000000000) at rIP: 0xffffffffb5c9a264
> (native_write_msr+0x4/0x20)
> [ 1112.592899] Call Trace:
> [ 1112.592902] update_srbds_msr+0x98/0xb0
> [ 1112.592904] smp_store_cpu_info+0x8e/0xb0
> [ 1112.592907] start_secondary+0x93/0x200
> [ 1112.592911] ? set_cpu_sibling_map+0xcb0/0xcb0
> [ 1112.592914] secondary_startup_64+0xa4/0xb0
> [ 2915.106879] show_signal: 6 callbacks suppressed
> [ 6089.209343] WARNING: stack going in the wrong direction? at
> i915_gem_close_object+0x2fb/0x560 [i915]
This looks strange.
Please send
- full dmesg
- output from the "grep -r . /sys/devices/system/cpu/vulnerabilities/" command
- /proc/cpuinfo
- .config
Privately is fine too.
> -----------------x---------------x----------------x------------
> Linux debian 5.9.1-rc1+ #4 SMP Fri Oct 16 16:48:04 IST 2020 x86_64
What kernel is that exactly?
Can you reproduce with plain v5.9 too?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-10-18 17:50 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 [this message]
[not found] ` <328218dc46c4f883dad44d6fb53746c5f35f055d.camel@rajagiritech.edu.in>
2020-10-18 21:03 ` Borislav Petkov
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=20201018174948.GC8364@zn.tnic \
--to=bp@alien8.de \
--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=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).