From: Punit Agrawal <punitagrawal@gmail.com>
To: Pierre FICHEUX <pierre.ficheux@smile.fr>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>,
linux-rt-users@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Strange problem with PREEMPT_RT
Date: Fri, 01 Oct 2021 08:40:25 +0900 [thread overview]
Message-ID: <871r554opi.fsf@stealth> (raw)
In-Reply-To: <CAFc1U0sYdJQWkeLgPjiR1Y1CnafV22zgS4AW0Yf6+h7CO03u+g@mail.gmail.com> (Pierre FICHEUX's message of "Thu, 30 Sep 2021 16:31:25 +0200")
Please don't top-post[0] - it makes it harder to reply with context from
previous emails. Kernel related mailing lists tend to prefer
bottom-posting[1].
Pierre FICHEUX <pierre.ficheux@smile.fr> writes:
> # cpupower -c all idle-info
> CPUidle driver: none
> CPUidle governor: menu
> analyzing CPU 0:
>
> CPU 0: No idle states
> ...
> same for all cpus.
It looks like cpuidle may not be to blame for your woes.
One last thing to check regarding idle (call me paranoid) would be to
see if there's an option to disable C-states in bios. Not being familiar
with your system, it would be useful to rule out any firmware driven
idle management.
Barring that, maybe look into upgrading to a newer kernel if possible.
[0] https://en.wikipedia.org/wiki/Posting_style#Top-posting
[1] https://en.wikipedia.org/wiki/Posting_style#Bottom-posting
[...]
next prev parent reply other threads:[~2021-09-30 23:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 16:40 Strange problem with PREEMPT_RT Pierre FICHEUX
2021-09-30 0:13 ` Punit Agrawal
2021-09-30 8:21 ` Pierre FICHEUX
2021-09-30 13:17 ` Luis Goncalves
2021-09-30 13:18 ` Sebastian Andrzej Siewior
2021-09-30 13:23 ` Sebastian Andrzej Siewior
2021-09-30 13:26 ` Pierre FICHEUX
2021-09-30 13:51 ` Sebastian Andrzej Siewior
2021-09-30 14:31 ` Pierre FICHEUX
2021-09-30 23:40 ` Punit Agrawal [this message]
2021-10-03 11:11 ` Jack Winch
2021-10-04 12:54 ` John Kacur
2021-10-18 9:12 ` Sebastian Andrzej Siewior
2021-09-30 13:41 ` John Ogness
2021-09-30 14:25 ` John Kacur
2021-09-30 15:02 ` John Ogness
2021-09-30 15:49 ` Sebastian Andrzej Siewior
2021-09-30 16:16 ` John Kacur
2021-09-30 23:22 ` Punit Agrawal
2021-09-30 14:59 ` John Kacur
2021-09-30 23:01 ` Punit Agrawal
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=871r554opi.fsf@stealth \
--to=punitagrawal@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=pierre.ficheux@smile.fr \
--cc=tglx@linutronix.de \
--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