From: d.cristiani@idem-tech.it (Dylan Cristiani)
To: linux-arm-kernel@lists.infradead.org
Subject: PXA270 linux-2.6.35.7 boot hang
Date: Fri, 1 Oct 2010 17:37:06 +0200 [thread overview]
Message-ID: <20101001173706.00006c12@unknown> (raw)
In-Reply-To: <AANLkTi=JEUbxmTZ6PHbz_Gi7KvNf+KJat7R1ot5LQ1SH@mail.gmail.com>
On Fri, 1 Oct 2010 21:53:14 +0800
Eric Miao <eric.y.miao@gmail.com> wrote:
> On Fri, Oct 1, 2010 at 6:33 PM, Santhosh N <san.mlists@gmail.com>
> wrote:
> > Hi,
> >
> > I am porting the latest linux kernel 2.6.35.7 on our PXA270 board.
> > The kernel starts booting and stops at:
> > Uncompressing Linux... done, booting the kernel.
> >
> > I can run the linux kernel 2.6.26 on the same board without any
> > issues. I am passing the boot args as:
> > bootargs=console=ttyS2,460800 rw root=1f02
> >
> > The STUART is used as the debug serial port. I had to change the
> > uart_base to STUART in arch/arm/mach-pxa/include/mach/uncompress.h
> > to get ?"Uncompressing Linux... done, booting the kernel.".
> >
> > I have set also set CONFIG_SERIAL_PXA_CONSOLE=y.
> >
> > Can anyone tell if I am missing something?
> >
>
> There could be many reasons. But you may want to turn on DEBUG_LL
> and earlyprintk for some early diagnostic messages. You got
> "Uncompress ..." messages so I assume the UART is setup correctly to
> this weird 460800 baudrate (though I doubt STUART on PXA27x is able
> to do that)
i agree with Eric but i remember that the maximum baud rate is 921,600
bps for all S-FF-BTUART pxa's uarts; maybe you can try also to migrate
from working kernel 2.6.26 to 2.6.27.... and so on, to see when it
first hangs, then seeing what was changed, with relation with
your specific cpu and/or platform, could be the trick.
next prev parent reply other threads:[~2010-10-01 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 10:33 PXA270 linux-2.6.35.7 boot hang Santhosh N
2010-10-01 13:53 ` Eric Miao
2010-10-01 15:37 ` Dylan Cristiani [this message]
2010-10-03 3:42 ` Marek Vasut
2010-10-05 11:31 ` Santhosh N
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=20101001173706.00006c12@unknown \
--to=d.cristiani@idem-tech.it \
--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