public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: J.Hwan.Kim <frog1120@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Hanging in kmalloc of nand_scan_tail() function
Date: Fri, 18 Sep 2009 13:17:48 +0900	[thread overview]
Message-ID: <4AB309EC.5030605@gmail.com> (raw)

Hi, everyone

I'm using U-boot 2009-03.
U-boot hangs in nand_init() function.
I found the routine kmalloc in nand_scan_tail() cause U-boot reset.


int nand_scan_tail(struct mtd_info *mtd)
{
    int i;
    struct nand_chip *chip = mtd->priv;

    if (!(chip->options & NAND_OWN_BUFFERS)) {
        chip->buffers = kmalloc(sizeof(*chip->buffers), GFP_KERNEL);   
    }

    if (!chip->buffers)
        return -ENOMEM;
              ........


U-boot displays message as follows :

NAND:  data abort
pc : [<31f902b4>]\0x09   lr : [<31fa084c>]
sp : 31f5bee0  ip : 00000076\0x09 fp : 00000000
r10: 00001188  r9 : 00020000\0x09 r8 : 31f5bfdc
r7 : 00000001  r6 : 00000000\0x09 r5 : 31fa42b8  r4 : 31fa4364
r3 : 31fa052c  r2 : 00000064\0x09 r1 : 00000063  r0 : ffffffff
Flags: NzCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...


Where the malloc function is defined?
Why the kmalloc() hangs the u-boot?
Is there any configuation definition needed?

Thanks in advance.

Regards,
J.Hwan Kim

             reply	other threads:[~2009-09-18  4:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18  4:17 J.Hwan.Kim [this message]
2009-09-18 17:52 ` [U-Boot] Hanging in kmalloc of nand_scan_tail() function Scott Wood
  -- strict thread matches above, loose matches on Subject: below --
2010-11-11 15:06 terry
2010-11-11 19:49 ` Scott Wood
2010-11-12 12:45   ` terry
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

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=4AB309EC.5030605@gmail.com \
    --to=frog1120@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