linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Dmytro Bablinyuk <dmytro.bablinyuk@tait.co.nz>
Cc: "Kevin A. Sapp" <Kevin.Sapp@catapult.com>,
	linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: RAMDISK Segv
Date: Thu, 04 Dec 2003 00:06:10 +0100	[thread overview]
Message-ID: <20031203230615.DECA4C5F5F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 04 Dec 2003 10:38:00 +1300." <3FCE57B8.1080508@tait.co.nz>


In message <3FCE57B8.1080508@tait.co.nz> you wrote:
>
> We had such problem with busybox and it was related to the buffer
> allocation policy (in busybox). We changed allocation policy from
> "Allocate with stack" to "Allocate with .bss" and problem gone.

The images have all been tested and are working fine here. It must be
a problem on Kevin's system - either memory map related, or the usual
culprit (SDRAM initialization).

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
There is an order of things in this universe.
	-- Apollo, "Who Mourns for Adonais?" stardate 3468.1

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-12-03 23:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 21:19 RAMDISK Segv Kevin A. Sapp
2003-12-03 21:38 ` Dmytro Bablinyuk
2003-12-03 23:06   ` Wolfgang Denk [this message]
2003-12-03 23:05 ` Wolfgang Denk
     [not found] <3FCF1BB0.9060005@catapult.com>
2003-12-04 11:43 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-12-04 21:13 Jean-Denis Boyer

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=20031203230615.DECA4C5F5F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=Kevin.Sapp@catapult.com \
    --cc=dmytro.bablinyuk@tait.co.nz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).