linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "OTAVIO ISAMU SUGENO" <otavio.sugeno@siemens.com.br>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: CPU performance measurement
Date: Tue, 23 Jul 2002 23:14:04 +0200	[thread overview]
Message-ID: <20020723211409.9635F10875@denx.denx.de> (raw)
In-Reply-To: Your message of "Tue, 23 Jul 2002 17:56:57 -0300." <B7AC573479F05C438F232539B961A168095007@CUR1006V.br002.siemens.net.br>


Dear OtavioOtavio,

in message <B7AC573479F05C438F232539B961A168095007@CUR1006V.br002.siemens.net.br> you wrote:
>
> >>You did mount the /proc filesystem, didn't you?
> I though /proc filesystem was mounted but it is not. My custom board is

Ummm.. I guess you have a login or any other way to access a shell on
your board? You can (and should) manually check which filesystems are
mounted, and mount anything that may be missing.

> running a 6MB ramdisk and I receive the following message when Linux
> goes up:
>
> EXT-f2 warning: mounting unchecked fs, running e2fsck is recommended

This is harmless - just an indication that  your  way  to  build  the
ramdisk image is more or less broken.

> VFS: Mounted root (ext2 filesystem)
> Freeing unused kernel memory: 60k init 4k openfirmware
> INIT; version 2.78 booting
> Checking all file systems...
> Parallelizing fsck version 1.19(13-jul-2000)
> Mounting local filesystems...
> Not mounted anuthing

To me this seems pretty much overkill for a ramdisk  of  an  embedded
system;  have  a  look  how  we  do this in our Simple Embedded Linux
Framework, see ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/

> I tried to run e2fsck but no success. Any idea what can I do to fix fs?

Fix the the build process for your ramdisk image.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
I used to be indecisive, now I'm not sure.

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

       reply	other threads:[~2002-07-23 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B7AC573479F05C438F232539B961A168095007@CUR1006V.br002.siemens.net.br>
2002-07-23 21:14 ` Wolfgang Denk [this message]
2002-07-22 18:30 CPU performance measurement OTAVIO ISAMU SUGENO
2002-07-22 18:49 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2002-07-22 11:01 OTAVIO ISAMU SUGENO
2002-07-22 17:27 ` 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=20020723211409.9635F10875@denx.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=otavio.sugeno@siemens.com.br \
    /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).