All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Pihet <jean.pihet@newoldbits.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Pandaboard boot problem
Date: Mon, 14 Feb 2011 15:01:30 +0100	[thread overview]
Message-ID: <AANLkTinJPPDH6bWQ-Q14k6vgx8iGQvUmPFbrWqQX1JJ5@mail.gmail.com> (raw)
In-Reply-To: <20110204015301.GQ3322@atomide.com>

On Fri, Feb 4, 2011 at 2:53 AM, Tony Lindgren <tony@atomide.com> wrote:
> * Jean Pihet <jean.pihet@newoldbits.com> [110201 10:29]:
>> Hi!
>>
>> I have a problem with a Pandaboard hanging a few seconds after the
>> kernel boot, likely due to the watchdog firing.
>> The kernel boots fine, mounts the root FS (initramfs) and the shell
>> prompt works OK.
>>
>> Board details: Panda A1, OMAP4430 ES2
>> Kernel details: l-o tree master, using the omap2plus_defconfig +
>> initramfs. WDOG is enabled in the config.
>>
>> From some investigation I can see that PM runtime disables the wdog
>> (omap_device_idle). Is that intented?
>>
>> Any thought?
>
> Does it power down after few tens of seconds?
Yes

> If so, I've seen this same issue few times after having my panda
> powered off for a while, for example over the weekend.
>
> What I've noticed is that leaving just u-boot prompt running
> for a few minutes cures the problem somehow.. After that the
> kernel will boot just fine.
Unfortunately that is not helping.
I am still investigating. For the moment the pandaboard is pretty useless ;(

>
> Regards,
>
> Tony

Regards,
Jean

  reply	other threads:[~2011-02-14 14:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 18:30 Pandaboard boot problem Jean Pihet
2011-02-04  1:53 ` Tony Lindgren
2011-02-14 14:01   ` Jean Pihet [this message]
2011-02-14 14:38     ` Jarkko Nikula
2011-02-16  8:59       ` Jean Pihet

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=AANLkTinJPPDH6bWQ-Q14k6vgx8iGQvUmPFbrWqQX1JJ5@mail.gmail.com \
    --to=jean.pihet@newoldbits.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /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.