imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Vadivelan M]

An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091104/6c3ef607/attachment.htm>

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Daniel Mack]

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 ....
> 
>      ��֍�򁰠0^ޝ��r�'���j��r:�������:��M�.��D�d�z.?��.T��8V�`�T���V잊]nn]^ｸ�m8m��^�.�m�.E��N��8��6���:]���

... 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

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Daniel Mack]

(Please do not remove anyone from Cc and do not post on top when
replying)

On Thu, Nov 05, 2009 at 04:27:11PM +0530, Prabha J wrote:
>    But in inittab ,we are not using any getty.

What you see is certainly not a crash - something obviously just changes
the baudrate. If you're not using getty, it's something else. Try
adding 'init=/bin/sh' to your kernel command line. That should dump you
directly to a shell without any further startup script processing. If
that works, your problem is not related to the kernel.

>    One more thing,
>    We have Linux-2.6.19.2 which is working on this board and we are using the
>    same root filesystem and the toolchain used also same.
>    We checked the clock and baudrate ,and it is correct.

Maybe the baud rate configured in the older kernel is different?
I don't know.

>    What else may be the problem.
>    Are we missing any configuration?
>    Between linux-2.6.19.2 and linux-2.6.28 there is lot of changes. Do we
>    have to change anything in the driver.

Which driver do you mean?

Daniel

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Vadivelan M]

An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091106/99f0c1b6/attachment-0001.htm>

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Daniel Mack]

On Fri, Nov 06, 2009 at 11:12:03AM +0530, Vadivelan M wrote:
>    I have checked the inittab. the baud rate is correct.
> 
>    When i am passing command line arguments "init=bin/sh
>    consloe=ttymxc0,115200 root=/dev/ram rw ip=off"
> 
>    same status. i can see the print Freeing init memory and some uart
>    function prints...
> 
>    After that only junk characters are coming.
> 
>    we have checked serial drivers . almost no changes between 2.6.19(working
>    kernel) and 2.6.27
> 
>    Please help us to go forward.....

Sorry, I don't know then. I was sure you're facing a baud rate issue,
which also is a common pitfall.

Can you try using a current mainline git kernel and see if the problem
persists? Your machine type (MX27ADS) should be supported.

Daniel

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Andy Green]

On 11/10/09 06:49, Somebody in the thread at some point said:

Hi -

>>     I have checked the inittab. the baud rate is correct.

> Sorry, I don't know then. I was sure you're facing a baud rate issue,
> which also is a common pitfall.

Vadivelan, it won't hurt to put an oscilloscope on the UART output and 
measure the smallest bit-time you see.

For 115200 it's 8.68us, if you see something different after the trash 
comes maybe you can get a clue from the measured period of the junk vs 
8.68us expected.

-Andy

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Vadivelan M]

An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091117/ea9258b3/attachment-0001.htm>

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Daniel Mack]

On Tue, Nov 17, 2009 at 09:34:44AM +0530, Vadivelan M wrote:
>    As you have suggested we tried on main line kernel also. It is hanging at
>    the same point...
> 
>    Freeing init memory..
>    After this some junk characters.
> 
>    We have measured the baud rate through CRO. It shows 8.6 us (115200) which
>    is correct.

Did you measure the junk characters or the 'working' serial output. The
question is whether the baud rate really changes.

>    Platform dependent changes
>                 Platform : IMX27ads board
>                                 clock changes & memory changes
>
>    will there be any platform dependency with UART driver?
>                 We did not do any modification here. It seems both the lower
>    version kernel and higher version kernel is same.

Please send in patches of your modifications so people here can have a
look to what you did.

>    Already working lower version kernel is not taking the command line
>    arguments [ passed from the CONFIG ]
>                 its taking the boot loader arguments only. so we just did a
>    hack so that it will take our CONFIG command line arguments.
>                 [commented strlcpy() @ arch/arm/kernel/setup.c - fn :
>    parse_tag_cmdline ]
>                 we are getting error : kernel panic - not syncing VFS: unagle
>    to mount roof fs on unknown-block(1,0)

You seem to have omitted the root= parameter. But frankly, I don't
understand why you're doing all that. Why don't let the bootloader pass
the options? The hard-coded config is only a fallback for bootloaders
that don't provide a cmdline tag.

Daniel



