From: "Arthur Naseef" <artn@home.com>
To: <linux-kernel@vger.kernel.org>
Subject: Kernel 2.2: tq_scheduler functions scheduling and waiting
Date: Mon, 28 May 2001 15:19:17 -0400 [thread overview]
Message-ID: <BGEHKJAIFDCFCMFALMGPIEHACAAA.artn@home.com> (raw)
All:
I have been diagnosing kernel panics for over a week and I have
concerns with the use of tq_scheduler for which I was hoping I
could get some assistance.
Is it considered acceptable for functions in the tq_scheduler
task list to call schedule? Is it acceptable for such functions
to wait on wait queues? What limitations exist?
As near as I can determine, the TTY driver code makes use of
the tq_scheduler list for such purposes.
In my testing, I am running with 96 TTY devices (talking to a
high-density modem card) and I consistently achieve kernel panics
when the system is under heavy swapping. I am continuing to
diagnose the problem. The kernel panics are triggered mostly in
goodness() and del_from_runqueue(), as indicated by ksym_oops and
gdb, and I suspect the run queue is getting corrupted.
In spite of this testing, I believe that I have an argument against
tq_scheduler functions waiting on wait queues, but I have not
thoroughly convinced myself that (a) this was not already known,
and (b) this is already happening in existing kernel code.
Any help is greatly appreciated.
-art
Arthur Naseef
P.S. If this information is availed through existing documentation,
searches, or other widely available resources, I would greatly
appreciate references to this material. All of my searches to
date have yielded few results and nothing definitive.
next reply other threads:[~2001-05-28 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 19:19 Arthur Naseef [this message]
2001-05-29 2:27 ` Kernel 2.2: tq_scheduler functions scheduling and waiting Andrew Morton
2001-05-29 11:21 ` Arthur Naseef
2001-05-29 11:25 ` Andrew Morton
2001-05-30 1:16 ` Arthur Naseef
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=BGEHKJAIFDCFCMFALMGPIEHACAAA.artn@home.com \
--to=artn@home.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