From: Russell King <rmk@arm.linux.org.uk>
To: rpm <rajendra.mishra@timesys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ADS GCP reboots when running the application!
Date: Tue, 14 May 2002 10:29:01 +0100 [thread overview]
Message-ID: <20020514102901.A17054@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200205131138.g4DBcU526690@localhost.localdomain> <20020513173714.F6024@flint.arm.linux.org.uk> <200205140911.g4E9B7624219@localhost.localdomain>
On Tue, May 14, 2002 at 02:41:06PM +0530, rpm wrote:
> On Monday 13 May 2002 10:07 pm, Russell King wrote:
> > 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 !
You're right in the x86 case, but wrong in the ARM case - you just take a
fault after fault after fault (and you'll either end up overwriting the
kernel or something else of that nature).
> so i conclude that the system crashes in brk() sys call !
strace would print 'brk(' on entry to the syscall though.
> If you can point out the cases where the kernel reboots without showing
> any message , then it will be easier to debug for me!
Well, if I knew of any, they'd get removed/fixed pretty damned fast.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
prev parent reply other threads:[~2002-05-14 9:29 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
2002-05-14 9:29 ` 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=20020514102901.A17054@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rajendra.mishra@timesys.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