>    -----Daniel Mack wrote: -----
> 
>      To: Vadivelan M <vadivelan.m@tcs.com>
>      From: Daniel Mack <daniel@caiaq.de>
>      Date: 11/10/2009 12:19PM
>      cc: linux-arm-kernel at lists.infradead.org, linux-arm at lists.infradead.org
>      Subject: Re: imx27 - hanging at freeing init memory -- getting some junk
>      characters here after on console ..
> 
>  On Fri, Nov 06, 2009 at 11:12:03AM +0530, Vadivelan M wrote:
>  >    I have checked the inittab. the baud rate is correct.
>  >
>  >    When i am passing command line arguments "init=bin/sh
>  >    consloe=ttymxc0,115200 root=/dev/ram rw ip=off"
>  >
>  >    same status. i can see the print Freeing init memory and some uart
>  >    function prints...
>  >
>  >    After that only junk characters are coming.
>  >
>  >    we have checked serial drivers . almost no changes between 2.6.19(working
>  >    kernel) and 2.6.27
>  >
>  >    Please help us to go forward.....
> 
>  Sorry, I don't know then. I was sure you're facing a baud rate issue,
>  which also is a common pitfall.
> 
>  Can you try using a current mainline git kernel and see if the problem
>  persists? Your machine type (MX27ADS) should be supported.
> 
>  Daniel
> 
>  =====-----=====-----=====
>  Notice: The information contained in this e-mail
>  message and/or attachments to it may contain
>  confidential or privileged information. If you are
>  not the intended recipient, any dissemination, use,
>  review, distribution, printing or copying of the
>  information contained in this e-mail message
>  and/or attachments to it are strictly prohibited. If
>  you have received this communication in error,
>  please notify us by reply e-mail or telephone and
>  immediately and permanently delete the message
>  and any attachments. Thank you

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Vadivelan M]

An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091117/f8089b77/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch_mx27ads.zip
Type: application/zip
Size: 21771 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091117/f8089b77/attachment-0001.zip>

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Daniel Mack]

On Tue, Nov 17, 2009 at 01:57:11PM +0530, Vadivelan M wrote:
>  Did you measure the junk characters or the 'working' serial output. The
>  question is whether the baud rate really changes.
>           -- Yes. we have measured the baud rate when the junk characters starts coming.

Then the only explanation I have is that something seriously crashes
your userspace binaries and makes the kernel go wild.

>  Please send in patches of your modifications so people here can have a
>  look to what you did.
>           -- Please find the patches [please find the attachment . ]

I don't get what you're doing and why. Why do you patch around in
vmalloc.h? What reason is there to modify the clock framework for that
platform? And Those patches are obvisouly agains version 2.6.19.2 and
not mainline? Without any word of elaboration, I'm afraid you're on your
own.

My suggestion is to take the MX27ADS platform which your kernel config
is made for and try the current mainline kernel on that hardware.
Without any of your patches. Then find out the difference between that
setup and your own board.

Albeit I don't have such hardware, but I'm quite confident the reference
platform works well. Maybe someone of the MX2 people can acknowledge that.

Daniel

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Vadivelan M]

An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091117/86f8ad3d/attachment-0001.htm>

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Daniel Mack]

On Tue, Nov 17, 2009 at 05:29:35PM +0530, Vadivelan M wrote:
>    Thanks for the continuous support. 
>    As you have suggested we have tried in main kernel with default
>    configuration.
> 
>    Without any change its stopping at

[...]

>    <1>Unhandled fault: external abort on non-linefetch (0x008) at 0xf4300000
>    Internal error: : 8 [#1]
>    Modules linked in:
>    CPU: 0    Not tainted  (2.6.27 #11)
>    PC is at mx27ads_timer_init+0x14/0x44
>    LR is at time_init+0x1c/0x24
>    pc : [<c0011390>]    lr : [<c000f8ac>]    psr: 800000d3
>    sp : c0429fa8  ip : c0429fb8  fp : c0429fb4
>    r10: a0021b58  r9 : 41069264  r8 : a0021b8c
>    r7 : c042ce5c  r6 : c0023f14  r5 : c044bcf0  r4 : c044bce4
>    r3 : f4300000  r2 : 00000000  r1 : 00000000  r0 : 019bfcc0
>    Flags: Nzcv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment kernel
>    Control: 0005317f  Table: a0004000  DAC: 00000017
>    Process swapper (pid: 0, stack limit = 0xc0428268)
>    Stack: (0xc0429fa8 to 0xc042a000)
>    9fa0:                   c0429fc4 c0429fb8 c000f8ac c001138c c0429ff4
>    c0429fc8
>    9fc0: c0008ae8 c000f8a0 c000853c 00000000 00000000 c0023f14 00000000
>    00053175
>    9fe0: c044c60c c0024318 00000000 c0429ff8 a0008034 c0008970 00000000
>    00000000
>    Backtrace:
>    [<c001137c>] (mx27ads_timer_init+0x0/0x44) from [<c000f8ac>]
>    (time_init+0x1c/0x24)
>    [<c000f890>] (time_init+0x0/0x24) from [<c0008ae8>]
>    (start_kernel+0x188/0x30c)
>    [<c0008960>] (start_kernel+0x0/0x30c) from [<a0008034>] (0xa0008034)
>     r6:c0024318 r5:c044c60c r4:00053175
>    Code: e92dd800 e24cb004 e59f3020 e59f0020 (e1d330b0)
>    <4>---[ end trace 1b75b31a2719ed1c ]---
>    <0>Kernel panic - not syncing: Attempted to kill the idle task!

Assuming this is the reference hardware which you're running on, others
should be able to reproduce this error. Unfortunately I can't help here,
as I don't have access to any MX2 based hardware. Anyone else?

Daniel

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Martin Fuzzey]

> Assuming this is the reference hardware which you're running on, others
> should be able to reproduce this error. Unfortunately I can't help here,
> as I don't have access to any MX2 based hardware. Anyone else?
>

Mainline (2.6.32rc5) works fine on MX21 for me.

I also have a MX27 based board (Eukrea CPUMX27 module not a ADS) which
worked fine on 2.6.30 (haven't tried since - could do so if no one
else has a ADS handy).

I think it was mentionned somewhere in the thread but what is user
space doing? - didn't see any reference to init=/bin/sh in the kernel
command line log.

Another idea would be to patch drivers/serial/imx.c so that
imx_set_termios() and imx_setup_ufcr() are NOPs; that should leave the
UART config as the bootloader set it - which seems to work.

[even though the bit time is correct maybe its a word format error...]

Martin

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Eric Bénard]

