public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: terry <gliumailenator@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Hanging in kmalloc of nand_scan_tail() function
Date: Fri, 12 Nov 2010 20:45:18 +0800	[thread overview]
Message-ID: <1289565918.2044.7.camel@terry> (raw)
In-Reply-To: <20101111134949.08c6a157@udp111988uds.am.freescale.net>

Dear Scott,
	I have disassemble the nand_base.o file,because i know the problem
happened here. Do you think it's useful for your analysis?

00001a4c <nand_scan_tail>:
 1749     1a4c:   e92d4070    push    {r4, r5, r6, lr}
 1750     1a50:   e590509c    ldr r5, [r0, #156]
 1751     1a54:   e595304c    ldr r3, [r5, #76]
 1752     1a58:   e3130701    tst r3, #262144 ; 0x40000
 1753     1a5c:   e1a06000    mov r6, r0
 1754     1a60:   1a000002    bne 1a70 <nand_scan_tail+0x24>
 1755     1a64:   e59f04ec    ldr r0, [pc, #1260] ; 1f58 <nand_scan_tail
+0x50c>
 1756     1a68:   ebfffffe    bl  0 <malloc>
 1757     1a6c:   e58500dc    str r0, [r5, #220]
 1758     1a70:   e59510dc    ldr r1, [r5, #220]
 1759     1a74:   e3510000    cmp r1, #0  ; 0x0
 1760     1a78:   03e0000b    mvneq   r0, #11 ; 0xb
 1761     1a7c:   08bd8070    popeq   {r4, r5, r6, pc}
 1762     1a80:   e5963014    ldr r3, [r6, #20]
 1763     1a84:   e59520b0    ldr r2, [r5, #176]
 1764     1a88:   e0813003    add r3, r1, r3
by the way,I cann't find the prototype of malloc in the whole project,it
seems that it is encapsulated in some libs.
--
Best regards,
Terry.

? 2010-11-11?? 13:49 -0600?Scott Wood???
> On Thu, 11 Nov 2010 23:06:01 +0800
> terry <gliumailenator@gmail.com> wrote:
> 
> > Dear everyone,
> > I'm using u-boot-2010.09. After I download u-boot.bin to my boards(cpu
> > is s3c2410),the output from serial shows that cpu has exception, the
> > information list as following:
> > U-Boot 2010.09 (Nov 11 2010 - 21:55:07)
> > 
> > U-Boot code: 33F80000 -> 33FA0BDC  BSS: -> 33FA45EC
> > RAM Configuration:
> > Bank #0: 30000000 64 MiB
> > NAND:  data abort
> > pc : [<33f8fbb4>]          lr : [<33f85f70>]
> > sp : 33f07fac  ip : 00000000     fp : 00000000
> > r10: 00001298  r9 : ffffff7f     r8 : 33f4ffe0
> > r7 : 00000000  r6 : 33fa3b50     r5 : 33fa3c00  r4 : 33fa0274
> > r3 : 33f9ff54  r2 : 00000064     r1 : 00000001  r0 : cc33cc33
> > Flags: NzCv  IRQs off  FIQs off  Mode SVC_32
> > Resetting CPU ...
> > 
> > value of pc locate at <malloc> function, value of lr locate at
> > <nand_scan_tail>(/drivers/mtd/nand/nand_base.c).
> 
> Could you look up the specific line numbers of
> 0x33f8fbb4 and 0x33f85f6c, and show a few lines of disassembly around
> those addresses?
> 
> -Scott
> 

-- 
Best regards,
terry

  reply	other threads:[~2010-11-12 12:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 15:06 [U-Boot] Hanging in kmalloc of nand_scan_tail() function terry
2010-11-11 19:49 ` Scott Wood
2010-11-12 12:45   ` terry [this message]
2010-11-12 17:19     ` Scott Wood
2010-11-13  3:43       ` terry
2010-11-13 16:24         ` Kumar Gala
2010-11-14 13:18           ` terry
2010-11-15 15:05             ` Kumar Gala
2010-11-15 17:42         ` Scott Wood
  -- strict thread matches above, loose matches on Subject: below --
2009-09-18  4:17 J.Hwan.Kim
2009-09-18 17:52 ` Scott Wood

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=1289565918.2044.7.camel@terry \
    --to=gliumailenator@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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