From: menon.nishanth@gmail.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] panda board locks up on boot
Date: Sun, 27 Jan 2013 08:33:54 -0600 [thread overview]
Message-ID: <51053AD2.8080805@gmail.com> (raw)
In-Reply-To: <20130127141254.GC5714@stinkpad>
On 01/27/2013 08:12 AM, Paolo Pisati wrote:
> On Fri, Jan 25, 2013 at 08:43:15AM +0000, Mats Liljegren wrote:
>> Hi Steven,
>>
>> Do you have CONFIG_CPU_FREQ enabled? As I posted earlier in linux-kernel forum ("Failed booting PandaBoard ES with Linux 3.8 RC4" two days ago) my PandaBoard ES hangs while booting with this option enabled. It works fine without it. I have not bisected it down to a single commit though.
>
> glad i'm not the only one who hit this problem:
>
> "3.8rc4+ and cpu_freq omap: hangs, oopses, etcetc"
>
> http://www.mail-archive.com/linux-omap at vger.kernel.org/msg83693.html
>
Support for TPS is not yet in mainline kernel. you may want to do:
you could try running 'mw.w 0x4A31E05A 0x1' before bootm in u-boot ->
This will hack the pad of panda ES pin mean for controlling TPS voltage
register (again a kernel bug where the GPIO block setup by bootloader
got reset).
CPUfreq needs both voltage and frequency scaling to work and without
support of the TPS voltage scaling on vdd_MPU, you are stuck at boot
voltage, and just scaling frequency. with the not-enough boot voltage,
moving to higher frequencies can/will result in unpredictable behavior.
---
Regards,
NM
next prev parent reply other threads:[~2013-01-27 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 3:01 [BUG] panda board locks up on boot Steven Rostedt
2013-01-25 7:10 ` Igor Grinberg
2013-01-25 8:43 ` Mats Liljegren
2013-01-25 13:07 ` Steven Rostedt
2013-01-27 14:12 ` Paolo Pisati
2013-01-27 14:33 ` Nishanth Menon [this message]
2013-01-28 9:59 ` Mats Liljegren
2013-01-25 12:54 ` Steven Rostedt
2013-01-25 8:52 ` Russell King - ARM Linux
2013-01-25 13:50 ` Steven Rostedt
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=51053AD2.8080805@gmail.com \
--to=menon.nishanth@gmail.com \
--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).