From: Martin Peck <coderman@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Longhaul cpu frequency scaling leads to segmentation violation in userspace
Date: Fri, 24 Sep 2004 10:49:29 -0700 [thread overview]
Message-ID: <4ef5fec604092410491fbae33b@mail.gmail.com> (raw)
I have encountered a strange scenario using 2.6.8.1 on a VIA C5P
mini-itx system when Longhaul CPU frequency scaling is enabled.
When filling a buffer with entropy via xstore in kernel space a tight
loop can be performed without any problems.
If the xstore is invoked in the same iterative manner in user space
for a sufficient number of iterations (~ 120 or more) the application
is terminated due to a segmentation violation.
Adding a short delay between iterations or turning off CPU frequency
scaling resolves the problem.
Is there something associated with CPU frequency scaling and processor
intensive operations in user space that leads to unexpected timeslice
overrun (or any other side effect) causing a segmentation violation?
This behavior is very strange; any insight would be appreciated.
Regards,
reply other threads:[~2004-09-24 17:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4ef5fec604092410491fbae33b@mail.gmail.com \
--to=coderman@gmail.com \
--cc=linux-kernel@vger.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