From: Russell King <rmk+lkml@arm.linux.org.uk>
To: railroad seeker <railroad.seeker@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scheduling in interrupt and call trace
Date: Mon, 19 Mar 2007 12:41:14 +0000 [thread overview]
Message-ID: <20070319124114.GA13850@flint.arm.linux.org.uk> (raw)
In-Reply-To: <6eb6ed920703190537o3c4738d6l61dd946d9554b4a3@mail.gmail.com>
On Mon, Mar 19, 2007 at 08:37:57PM +0800, railroad seeker wrote:
> After that, the program counter must located in BUG(), that is something
> like
> "(void *)0 = 0" if we really do scheduling in interrupt contxt, and
> should cause
> the kernel to panic. However, what i got is that the latest program
> counter is located within the do_IRQ() context when the kernel was
> crashed . But it
> seems that the stack trace is a kernel stack of process context since
> the bottom of the stack is ret_from_syscall. (I have not enabled the
> frame pointer when compiling the kernel, instead, I back traced by
> manually inspect each 32 bit value
> from the output of objdump) , and I think that the latest PC should
> point to the next instruction of "(void *) 0 = 0".
>
> Is there any possibility with which we got this incorrect information,
> or I have
> misunderstanding about "kernel system to interrupt context switch?
Please enable frame pointers and show the resulting backtrace; it is
possible that trying to manually decode the stack without frame
pointers enabled will result in a confused backtrace.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
prev parent reply other threads:[~2007-03-19 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 12:37 Scheduling in interrupt and call trace railroad seeker
2007-03-19 12:41 ` Russell King [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=20070319124114.GA13850@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=railroad.seeker@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 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.