Hi,

Martin Fuzzey wrote :
>> Assuming this is the reference hardware which you're running on, others
>> should be able to reproduce this error. Unfortunately I can't help here,
>> as I don't have access to any MX2 based hardware. Anyone else?
>>
> Mainline (2.6.32rc5) works fine on MX21 for me.
> 
> I also have a MX27 based board (Eukrea CPUMX27 module not a ADS) which
> worked fine on 2.6.30 (haven't tried since - could do so if no one
> else has a ADS handy).
> 
2.6.32-rc5 still works fine on CPUMX27 (i.MX27 + console on UART1 with 
TX/RX/RTS/CTS wired + OpenEmbedded generated rootfs).

How is wired your UART ? Is it using RTS/CTS ?
Is the iomux properly setup ?

Eric

imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..

[Subramani Venkatesh]

Hi Vadivelan,
Why don't you send us inittab file too, that would help us to debug the
problem.
It looks like a baudrate issues...

Regards,
Subbu
On Wed, Nov 4, 2009 at 2:39 AM, Vadivelan M <vadivelan.m@tcs.com> wrote:

>
> Hi,
> 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
> Memory policy: ECC disabled, Data cache writeback
> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
> Kernel command line: root=/dev/ram rw mem=64M console=ttymxc0,115200
> MXC GPIO hardware
> MXC IRQ initialized
> PID hash table entries: 256 (order: 8, 1024 bytes)
>
>  Clock input source is 26000000
>
>  After for loop
>  test1
>  CCM_PCCR1 = fe5aef88
>  b4 spll_clk.disableConsole: colour dummy device 80x30
> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
> Memory: 64MB = 64MB total
> Memory: 60780KB available (1956K code, 252K data, 92K init)
> Calibrating delay loop... 132.71 BogoMIPS (lpj=663552)
> Security Framework initialized
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> kernel thread started : M.V<5>SCSI subsystem initialized
> checking if image is initramfs...it isn't (no cpio magic); looks like an
> initrd
> do_sys_open entry<6>Freeing initrd memory: 1792K
> NetWinder Floating Point Emulator V0.97 (extended precision)
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> JFS: nTxBlock = 489, nTxLock = 3914
> msgmni has been set to 122
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Serial: IMX driver
> imx-uart.0: ttymxc0 at MMIO 0x1000a000 (irq = 20) is a IMX
> console [ttymxc0] enabled
> imx-uart.1: ttymxc1 at MMIO 0x1000b000 (irq = 19) is a IMX
> imx-uart.2: ttymxc2 at MMIO 0x1000c000 (irq = 18) is a IMX
> imx-uart.3: ttymxc3 at MMIO 0x1000d000 (irq = 17) is a IMX
> imx-uart.4: ttymxc4 at MMIO 0x1001b000 (irq = 49) is a IMX
> imx-uart.5: ttymxc5 at MMIO 0x1001c000 (irq = 48) is a IMX
> brd: module loaded
> loop: module loaded
> st: Version 20080504, fixed bufsize 32768, s/g segs 256
> Driver 'st' needs updating - please use bus_type methods
> Driver 'sd' needs updating - please use bus_type methods
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> do_sys_open entrydo_sys_open entry<5>RAMDISK: Compressed image found at
> block 0
> 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 ....
>
> ????&#531488;0^???r?'??????r:???????:??M? ??D?d?z ???
> ???8V?`?????V?]nn]^??m8m??^? ?m? E??N??8??6???:]???
>
>
> Thanks and Regards,
>
> Vadivelan M
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>
>
> _______________________________________________
> linux-arm mailing list
> linux-arm at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091205/7dea7d61/attachment-0001.htm>