From: "" <simon@baydel.com>
To: linux-kernel@vger.kernel.org
Subject: halt and schedule
Date: Mon, 4 Nov 2002 09:40:59 -0000 [thread overview]
Message-ID: <3DC640AB.12893.F77CB@localhost> (raw)
I have been changing 2.4.19 to run on some new hardware, X86
based. The system boots and runs off a ramdisk. I am having
problems which I see as pauses. The system starts up and loads
the kernel. All seems ok until the ramdisk is mouned and INIT is
started. From this point on the system appears to stop responding
for a few seconds and then start again. Eventually, when logged in
command input can be slow with pauses between entering a
character and the console displaying the character.
I have tried to debug this and found that the kernel is in the
cpu_idle() routine which is repeatedly calling default_idle() and
safe_halt(). If you then type a character on the console, using a
scope, you can see the interrupt being serviced and a character
being taken from the RX fifo, quickly. However there is no
response for some seconds. I have also noticed that if you keep the
thing busy with a benchmark or something simple like ls -lR there is
no pause.
I noticed that to get out of this loop the kernel is looking for a
process to schedule. It is as if the process is not being scheduled
as soon as it could be.
One point to consider is that this board has no RTC or CTC just the
timer wired to a 10ms interrupt.
I suspect that this is a hardware problem but I don't really know
where to start looking. Can anyone help ?
Many thanks
Simon.
__________________________
Simon Haynes - Baydel
Phone : 44 (0) 1372 378811
Email : simon@baydel.com
__________________________
next reply other threads:[~2002-11-04 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 9:40 simon [this message]
2002-11-04 17:46 ` Richard B. Johnson
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=3DC640AB.12893.F77CB@localhost \
--to=simon@baydel.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
all inboxes | Powered by JetHome®