Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] ramdisk building issue
Date: Fri, 20 Apr 2007 13:14:13 +0200	[thread overview]
Message-ID: <20070420111413.GA15091@aon.at> (raw)
In-Reply-To: <255259.71430.qm@web15811.mail.cnb.yahoo.com>

On Fri, Apr 20, 2007 at 05:36:31PM +0800, Jinag Robert wrote:
>Hi, All,
>
>I built ramdisk for a ARM 920T board on  a RedHat 2.6.9-34.ELsmp server. 
>But after booting up, following message was printed repeatedly:
># attempt to access beyond end of device
>ram0: rw=0, want=65734, limit=65536
>
>The ramdisk is c create by "genext2fs" command 
>and the "genext2fs" is created during building process. 
>
>I tried on three other linux boxes,  and couldn't  reproduce this problem.
>Build server    Host GCC version           Ramdisk.gz size      Bug status
>2.6.9-42.0.3.ELsmp  gcc 3.4.6              11615252             Passed
>Fedora Core 4   gcc 4.0.2                  11624291             Passed
>2.6.9-34.ELsmp  gcc 3.4.5                  11661380             Failed
>Fedora Core 3   gcc 3.4.2                  11613082             Passed
>
>I updated 2.6.9-34.ELsmp server's GCC and binutils and rebuilt again, 
>the dirty message is still printed.
>
>
>And idea that how I will fix this problem ? 

Wrong list. Better ask the redhat people. Alternatively, this one works
for me:
http://www.debian.org/CD/netinst/

  reply	other threads:[~2007-04-20 11:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20  9:36 [Buildroot] ramdisk building issue Jinag Robert
2007-04-20 11:14 ` Bernhard Fischer [this message]
2007-04-21  2:47   ` [Buildroot] buildroot compile error nina.holly at aerende.com

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=20070420111413.GA15091@aon.at \
    --to=rep.dot.nop@gmail.com \
    --cc=buildroot@busybox.net \
    /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