From: Kevin Hilman <khilman@deeprootsystems.com>
To: Peter Reid <ppeter.reid@gmail.com>
Cc: Koen Kooi <koen@beagleboard.org>, linux-omap@vger.kernel.org
Subject: Re: Beagle PM hangs
Date: Wed, 28 Jan 2009 08:28:52 -0800 [thread overview]
Message-ID: <87zlhbqtrv.fsf@deeprootsystems.com> (raw)
In-Reply-To: <345163910901280814nb847b34pca50f4ee6e49929d@mail.gmail.com> (Peter Reid's message of "Wed\, 28 Jan 2009 21\:44\:01 +0530")
Peter Reid <ppeter.reid@gmail.com> writes:
> Hi Kevin,
> I get hangs after boot on beagle with latest PM tree i have quite a
> few scripts that run on boot.
>
> have you seen this before?
I have not, but I believe Koen has see something similar. I've mainly
been testing just a minimal rootfs and a minimal set of drivers on
Beagle so I can hit full-chip off in idle.
It would help if you could desribe your setup in more detail. What
kernel config are you using, what rootfs are you using? Does it hang
in the same spot every time? If so, what is going on when it hangs?
Have you written anything to any of the /sys/power/* files?
Kevin
next parent reply other threads:[~2009-01-28 16:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <345163910901280814nb847b34pca50f4ee6e49929d@mail.gmail.com>
2009-01-28 16:28 ` Kevin Hilman [this message]
2009-01-28 17:46 ` Beagle PM hangs Kevin Hilman
2009-01-30 14:16 ` Sriram V
2009-01-30 14:34 ` Woodruff, Richard
2009-01-30 17:12 ` Kevin Hilman
2009-01-30 19:41 ` Pandita, Vikram
2009-01-30 19:53 ` Kevin Hilman
2009-01-30 21:31 ` Woodruff, Richard
2009-02-02 5:00 ` Nayak, Rajendra
2009-01-30 21:34 ` Koen Kooi
2009-01-30 22:03 ` Woodruff, Richard
2009-01-30 22:09 ` Koen Kooi
2009-01-30 22:39 ` Kevin Hilman
2009-01-30 22:49 ` Woodruff, Richard
2009-01-30 23:21 ` Kevin Hilman
2009-01-31 11:18 ` Igor Stoppa
2009-01-30 22:40 ` Woodruff, Richard
2009-01-29 17:20 ` Peter Reid
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=87zlhbqtrv.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=koen@beagleboard.org \
--cc=linux-omap@vger.kernel.org \
--cc=ppeter.reid@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox