All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anjali Kulkarni" <anjali@indranetworks.com>
To: Richard Zidlicky 
	<Richard.Zidlicky@stud.informatik.uni-erlangen.de>,
	Anjali Kulkarni <anjali@indranetworks.com>,
	mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: scheduler problems
Date: Wed, 12 Jun 2002 22:38:37 -0700	[thread overview]
Message-ID: <200206130538.WAA18419@eagle.he.net> (raw)



> > > > [...] It is due to the fact that the schedule() function does 
not 
> > find
> > > > the 'current' process in the runqueue. [...]
> > > 
> > > a crash in line 384 means that the runqueue got corrupted by 
> > something,
> > > most likely caused by buggy kernel code outside of the scheduler.
> > 
> > Right, I thought of that, but how is it that it gets corrupt at 
exactly 
> > the same offset in task_struct of that process and every time with 
> > different processes? (I have run it atleast 20-30 times). And it 
just 
> > doesnt come if I kill the process in question? 
> 
> I've had similar problems when some code invalidated CPU cache 
> and an interrupt came in at the wrong time.
> 

Hi!

I have not very clear on what u mean. Can u explain in more detail?

Thanks,
Anjali

> Richard
> 
> 


Anjali Kulkarni
Software Engineer
Indra Networks

~Living Well is the best Revenge~

             reply	other threads:[~2002-06-13  5:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13  5:38 Anjali Kulkarni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-12  7:14 scheduler problems Anjali Kulkarni
2002-06-12 10:20 ` Richard Zidlicky
2002-06-12  5:20 Anjali Kulkarni
2002-06-12  6:20 ` Ingo Molnar

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=200206130538.WAA18419@eagle.he.net \
    --to=anjali@indranetworks.com \
    --cc=Richard.Zidlicky@stud.informatik.uni-erlangen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.