From: "John B. Wyatt IV" <jwyatt@redhat.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Petr Mladek <pmladek@suse.com>,
Clark Williams <williams@redhat.com>,
jlelli@redhat.com, Derek Barbosa <debarbos@redhat.com>,
"John B. Wyatt IV" <sageofredondo@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: NMI Reported with console_blast.sh
Date: Mon, 12 Feb 2024 16:23:04 -0500 [thread overview]
Message-ID: <ZcqMOKtHsZ9qnxNg@thinkpad2021> (raw)
In-Reply-To: <87a5o8j9gp.fsf@jogness.linutronix.de>
On Sat, Feb 10, 2024 at 10:33:50PM +0106, John Ogness wrote:
> On 2024-02-09, "John B. Wyatt IV" <jwyatt@redhat.com> wrote:
> >> Could you provide me your kernel config and boot args?
>
> Thanks for the config. Could you provide me the boot args as well? I am
> trying to understand why early_printk is showing up in your trace.
I forgot to include that, my apologies.
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.7.0-rt6 root=UUID=6e05c61a-a39c-45f1-acf2-0b0892c0739e ro rootflags=subvol=root console=ttyS0,115200n81 skew_tick=1 tsc=reliable rcupdate.rcu_normal_after_boot=1 isolcpus=managed_irq,domain,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223 intel_pstate=disable nosoftlockup
I talked about the isolcpus options with Juri. Tuned had the realtime profile enabled. Juri suggested testing with the thoughput-performance profile.
Red Hat's conservers are having an issue with the machine I was testing
on. It may take me a while to get back to you with more test results.
next prev parent reply other threads:[~2024-02-12 21:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 0:43 NMI Reported with console_blast.sh John B. Wyatt IV
2024-02-09 9:11 ` John Ogness
2024-02-09 20:50 ` John B. Wyatt IV
2024-02-10 21:27 ` John Ogness
2024-02-12 21:23 ` John B. Wyatt IV [this message]
2024-02-22 5:21 ` John B. Wyatt IV
2024-02-29 11:15 ` Petr Mladek
2024-02-29 11:19 ` Petr Mladek
2024-03-01 10:11 ` Sebastian Andrzej Siewior
2024-03-01 16:53 ` John B. Wyatt IV
2024-02-20 22:24 ` John B. Wyatt IV
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=ZcqMOKtHsZ9qnxNg@thinkpad2021 \
--to=jwyatt@redhat.com \
--cc=debarbos@redhat.com \
--cc=jlelli@redhat.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=sageofredondo@gmail.com \
--cc=williams@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