From: rpm <rajendra.mishra@timesys.com>
To: Russell King <rmk@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ADS GCP reboots when running the application!
Date: Tue, 14 May 2002 14:41:06 +0530 [thread overview]
Message-ID: <200205140911.g4E9B7624219@localhost.localdomain> (raw)
In-Reply-To: <200205131138.g4DBcU526690@localhost.localdomain> <20020513173714.F6024@flint.arm.linux.org.uk>
On Monday 13 May 2002 10:07 pm, Russell King wrote:
> On Mon, May 13, 2002 at 05:08:30PM +0530, rpm wrote:
> > The kernel is not showing any OOPS or panic , it just reboots !
>
> Weird. Tried any more recent kernels?
>
> > what i think is that some double fault ( fault inside fault handler )
>
> No such thing on ARMs. If you take a fault while handling one, you
> re-enter the fault handler - you don't reboot.
>
What if the fault handler does a fault ( like seg fault in seg fault handler
) , cause in i386, i remember such a situation causes a processor reboot as
it becomes a infinite loop !
the same code works fine on an iPAQ ! without any problems
and i did a diff of the strace output on iPAQ and GCP and found that the
following lines are extra in case of iPAQ while GCP reboots before it can
print the lines !
***************************************
brk(0xc8000) = 0xc8000
close(4) = 0
close(3) = 0
munmap(0x40000000, 4096) = 0
_exit(0) = ?
*****************************************
so i conclude that the system crashes in brk() sys call !
If you can point out the cases where the kernel reboots without showing any
message , then it will be easier to debug for me!
and thanks a lot for the reply :)
rpm
next prev parent reply other threads:[~2002-05-14 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 11:38 ADS GCP reboots when running the application! rpm
2002-05-13 16:37 ` Russell King
2002-05-14 9:11 ` rpm [this message]
2002-05-14 9:29 ` Russell King
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=200205140911.g4E9B7624219@localhost.localdomain \
--to=rajendra.mishra@timesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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