From: "VanBaren, Gerald (AGRE)" <Gerald.VanBaren@smiths-aerospace.com>
To: <linuxppc-embedded@lists.linuxppc.org>,
"Joao Vicente" <joao.vicente@spectel.com>
Subject: RE: RAMDISK problem
Date: Thu, 20 Nov 2003 13:10:17 -0700 [thread overview]
Message-ID: <8039970AF146314597457D3B51A68B382DC11B@cossmgmbx02.email.corp.tld> (raw)
> -----Original Message-----
> From: Wolfgang Denk [mailto:wd@denx.de]
> Sent: Thursday, November 20, 2003 11:27 AM
> To: Joao Vicente
> Cc: linuxppc-embedded@lists.linuxppc.org
> Subject: Re: RAMDISK problem
>
>
>
> In message
> <DEF39A0710293E489D45B10E06645CBD02671CA2@dub-msx1.spectelcorp
> .com> you wrote:
> >
> > My problem is that I dont really know what address the core
> is trying to write to when the exception occurs.
> > As I mentioned in the previous message, the write() calls
> _syscall3() macro which will perform the write operation, but
> early in that macro the assembly 'sc' instruction is called.
> > As I cannot step through 'sc', I cannot go further on
> investigating at what write access the exception occurs.
>
> But you can set a breakpoint in the sc exception handler.
>
> > How do I even find out what is the start address of the
> file associated with the file descritor?
>
> Analyze at which offset the file starts in your filesystem image;
> find out the load address of the filesystem image in RAM; add the
> offset.
>
> Best regards,
>
> Wolfgang Denk
Hi Joao,
I assume you get a crash dump including the registers when it crashes. If not, you need a better debugger (BDI2000). If so, look at SRR0, SRR1, etc. Please read the PowerPC 603e User's Manual (assuming that is applicable: I forgot which processor you are using). For the 82xx (PPC603e core):
SRR0 = effective address for resuming program execution
SRR1 = MSR with some error identification bits
When you find the failure location, disassemble the memory leading up to the failure. Figure out which registers are being used for a memory access when the crash occurred, and find what those registers contained in the crash dump. That will tell you why the crash occurred (I'm guessing TEA, bit 13 in SRR1) and which address was at fault (load or store into a memory location, said memory location being one of the GPRs).
If your tools don't give you this information, you need to buy better tools.
gvb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-11-20 20:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 20:10 VanBaren, Gerald (AGRE) [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 13:53 ramdisk problem 刘彩苹
2003-11-20 15:34 RAMDISK problem Joao Vicente
2003-11-20 16:27 ` Wolfgang Denk
2003-11-19 19:49 VanBaren, Gerald (AGRE)
2003-11-19 19:13 Joao Vicente
2003-11-12 21:01 Jean-Denis Boyer
2003-11-12 21:29 ` Wolfgang Denk
[not found] <DEF39A0710293E489D45B10E06645CBD026719AB@dub-msx1.spectelcorp.com>
2003-11-12 19:45 ` Wolfgang Denk
2003-11-11 19:58 Steven Blakeslee
2003-11-11 15:44 Joao Vicente
2003-11-11 19:58 ` Wolfgang Denk
2003-03-13 9:38 RAMDISK Problem Kamalesh B
2003-03-03 12:19 Kamalesh B
2003-03-03 12:30 ` Wolfgang Denk
2002-06-13 15:20 Re: ramdisk problem somshekar chandrashekar kadam
2002-06-13 15:35 ` Wolfgang Denk
2002-06-13 13:43 somshekar chandrashekar kadam
2002-06-13 13:54 ` Wolfgang Denk
2002-06-13 11:14 somshekar chandrashekar kadam
2002-06-13 11:49 ` Wolfgang Denk
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=8039970AF146314597457D3B51A68B382DC11B@cossmgmbx02.email.corp.tld \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=joao.vicente@spectel.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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.