From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: n900 in 4.2-rc0: repeating oopses
Date: Sun, 26 Jul 2015 11:26:15 +0200 [thread overview]
Message-ID: <20150726092615.GA6824@amd> (raw)
In-Reply-To: <20150701103421.GV4156@atomide.com>
Hi!
> > > So, Pavel can you re-test? Maybe there can be problem with some driver
> > > which Tony did not compiled into zImage? Just speculation...
> >
> > I re-tested with today's git, and it seems to boot. Thanks for help...
>
> OK good to hear.
>
> > Now. "echo mem > /sys/power/state" is broken, as in "returns
> > immediately in about 50% cases". The messages are
> >
> > Powerdomain (per_pwrdm) didn't enter target state 1
> > Powerdomain (core_pwerdm) didn't enter target state 1
> >
> > Any ideas? Thanks,
>
> Works for me after enabling the idle timeouts with the following
> script and blanking the screen and disconnecting USB:
>
> Also both keyboard LEDs should start blinking after the idle
> timeout with screen blanked and USB disconnected. If not, you
> have some module loaded that blocks the deeper idle states.
Ok, tried that, I had to do:
cd /sys/class/gpio
echo 162 > export
cd gpio162
echo out > direction
echo 1 > value
to get the debug lights to work. But I could not get those leds to
blink.
> modprobe leds-gpio
> modprobe ledtrig-default-on
Is this actually neccessary/relevant?
> echo 255 > /sys/class/backlight/acx565akm/brightness
And this?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-07-26 9:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 9:32 n900 in 4.1-rc0 Pavel Machek
2015-04-16 9:37 ` Marc Zyngier
2015-04-16 16:35 ` Tony Lindgren
2015-04-26 10:15 ` Pavel Machek
2015-04-16 16:45 ` Tyler Baker
2015-04-26 10:20 ` Pavel Machek
2015-04-27 18:58 ` Tyler Baker
[not found] ` <20150629091146.GA5103@amd>
2015-06-29 10:45 ` n900 in 4.2-rc0: repeating oopses Pali Rohár
2015-06-30 9:24 ` Pavel Machek
2015-06-30 9:53 ` Pali Rohár
2015-07-01 6:59 ` Tony Lindgren
2015-07-01 7:22 ` Pali Rohár
2015-07-01 9:59 ` Pavel Machek
2015-07-01 10:34 ` Tony Lindgren
2015-07-01 13:09 ` Pavel Machek
2015-07-02 6:16 ` Tony Lindgren
2015-07-26 22:31 ` Pavel Machek
2015-07-27 7:12 ` Pali Rohár
2015-07-02 20:25 ` Pavel Machek
2015-07-26 9:26 ` Pavel Machek [this message]
2015-07-28 6:01 ` Tony Lindgren
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=20150726092615.GA6824@amd \
--to=pavel@ucw.cz \
--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).