linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..
Date: Wed, 4 Nov 2009 14:15:01 +0100	[thread overview]
Message-ID: <20091104131500.GZ14091@buzzloop.caiaq.de> (raw)
In-Reply-To: <OF15AFD08D.F28F9544-ON65257664.002A1275-65257664.002A127F@tcs.com>

On Wed, Nov 04, 2009 at 01:09:32PM +0530, Vadivelan M wrote:
>      I am porting Linux-2.6.28 Kernel on IMX27based board.
>      Filesystem is mounted and after that we are getting message Freeing init
>      memory and some junk characters are coming. Keyboards are responding.
>      Can anybody help us in this regard.
> 
>      Thanks,
> 
>      Please see the following logs ..
> 
>      Launch LinuxUncompressing
>      Linux......................................................................
>      done, booting the kernel.
>      Linux version 2.6.28-arm2 (root at localhost.localdomain) (gcc version
>      4.1.1) #75 Wed Oct 28 13:12:53 IST 2009
>      CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177
>      CPU: VIVT data cache, VIVT instruction cache
>      Machine: Freescale i.MX27ADS
>      Kernel command line: root=/dev/ram rw mem=64M console=ttymxc0,115200

Your kernel uses 115200 baud to output these messages ...

[...]

>      EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
>      VFS: Mounted root (ext2 filesystem).
>      Freeing init memory: 92K
> 
>      After this some junk characters are coming like ....
> 
>      &#65533;&#65533;&#1421;&#65533;&#531488;0^&#1949;&#65533;&#65533;r&#65533;'&#65533;&#65533;&#65533;j&#65533;&#65533;r:&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;&#65533;:&#65533;&#65533;M&#65533;.&#65533;&#65533;D&#65533;d&#65533;z.?&#65533;&#65533;.T&#65533;&#65533;8V&#65533;`&#65533;T&#65533;&#65533;&#65533;V&#51082;]nn]^&#65400;&#65533;m8m&#65533;&#65533;^&#65533;.&#65533;m&#65533;.E&#65533;&#65533;N&#65533;&#65533;8&#65533;&#65533;6&#65533;&#65533;&#65533;:]&#65533;&#65533;&#65533;

... and in your inittab, there seems to be a getty registered which
operates at a different speed. Change either of the two and you should
be fine.

Daniel

  reply	other threads:[~2009-11-04 13:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04  7:39 imx27 - hanging at freeing init memory -- getting some junk characters here after on console Vadivelan M
2009-11-04 13:15 ` Daniel Mack [this message]
2009-11-06  5:42   ` Vadivelan M
2009-11-10  6:49     ` Daniel Mack
2009-11-10  9:14       ` Andy Green
2009-11-17  4:04       ` Vadivelan M
2009-11-17  7:17         ` Daniel Mack
2009-11-17  8:27           ` Vadivelan M
2009-11-17  9:17             ` Daniel Mack
2009-11-17 11:59               ` Vadivelan M
2009-11-17 12:39                 ` Daniel Mack
2009-11-23 17:07                   ` Martin Fuzzey
2009-11-23 20:02                     ` Eric Bénard
     [not found] ` <OFEF3C8131.8C4BB129-ON65257665.003C2B08-65257665.003C2B0A@tcs.com>
2009-11-05 11:07   ` Daniel Mack
2009-12-05 15:15 ` Subramani Venkatesh

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=20091104131500.GZ14091@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=linux-arm-kernel@lists.infradead.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).