From: p.pisati@gmail.com (Paolo Pisati)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] panda board locks up on boot
Date: Sun, 27 Jan 2013 15:12:54 +0100 [thread overview]
Message-ID: <20130127141254.GC5714@stinkpad> (raw)
In-Reply-To: <0247700D01F14443B9209F90AD938CC52409708C@sestoex09.enea.se>
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
--
bye,
p.
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Pisati <p.pisati@gmail.com>
To: Mats Liljegren <mats.liljegren@enea.com>
Cc: Igor Grinberg <grinberg@compulab.co.il>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Tony Lindgren <tony@atomide.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Venkatraman S <svenkatr@ti.com>
Subject: Re: [BUG] panda board locks up on boot
Date: Sun, 27 Jan 2013 15:12:54 +0100 [thread overview]
Message-ID: <20130127141254.GC5714@stinkpad> (raw)
In-Reply-To: <0247700D01F14443B9209F90AD938CC52409708C@sestoex09.enea.se>
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@vger.kernel.org/msg83693.html
--
bye,
p.
next prev parent reply other threads:[~2013-01-27 14:12 UTC|newest]
Thread overview: 20+ 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 3:01 ` Steven Rostedt
2013-01-25 7:10 ` Igor Grinberg
2013-01-25 7:10 ` Igor Grinberg
2013-01-25 8:43 ` Mats Liljegren
2013-01-25 8:43 ` Mats Liljegren
2013-01-25 13:07 ` Steven Rostedt
2013-01-25 13:07 ` Steven Rostedt
2013-01-27 14:12 ` Paolo Pisati [this message]
2013-01-27 14:12 ` Paolo Pisati
2013-01-27 14:33 ` Nishanth Menon
2013-01-27 14:33 ` Nishanth Menon
2013-01-28 9:59 ` Mats Liljegren
2013-01-28 9:59 ` Mats Liljegren
2013-01-25 12:54 ` Steven Rostedt
2013-01-25 12:54 ` Steven Rostedt
2013-01-25 8:52 ` Russell King - ARM Linux
2013-01-25 8:52 ` Russell King - ARM Linux
2013-01-25 13:50 ` Steven Rostedt
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=20130127141254.GC5714@stinkpad \
--to=p.pisati@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.