public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Zick" <mszick@goquest.com>
To: anton wilson <anton.wilson@camotion.com>, linux-kernel@vger.kernel.org
Subject: Re: printks in the scheduler freeze during scripts
Date: Fri, 28 Jun 2002 06:56:15 -0500	[thread overview]
Message-ID: <02062806561501.00733@localhost.localdomain> (raw)
In-Reply-To: <200206271349.JAA16318@test-area.com>

On Thursday 27 June 2002 09:03 am, anton wilson wrote:
> I'm running linux 2.4.17 and Redhat 7.2 with the preemptive and low latency
> patches, and whenever I stick printks in the scheduler(void) my system
> freezes somewhere after it tries to load the system font. Where it stops
> seems to be random. I can only run under single user mode without my system
> freezing. Does anyone have any clues why? Or any better ways to go about
> tracking the scheduling of processes in the scheduler?

Something I have used in my testing:

Add, in the task structure:

task_t  *sched_from;

In schedule, prior to context_switch:

next->sched_from = prior; /* at this point still == get_current ()*/

Somewhere else (so you don't inadvertantly side-effect to death schedule()):

Follow the back-link and printk whatever for the task that you are interested 
in, being careful not to reference task structures that no longer exist.

Mike
>
>
> Anton

      parent reply	other threads:[~2002-06-28 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27 14:03 printks in the scheduler freeze during scripts anton wilson
2002-06-27 14:15 ` Andrew Morton
2002-06-28 11:56 ` Michael S. Zick [this message]

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=02062806561501.00733@localhost.localdomain \
    --to=mszick@goquest.com \
    --cc=anton.wilson@camotion.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