mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Liu haixiang <liu.haixiang@gmail.com>
Cc: Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Question on Schedule and Preemption
Date: Tue, 18 Apr 2006 13:32:56 -0400	[thread overview]
Message-ID: <1145381576.17085.138.camel@localhost.localdomain> (raw)
In-Reply-To: <bf3792800604181021y4d985dedk19c7d94707c0cd8d@mail.gmail.com>

On Wed, 2006-04-19 at 01:21 +0800, Liu haixiang wrote:
> 2006/4/18, Steven Rostedt <rostedt@xxxxxx.com>:

Damn! I used my work email account to send that. I try to keep the spam
down on that account, so I don't publish it as much. Darn Evolution
keeps picking the wrong account.

> > On Tue, 2006-04-18 at 20:55 +0800, Liu haixiang wrote:
> >
> > Well according to your output, it was the task "TURNER0" with the pid
> > 611.  After you recompile the kernel with CONFIG_FRAME_POINTERS you will
> > need to follow the stack trace and see what function turned off
> > preemption.  This can happen calling a spin_lock and not unlocking it
> > before calling something that would schedule.
> >
> 
> If it's true, it is a great help for me.
> 
> > If you also turn on in "Kernel Hacking" -> "Compile the kernel with
> > debug info", you can then do a "gdb vmlinux" in the root directory of
> > the compile, and pass in the stack address with the command
> > "li *0xc042382e" to show where that function would return. (replace the
> > c042382e with the location you are looking for).
> >
> > Also, what arch are you using to get a 0x04000000 in the preempt_count
> > (the 0x1 is the depth). Of course I'm looking at 2.6.17-rc1 and not the
> > one you are using.  Hmm, your arch may not even support frame pointers.
> >
> > -- Steve
> >
> 
> The arch is SH4.

Well I just tried a "make ARCH=sh menuconfig" and the
CONFIG_FRAME_POINTERS option is there.  Whether it makes a difference or
not, I haven't the foggiest clue.

-- Steve



  reply	other threads:[~2006-04-18 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18  7:23 Liu haixiang
2006-04-18  9:17 ` Andreas Mohr
2006-04-18  9:23   ` Arjan van de Ven
2006-04-18  9:28     ` Andreas Mohr
2006-04-18 12:55   ` Liu haixiang
2006-04-18 14:56     ` Steven Rostedt
2006-04-18 17:21       ` Liu haixiang
2006-04-18 17:32         ` Steven Rostedt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-18 13:31 Michael Guo
2006-04-18  7:12 Liu haixiang

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=1145381576.17085.138.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=andi@rhlx01.fht-esslingen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liu.haixiang@gmail.com \
    /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®